Accessibility statement.
Our target, the checks completed and the work still to verify across the public reference desk and protected workspace.
Statement prepared: 2 November 2026.
Last source review: 2 November 2026.
Last complete browser and assistive-technology assessment: not yet completed.
Our accessibility target
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Full conformance has not been established. The current review covers source code and build checks; it does not establish that every page and complete task meets all applicable criteria.
Features intended to help
- A skip link, labelled navigation and descriptive headings help you find the main content.
- The menu and search include keyboard controls. Escape closes the menu or search dialog and returns focus to its trigger.
- Security findings include written status labels and explanations alongside their icons and colours.
- Motion is reduced when your device requests it. Editable controls use at least 16px text on narrow screens.
- Guides and reports have print styles. The report’s Print / PDF button produces the complete report, including findings excluded by an on-screen filter.
Known limitations and outstanding checks
Compatibility with NVDA, VoiceOver and TalkBack has not yet been tested. The full keyboard task sequence across Chrome, Firefox and Safari, 320px reflow, 200% text resizing, 400% browser zoom, text spacing and real-device layouts also remain to be verified.
Print styles and disclosure expansion have been improved in source. Native A4 print-preview PDFs from Chrome, Firefox and Safari have not yet been verified. Printing a filtered report page reflects its current view; use the report’s Print / PDF control for the complete report.
Sign-in for the separate protected workspace is provided by the ChatGPT Sites platform. The current source review does not establish the accessibility of that external sign-in process.
Help and reporting a problem
Visit Help & common questions for guidance on the checks, reports and supported workflows. A dedicated accessibility contact address has not yet been published; this remains an open release item.
When reporting an issue through the channel you use to contact the site owner, include the page address, the task you were attempting, what happened, and your browser or assistive technology if you know it. Do not include API keys, passwords or private assessment evidence.
How this statement will be updated
We will update the statement when browser and assistive-technology evidence becomes available, when known barriers are confirmed or fixed, and when an accessibility contact route is established. A source change alone is not recorded as a completed user test.
Read the WCAG 2.2 Recommendation for the full requirements.