archimedes
write

EverythingAccessibility

Accessibility

Target: WCAG 2.1 AA

This firm sells accessibility scoping, so this page describes what the site actually does rather than what it hopes to. Checked on the build you are looking at.

What it does

  • A skip link is first in the tab order and moves focus to the main content.
  • The search is a proper combobox. Arrow keys move through matches, Enter opens one, Escape clears. The active match is exposed through aria-activedescendant, and a polite live region announces how many matches there are.
  • The full index is in the HTML underneath the search. With scripting off, or if you would rather browse than type, everything is still there.
  • Every move between pages is a plain link. Nothing needs a mouse, a drag, a hover, or a gesture.
  • Focus is visible: a 2px outline offset from every link and button, and the search field changes its border when it has focus.
  • Motion stops. The blinking caret, the cycling placeholder, the scroll-driven reveal of the method diagram, and the transitions between pages all switch off under the operating system’s reduced-motion setting and under the “reduce motion” control in the header, which is remembered in this browser.
  • Colour is never the only signal. Decision points in the method are labelled “Decision” in text; the active search match is marked with aria-selected.
  • Contrast on the paper ground: body ink 11.9:1, quieter text 8.5:1, the green used for interaction 6.3:1, the red used for links 5.7:1. WCAG AA asks 4.5:1 for text.
  • The layout reflows down to 390 pixels wide without sideways scrolling, so 200% zoom on a laptop works.
  • Pages use landmarks (header, main, footer), one first-level heading each, and declare their language.

What it does not do yet

  • It has not been assessed by anyone but me. Behind this page is a keyboard pass and an automated scan on each build, which are the first two steps of the method I sell, not a third-party audit or a VPAT.
  • Page transitions only run in browsers that support cross-document view transitions. Everywhere else, navigation is ordinary, which is the intended fallback.

If any of this is untrue on the page you are looking at, write e.barbosa@asgfederal.com. It will be fixed, and this page corrected.