Accessibility statement

1 · Conformance target

We aim for Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. As of 2026-05-30, the wiki is substantially conformant but not formally AA-attested. Known gaps are listed in §3 below.

2 · What works well today

• Skip-to-main-content link on every page
• Semantic HTML throughout (proper heading hierarchy, article-element wrappers, table-header associations on data tables)
• Keyboard-only navigation supported across catalog browsing, citation copy, and the search affordance at /wiki/find
• Respect for prefers-reduced-motion (no auto-playing animations)
• Single text-zoom up to 200% without horizontal-scroll on standard browsers
• Honest disclosure rather than false WCAG-AA badging

3 · Known limitations (honest disclosure)

Audited 2026-05-30 by an AI WCAG-specialist persona. Specific gaps identified, in remediation:

• PDF downloads are not tagged-PDF (PDF/UA). The auto-generated comparison memos at /wiki/compare/[pair]/[topic]/pdf are built with @react-pdf/renderer which does not produce tagged PDFs. For accessible access, use the HTML view (drop the /pdf suffix). Tagged-PDF tooling is on the Q4 2026 roadmap.
• Some colour-contrast pairs at 3.0-4.4:1. Confidence-tier chips on the coverage table use light tinted backgrounds; the contrast ratio of the chip text against the chip background is between 3.0:1 and 4.4:1 for some tiers. Mitigation in progress (iter-312 darkens the chip palette). Body-text contrast meets AA throughout.
• Non-English citation phrases.Coverage cells sometimes cite primary sources in their original language (e.g., French "Règlement (UE) 2024/1689") without a lang="fr" wrapper. Screen readers may mispronounce these phrases. Roadmap item.
• Touch-target size on citation widgets. Some buttons in the per-cell citation widget are below the WCAG 2.5.5 AAA target of 44×44 pixels. Mobile use is possible but tighter than ideal.

4 · Audit history

• 2026-05-30 (iter-312): Internal automated audit by WCAG-specialist persona; 15 findings prioritised (4 critical, 5 major, 6 minor). Critical findings on colour contrast + clipboard ARIA-live + accessibility statement remediated in same iter; remaining tracked in the public roadmap.
• Planned: external WCAG audit by a certified specialist before any commercial firehose customer is on-boarded (gated by editorial-board recruitment per /wiki/editorial-board).

5 · Report an accessibility issue

Email accessibility@policywindow.org. Please include: the page URL, what you were trying to do, what went wrong, the assistive technology you use (screen reader name + version, OS), and screenshots if relevant.

Response target: 7 business days for initial acknowledgement, 30 business days for remediation or for a specific roadmap commitment with a date. Issues affecting access to public-interest content (the catalog itself) are prioritised over cosmetic gaps.

If we don't respond within the SLA above, escalate via a GitHub issue using the bug-report template (github.com/ryanwong/policy-window) with the "accessibility" label.

6 · Technical context

This site is built with Next.js 16, React 19, and Tailwind CSS. We use semantic HTML wherever possible and rely on framework defaults for focus management. Browser support: modern evergreen browsers (Chrome, Firefox, Safari, Edge, last 2 major versions). Internet Explorer is not supported.