The site has to live by its purpose.

Our commitment

The target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Where a simple improvement can materially help, we intend to go beyond that baseline. WCAG covers many needs, but no checklist can represent every person or every disability.

Measures built into this version

• Semantic page structure and plain-language labels
• Keyboard-operable controls with strongly visible focus
• Responsive reflow and touch targets designed for small screens
• Color-independent states and high-contrast reading choices
• User-controlled text size, line spacing, letter spacing, and word spacing
• Reduced-motion support and print-friendly large text
• ARIA used to clarify status and controls where native HTML is not enough

How it has been assessed so far

Development testing has included automated build and functional checks, direct desktop visual inspection, and interaction at a 390-pixel mobile viewport. Output behavior—not only page appearance—has been tested for the current reader.

Automated checks are useful but do not prove accessibility. A broader real-screen-reader matrix, assistive-technology review, and testing with disabled users remain important future work.

Known limitations

• Device speech voices and keyboard behavior can vary across browser and operating-system combinations. Some voices may use an external online service.
• The exact-detail finder uses local pattern matching. It may miss a detail or identify ordinary text as a date, time, amount, phone number, or email address.
• Printed size, margins, and page breaks vary by browser and printer settings.
• This release has not yet completed a formal independent audit or a broad test across real screen readers and other assistive technologies.

Technical approach

The site relies on current HTML, CSS, and JavaScript standards. The interactive reader requires JavaScript; the informational pages remain ordinary structured documents. We prefer native controls and add WAI-ARIA only where it supplies information native HTML cannot express clearly.