Accessibility Statement

Last updated: 6 November 2026. App Works is meant to be usable by anyone who needs a calculator, including people who navigate with a keyboard, read with a screen reader or enlarge text on a small screen. This statement describes where we stand, what we have tested, and how to tell us when something gets in your way.

Accessibility Commitment

Accessibility is treated as a defect class here, not a courtesy. When a calculator cannot be operated without a mouse, or a chart is unreadable to a screen reader, that is a bug and it is fixed in the same queue as a broken formula. We aim for WCAG 2.2 level AA on every page and we accept that some parts of the site, particularly older tools with custom sliders, are still short of that target while they are rebuilt.

Compliance Standards

Our reference standard is WCAG 2.2 AA, and we read it alongside EN 301 549 and the ADA guidance that applies to commercial websites in the United States. Conformance is checked against those success criteria rather than against a vendor badge: automated scans catch perhaps a third of real problems, so the rest is found by tabbing through pages and listening to a screen reader. We also audit pages when JavaScript is slow, because a calculator that never appears is still a failure.

Accessible Features

The features below are present across the site today, with caveats noted where they are incomplete.

  • Semantic structure. One H1 per page, headings in order, landmark regions around navigation and content, and a visible skip link at the top of every page.
  • Form controls. Every input has a persistent label rather than a placeholder, errors are announced in text, and results are written into a live region so a screen reader hears the new number.
  • Contrast and zoom. Body text passes 4.5:1 against its background, layouts reflow at 400% zoom without horizontal scrolling, and motion respects the reduced-motion setting.

Keyboard Navigation

Every interactive element can be reached with Tab and operated with Enter or Space, and the focus ring is never removed without a visible replacement. Calculator forms keep a logical tab order from first input to result, sliders respond to arrow keys and Page Up, and charts that carry meaning also expose the underlying numbers in a table. Where a widget traps focus — a rare case in the mortgage amortisation view — Escape releases it, and we treat any trap as a bug to be removed.

Screen Reader Support

Testing is done with VoiceOver on macOS and Safari, with NVDA on Windows where a volunteer tester is available.

  • Announced results. After a calculation, the result block is marked as a live region so the value is spoken without requiring a re-read of the page.
  • Known gaps. Two older sliders announce their value only on release, and one comparison chart lacks a data table in the Indonesian edition. Labels are reviewed by hand, because a wrong ARIA label is worse than silence: it announces a function that does not exist.

Trademark Notice

Names of assistive technologies, browsers and standards bodies mentioned here belong to their owners and are used only to describe what we test against. A mention of NVDA or VoiceOver is not an endorsement of this site by those projects, and no claim of certification is made by naming a standard. If a vendor believes a reference misrepresents their product, we will correct the wording. Certification is something a third party grants, not something a site declares for itself, and where a name is used loosely we prefer the generic description.

Governing Law

This statement is published under the laws of the State of California, United States, and does not create a contractual obligation beyond the accessibility duties that already apply to the site. Where local law grants a stronger right — the European Accessibility Act, for instance — that right governs your complaint. Nothing in this statement promises a date by which a known gap will close.

Editorial Review

The statement is revisited twice a year, and whenever a template or calculator rebuild changes the markup. Reviews are recorded with the pages sampled, the tools used and the issues opened, so a later reader can see what was tested rather than only what was claimed. The next review is scheduled for May 2027, and the sample grows each time.

Contact Us

Tell us what blocked you at [email protected] or through the contact form, including the page and the assistive technology you use; we reply within two business days and aim to fix blocking issues within a release cycle.