What standard do we aim for?

WCAG 2.1 Level AA. That is the benchmark most settlements, consent decrees, and court orders in the United States reference, and it is the one we describe in our own reporting on Title III litigation.

What have we actually done?

The site is tested with automated tooling and by keyboard. Specific measures in place today:

  • A skip link so keyboard users can bypass the masthead, navigation, and headline ticker on every page.
  • One page heading per page, with headings nested in order, so screen reader users can navigate by structure.
  • A visible focus outline on every interactive element.
  • A control to stop the scrolling headline ticker, because content that moves on its own has to be stoppable by everyone, not only by readers who can hover a mouse.
  • Reading preferences for text size, contrast, and motion, stored on your device.
  • Text descriptions on images, and credit lines that are readable rather than decorative.

Why is there no accessibility overlay?

Deliberately. Overlay widgets that promise to make a site compliant do not repair the underlying code. They frequently conflict with the screen reader or magnifier a person already uses, and their compliance claims have drawn regulatory scrutiny. Businesses that installed them have still been sued, because the barriers were never fixed.

The panel in the corner of this site makes no compliance claim. It adjusts text size, contrast, and motion, and nothing else. The accessibility work is in the markup, where it belongs.

What are we still working on?

Automated testing catches a minority of real barriers. We have not yet completed testing with screen readers across browsers, and we have not had the site reviewed by users with disabilities. Both are planned. We would rather say that plainly than imply a level of conformance we have not verified.

How do I report a barrier?

Email alex@buildifyhq.com and describe what you were trying to do, the page you were on, and the assistive technology you were using if any. We treat these as bug reports, not feedback, and we will tell you what we did about it.