This is a self-assessment, not a verified conformance claim
{{LAST_REVIEWED}} by {{ACCESSIBILITY_REVIEWER}}.1. Our target
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. These guidelines explain how to make web content more accessible to people with a wide range of abilities, including visual, motor, auditory, and cognitive differences. Accessibility is treated as an ongoing effort, revisited as the site changes.
2. What we have done
Measures taken as part of building the site include:
- semantic HTML and landmark structure, with a “skip to content” link as the first focusable element;
- a visible keyboard focus indicator on interactive elements, with the focus ring offset so it is not obscured;
- color choices designed to meet the WCAG AA contrast ratios for text and interface elements, in both light and dark themes;
- navigation that works without JavaScript, with real links and native form controls;
- support for reduced-motion preferences, so animation is minimized when the operating system requests it;
- labels and accessible names on controls, and status information conveyed by text and icon, not by color alone;
- automated accessibility linting integrated into development to catch common issues early.
3. Known limitations
We want to be transparent about what is not yet complete. Known gaps as of the review date include:
- Real-device and assistive-technology testing is a named, open gap. Automated checks and keyboard testing have been done, but full manual testing on physical devices and with screen readers (for example, VoiceOver, NVGDA/NVDA, JAWS, and TalkBack) has not yet been completed. This is our highest-priority outstanding item.
{{AT_TESTING_STATUS}} - no independent third-party accessibility audit has been performed yet;
- downloadable documents such as certificate-of-analysis PDFs may not yet be fully tagged for accessibility;
- some third-party or embedded components may not fully meet our target and are being reviewed; and
- content and features added over time may temporarily fall short of the target until reviewed.
Because these gaps remain, we describe our status as “working toward” WCAG 2.2 AA rather than “conformant.” This wording will be updated only when testing supports a stronger statement.
4. Reporting a problem and getting help
If you encounter an accessibility barrier on this site, or need information in a different format, please tell us — your reports directly help us prioritize fixes. Contact {{ACCESSIBILITY_EMAIL}} (or {{ACCESSIBILITY_PHONE}}) with the page address, a description of the problem, and the browser and assistive technology you were using, if known. We aim to acknowledge reports within {{ACCESSIBILITY_RESPONSE_TIME}} and to work with you on a resolution.
5. Formal complaints
If you are not satisfied with our response, you may escalate through {{ACCESSIBILITY_ESCALATION}}. Applicable accessibility laws and complaint mechanisms depend on jurisdiction; [COUNSEL] to confirm the appropriate references and any required regulatory language before launch.