Standards target
Revised Section 508 incorporates WCAG 2.0 Level A and AA for web content. WCAG 2.2 AA adds newer success criteria, but does not by itself prove full 508 conformance. Scoping, functional performance, support, and documentation still matter.
This independent site is not represented as a federal system or as certified. Section 508 readiness is relevant because California Government Code §7405 applies Section 508 accessibility requirements to state governmental entities’ information technology work and procurement.
Last manual review
Reviewed , at commit ef1d11b. That is the date this status was written. The Atlas dates every source, retrieval, evidence record and watchlist review; this is that date for its own evaluation.
What that review covered
- Static: lint, canonical-data validation, and rendered HTML assertions.
- Structure: checks for page language, titles, skip navigation, main regions, layer labels, and the result-count live region.
- Relationship view: source and analysis remain consecutive semantic sections; native filters, written role labels, and complete text links duplicate decorative rails and nodes.
- Automated review: representative-route scans plus programmatic reflow, focus-order, and reduced-motion spot checks.
Those scans were a one-off. The tooling, exact route list and results were not recorded, and no accessibility tool runs in the release gate, so they cannot be reproduced today. The rendered-HTML assertions do run on every build; they are not the same checks.
Routes covered by that review
The routes that existed at that commit, plus the 404 page.
//directives/[id]/evidence/handoffs/methodology/data/accessibility
Not covered by that review
/research/tda-ntd— added Jul 13, 2026/corrections— added Jul 14, 2026/watchlist— added Jul 29, 2026- The presentation of every route above: the register was redesigned on Jul 22, 2026, after the review.
- Patterns added since: the print control on directive records, filters that rewrite the URL, and the watchlist disclosure widget on
/watchlistand on every directive page.
None of that is a finding that those surfaces are inaccessible. It states that they have not been evaluated, which is the only claim the record supports.
Pending before any conformance claim
- Keyboard: complete user-flow review in current Chrome, Firefox, and Safari.
- Assistive technology: VoiceOver and NVDA or JAWS review of the directive and handoff explorers, directive detail, evidence index, method, and download flows.
- Low vision: full 200% and 400% zoom, text-spacing, forced-colors, and narrow-width review across every route.
- Human evaluation: testing with disabled users and documented decisions about external source and evidence-file accessibility, including the inaccessible signed source.
Automated checks are quality controls, not certification. Until the pending reviews are complete and exceptions are documented, the project does not claim WCAG or Section 508 conformance. A future Accessibility Conformance Report would need to name the exact release, evaluator, method, environment, and exceptions.
Known external limitations
The signed executive order is hosted externally as a scanned, untagged PDF outside this repository and the site evaluation scope. The atlas provides semantic HTML summaries, short reviewed excerpts, and page locators to reduce that barrier, but those are not a complete alternative version and cannot remediate the authoritative source file.
Reviewed public artifacts are also externally hosted and remain outside this repository's conformance scope. The evidence layer records cautious accessibility metadata without claiming that a tagged PDF conforms to PDF/UA, WCAG, or Section 508. The Atlas cannot remediate those external files.