Our target
The site is built against the Web Content Accessibility Guidelines 2.2 at level AA. Accessibility is treated as a requirement of the build, not a task for later: a calculator whose form cannot be operated by keyboard is not finished.
The site is usable without an account, without a mouse and, for the calculators, without JavaScript.
What the site does
- Semantic structure — one first-level heading per page, ordered section headings, landmark elements and a skip link that moves focus straight to the main content.
- Labelled inputs — every field has a visible label, a unit, and a hint where the expected format is not obvious. Errors are announced in a status region rather than shown only by colour.
- Live results — the result container is a polite live region, so a screen reader announces the updated summary when a calculation completes.
- Keyboard access — all controls are reachable and operable with the keyboard, with a visible focus outline that is not removed for aesthetics.
- No-JavaScript fallback — the calculator form submits with a normal GET request, so results still render on the server when scripting is unavailable.
- Motion and contrast — animation is disabled when the operating system requests reduced motion, and text colours are chosen to meet AA contrast ratios.
- Language — the page language is declared, and an untranslated English article inside a Spanish or German page is marked with its own language attribute so screen readers switch voice correctly.
Known limitations
- Third-party advertising. Advertisements are served by Google in an iframe-like slot. Their markup, contrast and keyboard behaviour are outside our control, and a poorly built creative can create a barrier we cannot fix directly.
- Translated content. Only some calculator pages exist in Spanish and German. Where a page has not been translated it is served in English and labelled as English.
- Charts and tables. Results are delivered as tables with header cells. Very wide tables scroll horizontally on small screens rather than reflowing into cards.
- Browser support. The site targets current versions of Chrome, Firefox, Safari and Edge. Very old browsers may lose the live result update but keep the server-rendered fallback.
Reporting a barrier
If something on the site prevents you from getting an answer, email hello@usooz.com with:
- the address of the page,
- what you were trying to do,
- the assistive technology or browser you were using, if relevant.
Accessibility reports are treated as bugs and get the same review as a numerical error. We aim to reply within two business days and to fix or provide an alternative within thirty days.
How this statement is maintained
The statement is reviewed whenever the layout changes. It describes the current build rather than an aspiration; when a limitation is fixed, it is removed from the list above instead of being left as a stale claim.