01 · CONFORMANCE STATUS
This site aims to conform to Web Content Accessibility Guidelines 2.2, Level AA. As of the last review it is substantially conformant: automated testing across every page in both themes reports no violations, and the issues found in our most recent audit have been fixed. "Substantially" is doing honest work in that sentence: conformance claims depend on manual judgement that we have completed for keyboard operation and macOS VoiceOver, but not yet for every assistive technology. The known gaps are listed in section 03.
02 · HOW WE TEST
- 01AUTOMATED, ON EVERY CHANGEEvery pull request runs axe-core against all pages in both colour themes, plus checks for reflow at 320px, target size, and keyboard reachability of the skip link. A failure blocks the merge.
- 02MANUAL KEYBOARD PASSESTemplates are operated keyboard-only: tab order, focus visibility, the consent-desk tab component, the mobile menu, and the contact form's error handling.
- 03DESIGN-TIME CONSTRAINTSColour tokens are checked against their worst-case surface before they ship. Motion is gated behind prefers-reduced-motion. Canvas artwork carries a text equivalent rather than being the only source of a heading.
03 · KNOWN LIMITATIONS
Publishing the gaps is the point of a statement like this. These are current and known, not hypothetical.
01
Wide data tables scroll on small screens
The security and record-index tables keep real table semantics rather than collapsing into stacked blocks, so on narrow viewports they scroll horizontally inside a labelled, keyboard-focusable region. This is a deliberate trade: column relationships survive for screen-reader users at the cost of some horizontal scrolling.
02
Dense monospace type
Several interface labels are set at 10–11px. They meet contrast minimums, but small type is a real barrier for some low-vision users. Browser zoom and OS text scaling both work; we consider raising the floor a live design question rather than a settled one.
03
Screen-reader coverage is partial
Testing to date is VoiceOver on macOS and keyboard-only operation. We have not yet completed passes with JAWS or NVDA on Windows, so we cannot claim verified parity there.
04 · REPORTING A BARRIER
If any part of this site stops you getting what you came for, tell us and we will fix it. Email hello@369hertz.com. We acknowledge reports within two business days and will tell you the remedy and the timescale, or give you the information in another format in the meantime. Accessibility reports are welcome from anyone; you do not need to be a client.
05 · IN CLIENT WORK
Interface code we deliver is verified to WCAG 2.2 AA per component (states, focus order, keyboard operation, and reduced motion), and the evidence ships with the work rather than being asserted afterwards. How engagements run.