Published document reading
An accessible document reader for longer reads.
Help readers find a passage, jump to the right table, and choose a comfortable reading appearance. These tools accompany the hosted HTML version of a document after it has been deliberately published or shared.
Updated
Four ways to move through the document.
A benefits handbook, meeting report, or course guide can contain the answer a reader needs several sections below its introduction. Open Reading tools above the document to choose where and how to read.
Go straight to a heading, table, or figure
Choose a destination from the document’s existing structure. The reader moves focus to the selected content, so a long report does not have to be read from the beginning every time.
Navigation reflects the HTML that was published. A missing heading or poorly described figure still needs correction in the document.
Find a word or phrase within this document
Search the visible document text and move between matching passages. A result brings the passage into view without opening another page or searching the entire website.
Up to 100 matching passages are shown. A more specific phrase narrows a long result list; text that only exists inside an image is not searchable.
Adjust the reading appearance
Choose default, large, or extra-large text; default, relaxed, or wide line spacing; and a narrow, default, or full-column reading width. Reset appearance restores the starting settings.
Preferences apply to the current reading session. Tables and forms retain the space they need, and these controls do not edit the published content or source file.
Listen when a local voice is available
Start at the beginning, choose a voice and reading speed, then pause, resume, or stop. The reader offers only voices the browser identifies as on-device.
Availability depends on the browser and device. Form entries, hidden text, and navigation are excluded. Read-aloud does not replace a screen reader or test the document’s accessibility.
Keep a clear path from source to reader.
Start with a supported source, inspect the converted structure and outstanding findings, and review the exact version before making it available. Reading controls help someone use that output; they cannot repair omitted content or decide whether a table’s header relationships are correct.
Document reader questions
- Does the reader change my PDF?
- No. Reading tools operate on the hosted HTML document. Text size, spacing, search, and speech do not modify the source PDF, its tag tree, or the published document version.
- Can a visitor use it without a DocAccessible account?
- A visitor who can access the published document can use its reading tools. A public document does not require an account; private documents and protected viewing links retain their existing access controls.
- Why might read-aloud be unavailable?
- The browser may not support speech synthesis or may not report any on-device voices. The reader explains that state instead of selecting a remote voice. You can use your screen reader or check local speech settings on your device.
- Do reading tools establish WCAG or PDF/UA conformance?
- No. The quality of the underlying content, heading structure, tables, alternatives, reading order, and interactions still matters. Review the exact output with keyboard and representative assistive technology before publication.