Design and development standard
The production goal is conformance with WCAG 2.2 Level AA where reasonably applicable. Automated checks are useful but do not replace keyboard, screen-reader, zoom, contrast, and real-user testing.
Content accessibility
Editors should use descriptive headings and links, concise alternatives for meaningful images, transcripts for important audio or video, properly structured tables, and plain explanations for technical terms.
Known foundation limits
The current administrator and public interfaces require continued testing across assistive technology and devices. Production uploads, third-party embeds, charts, downloadable documents, and editor-generated content need their own validation workflow.
Requesting assistance
Report the page, device or assistive technology, task you were attempting, and the barrier encountered through the contact page. An accessible alternative should be offered while the issue is reviewed.
Use the contact page so the request can be routed and documented.