What an accessibility review can establish before release
Abstract
Documents produced in an executive office often reach the public, a regulator, a board, or a customer without a deliberate accessibility review. This article explains what public accessibility standards require, how a document-level review differs from a website audit, and what evidence a support team can reasonably produce before release. It sets a bounded review method and identifies where specialist testing is still required. The method is written for the desk that prepares the document, not for a dedicated accessibility team [1][2][3].
Methodology
The review draws on the federal Section 508 standards, the Web Content Accessibility Guidelines, and federal guidance on effective communication. It separates source-document checks from published-format checks and treats automated results as a screening step rather than proof of conformance. The method is descriptive and cannot certify legal compliance, which depends on the document, the audience, and the applicable law. It also flags the point at which a specialist should take over [1][2][4].
The release decision and the accessibility question
An executive office publishes more than it realizes. Board packs, consultation papers, annual reports, policy notices, and responses to regulators all leave the building as documents. Each one may be read on a phone, with a screen reader, at a large zoom level, or in printed form. The release decision therefore includes an accessibility question whether or not anyone names it [1][2].
The question is not whether the document looks good in the author's application. It is whether the information and the structure survive the formats and tools that readers actually use. A polished PDF can be less accessible than a plain web page if its headings are only visual and its tables have no header structure. The office should decide who is responsible for that check before the release date [1][3].
The office should also decide which releases carry the highest risk. A public consultation document, a regulator filing, and a customer-facing report may reach readers who cannot ask for help. An internal draft may need less testing but still benefits from real headings and readable tables. Ranking releases by audience and consequence keeps the review proportionate.
A release that will be printed and posted online needs two different checks. The printed version depends on font size, contrast, and paper quality, while the online version depends on structure and assistive technology. The office should list every channel the document will use before it starts the review. A single review pass cannot cover channels it never considered.
What the standards actually require
The Section 508 standards require federal agencies to make electronic content accessible, and they incorporate the Web Content Accessibility Guidelines by reference for web content. The guidelines are organized around four principles: content must be perceivable, operable, understandable, and robust. Those principles apply to documents as well as pages, even when the specific techniques differ. The guidelines describe the outcome rather than a particular software package [1][2].
A practical reading focuses on structure, alternatives, and contrast. Headings should be real headings rather than bold text, images that carry meaning need alternative text, and colour should not be the only way to convey information. Tables need header rows and a reading order that makes sense. These are checks a trained support team can perform before a specialist is involved [1][2][3].
The standards do not require a particular software package or a single file format. They require the content to work with the tools readers use, which may include a screen reader, a keyboard, or a magnifier. A team can meet that requirement with a well-structured source document and a careful export. The method matters less than the result.
A document-level review before conversion
Start in the source application, because many accessibility problems are created before the file is exported. Use the built-in accessibility checker to find missing alternative text, unclear link text, and merged table cells. Fix the heading styles so the document has a logical outline. Give every table a header row and avoid using tables for layout [1][2].
Read the document in the order a screen reader would follow, not the order it appears on the page. Text boxes, sidebars, and floating images can scramble that order. Replace them with inline content or move them into a logical sequence. If the document uses a scanned image of text, run optical character recognition and then correct the result. The source review is where most of the improvement happens [2][3].
Keep a short pre-flight list beside the source file. It should cover headings, alternative text, table headers, link text, language settings, and the reading order. Ask the author to confirm the list before the document moves to review. A list that is used every time is more effective than a long guide read once.
Testing the published format
Export the document to each format the audience will receive, then test the exported file rather than the source. Check that the heading structure survived, that links are still descriptive, and that the reading order remains sensible. Open the file at a high zoom level and with a screen reader if one is available. Automated checkers can screen for common failures but cannot judge whether the content makes sense [1][2].
For a PDF, confirm that the document is tagged and that the tags match the visual structure. For a web page, check the keyboard path through links, forms, and menus. For a printed pack, check font size and contrast under ordinary lighting. Each format has its own failure modes, so one successful test does not cover the others [2][4].
Save the test evidence with the released file. A screenshot of the heading structure, the checker report, and a note about the screen reader used are enough for most offices. If a problem is found after release, the evidence shows what was tested and what changed. That record also helps the next document reuse the same fixes.
Roles, evidence, and sign-off
Name the person who prepares the document, the person who checks it, and the person who approves the release. The checker should have enough training to recognize a structural problem and enough authority to send the file back. Keep a short record of the checks performed, the format tested, and any known limitation. That record is more useful than a verbal assurance [1][3].
The sign-off should state what was tested and what was not. A document can pass a structural check and still have unclear language, which is a separate accessibility concern. Do not let a checklist imply a level of conformance the office has not demonstrated. Honest scope makes the record defensible and helps the next reviewer [2][3].
The reviewer should have a way to stop a release without needing a meeting. Give the role a clear hold authority and a short reason code. The accountable owner can then decide whether to fix, delay, or accept a documented risk. A hold that requires consensus is rarely used in time.
Limits and when to bring in a specialist
A support-team review is not a substitute for testing with people who use assistive technology. It can catch structural defects, but it cannot establish that the document is usable for every reader. Complex forms, interactive PDFs, mathematical notation, and multilingual content usually need specialist review. The office should budget for that review on high-risk releases [1][2].
Legal requirements vary by jurisdiction, funder, and audience. The Section 508 standards apply to federal agencies and their contractors in defined circumstances, while other laws may impose different duties. The office should confirm the applicable rule with qualified counsel rather than treating one standard as universal. The review method in this article is a starting point for that conversation [1][4].
Accessibility also depends on plain language. A document can have perfect tags and still be hard to understand because its sentences are long or its terms are undefined. The review should include a readability check for public-facing material. That check sits alongside the technical review rather than replacing it.
Key findings
- Accessibility is a release decision, not a formatting preference, because readers use phones, screen readers, zoom, and print [1][2].
- Structural fixes in the source document prevent most exported-format failures [1][2].
- Automated checkers screen for common defects but do not establish usability [2][3].
- Each published format needs its own test, including PDF tags and web keyboard paths [2][4].
- Specialist review is still needed for complex documents and for legal conformance claims [1][4].
Sources
- Section 508 of the Rehabilitation Act, U.S. General Services Administration
- Web Content Accessibility Guidelines (WCAG) 2.2, W3C
- Effective Communication, U.S. Department of Justice
- Creating Accessible Documents, U.S. General Services Administration