Conformance documents are useless unless they are themselves accessible

What it is

An accessibility statement shipped as a scanned PDF, a low-contrast legal page, or a modal the keyboard cannot enter never reaches the people who need it. The conformance document must itself be accessible is not courtesy: the statement's readers are exactly the people whose channels are blocked. If the document fails perceivable, operable, understandable, robust, then a perfect list, channel, and date have no function. Value is “can be read and acted on,” not “a file exists in the legal folder.”

Why it happens

Statements often live in another stack — a legal CMS, the brand-site footer, a download centre — that never used the product component library, so contrast, headings, focus, and language markup all drop. The second layer is that format already chooses the reader: an image PDF has no text layer, and a screen reader gets an empty document; a statement that exists only as an in-app sheet is invisible to anyone whose app has crashed or will not install. Structure also decides action: if the feedback link is not a real link, and the phone number lives only in a picture, the channel was never given. The statement page is part of the product, not an annex.

Studying it

Treat the statement URL as an ordinary page and run the same checks: finish it from the keyboard, listen to headings and links with a screen reader, zoom to 200%, check contrast and language. For PDFs, look for a text layer, a tag tree, and headings.

Independent variables: format (HTML / tagged PDF / image PDF / in-app modal); whether product components are used. Dependent variables: whether a screen reader can read the list and the channel; whether the keyboard can enter and leave; whether zoom causes two-axis scrolling.

Do not take “legal signed it” as evidence the document is usable.

Where it stops holding

Each language edition of a multilingual statement must be processable by assistive technology in that language; an accessible English original is not enough. Printouts for in-person service are allowed; they cannot be the only public release. E-signature and archive copies may keep an immutable PDF; the public still needs HTML. If a third-party policy host cannot be changed, switch host or offer an equivalent page on your own domain — “the host will not let us edit” cannot leave the statement unreadable.

Applying it

• Publish the public statement as HTML with real heading levels and a correct language attribute. If a PDF is required, export a tagged text PDF; scans are not allowed.
• Use the same contrast, focus, and link components as the product. Do not invent a separate “legal grey type.”
• Feedback links, phone numbers, and alternative-format entries are real, focusable controls, not text in an image.
• How to check: with the display off, listen to the statement from the first heading through a successful feedback submit. An empty document, an unnamed link, or focus trapped in a modal means the document does not yet have value. Zoom to 200% and confirm the list can be read without dragging sideways.

Related

• Same group: J1.12.1 A statement must list known failures, not only claim overall compliance · J1.12.2 A statement must offer a channel for reporting newly found barriers · J1.12.3 A statement must name test methods and the last update date
• Nearby: J1.01 Four Principles · J2.02 Text Resize
• Search terms: accessible accessibility statement · tagged PDF · POUR