Commitment
Our organization is committed to making our website(s) and digital offerings accessible across web and mobile by proactively identifying and removing barriers. We are aligning our work to Level AA of the W3C’s current Recommendation for web accessibility, the Web Content Accessibility Guidelines (WCAG) 2.2, which adds nine new success criteria and removes 4.1.1 Parsing to reflect modern interoperability and usability needs (WCAG 2.2; What’s New in WCAG 2.2). We are updating references that previously pointed to WCAG 2.0 to reflect this current standard while remaining largely backward compatible with 2.0/2.1. Targeting WCAG 2.2 AA positions us well given today’s regulatory landscape: in the United States, the Department of Justice’s final rule under ADA Title II requires state and local governments to conform to WCAG 2.1 AA, with phased compliance dates beginning April 2026 for larger entities and April 2027 for smaller entities (DOJ Title II fact sheet); in the European Union, harmonized standard EN 301 549 has been updated to reference WCAG 2.2 and the European Accessibility Act applies from 28 June 2025 (EN 301 549 v4.1.1; European Accessibility Act). We recognize that accessibility issues remain prevalent on the web—automated testing of 1,000,000 home pages in 2024 found detectable WCAG failures on 96.3% of pages, averaging 56.8 errors per page—so we are investing in continuous improvements grounded in standards and user feedback (WebAIM Million 2024). We are actively working to increase the accessibility and usability of our website(s) and endeavor to conform to level AA of the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines 2.0.
Scope & Plan
We are executing a multi‑year, measurable plan to achieve and sustain WCAG 2.2 Level AA conformance across our web and mobile experiences. Our approach includes policy updates (procurement and vendor SLAs that specify “WCAG 2.2 Level AA”), design‑system upgrades (focus visibility, target sizes, gesture alternatives, forms/authentication patterns), CI/CD automation mapped to ACT‑informed rules, and routine manual and assistive technology testing across platforms and browsers. We align our roadmap to current regulations and standards convergence—including the U.S. DOJ Title II rule (WCAG 2.1 AA) and EU EN 301 549/EAA—so our implementations are compliant today and future‑ready (DOJ Title II; EN 301 549; EAA; WCAG 2.2 Quick Reference).
- Accessibility Team: Our cross‑functional Accessibility Team (product, design, engineering, QA, content, legal) leads policy, training, and delivery. We maintain a WCAG 2.2 AA–mapped design system and component library, with documented usage guidance and patterns aligned to ARIA Authoring Practices and verified for assistive‑technology interoperability via the ARIA‑AT project. We track program KPIs such as: percentage of critical user journeys passing WCAG 2.2 AA checks; automated rule coverage and CI gate pass rates; time‑to‑remediate priority defects; and training completion by role. Our governance and reporting practices follow W3C WAI guidance for planning/managing accessibility programs (WAI program guidance) and reflect strengthened expectations seen in public‑sector oversight (for example, defined leadership, regular testing, inventories, and metrics). We maintain a conformance statement process referencing WCAG 2.2 conformance requirements for full pages and complete processes (WCAG 2.2 Conformance).
- Audit & Review: We conduct continuous audits combining automated and human testing. Automated scans (e.g., axe‑powered checks in development tooling/CI) provide fast feedback on detectable issues, while scheduled manual reviews verify keyboard navigation, focus visibility/non‑obstruction, pointer target sizes and spacing, reflow at small viewports, zoom at 200–400%, form labeling/error recovery, and content triggered on hover/focus. We test core flows with screen readers (NVDA, JAWS, VoiceOver/TalkBack) and alternative inputs (keyboard‑only, voice/switch), and validate custom widgets against ARIA‑AT results where available. Reviews are mapped to WCAG 2.2, with particular attention to new criteria such as Focus Not Obscured (2.4.11), Dragging Movements (2.5.7), Target Size (Minimum) (2.5.8), Redundant Entry (3.3.7), and Accessible Authentication (3.3.8) (WCAG 2.2 Quick Reference; What’s New in 2.2). We schedule periodic third‑party validations to confirm our findings and align to evolving guidance and ACT‑informed rule sets.
- Remediation and Implementation: We implement universal coding standards and design‑system tokens that embed WCAG 2.2 AA—robust, high‑contrast focus indicators that are not obscured by sticky headers/overlays; sufficient target sizes or spacing; non‑drag alternatives for sliders and drag‑and‑drop; streamlined, consistently located help; reduced redundant data entry; and authentication that avoids cognitive tests and supports password managers and device‑based methods. We support copy/paste into password fields and modern authentication like passkeys to reduce cognitive and physical load. Although WCAG 2.2 removed 4.1.1 Parsing from conformance, valid semantic markup remains our baseline for interoperability. We apply these patterns across web and native mobile, and verify compatibility with platform accessibility features that continue to expand (for example, Apple’s on‑device Eye Tracking and other capabilities) (WCAG 2.2; What’s New in 2.2; Apple accessibility features).
Contact Us
We operate an accessibility feedback loop to drive measurable improvements and meet current expectations for transparency. If you encounter any barrier or need content in an alternate format, please contact us using the email below and include the page/app, assistive technology or browser used, and a brief description of the issue. We commit to acknowledge and triage reports within 5 business days and will provide periodic updates on confirmed issues and accessible alternatives when needed. We aggregate feedback themes and publish summaries of improvements (for example, issues resolved, median time to resolution, and top categories like color contrast, labels, keyboard traps) so users can see progress. This approach reflects widely adopted practices and regulatory expectations for accessible services (for example, the EU requirement for a feedback mechanism in public‑sector accessibility statements and Canada’s Accessible Canada Act guidance on summarizing feedback in progress reports) (EU Web Accessibility Directive; Accessible Canada Act – progress reports). We also prioritize fixes aligned to near‑term regulatory timelines (for example, ADA Title II WCAG 2.1 AA compliance dates beginning in 2026–2027) to ensure timely remediation (DOJ Title II final rule). Evidence shows automation alone is insufficient—96.3% of top home pages still had detectable WCAG errors in 2024—so we combine user feedback with manual testing by people using assistive technologies (WebAIM Million 2024).
Helpful Links
Web Content Accessibility Guidelines (WCAG 2.0)
U.S. Federal Government Section 508 accessibility guidelines
ADA.gov
What’s New in WCAG 2.2
How to Meet WCAG 2.2 (Quick Reference)
ADA Title II Web Rule (DOJ)
EN 301 549 (EU harmonized ICT standard)
European Accessibility Act
ARIA‑AT (Assistive Technology Interoperability Tests)