These are real reports from the same check a paid run performs, measured against five documents published by real public entities — a state application form, a state health publication, a school district child-nutrition document, and two college lecture decks. The numbers below are that run's output, not an illustration.
Published by Minnesota Dept of Employment & Economic Development · src-docx-0-sample-employment-application_tcm1045-420557.docx
Sample Employment Application · Word .docx · checked 2026-09-13
0 of 0 correctable mechanically on your approval
These checks found nothing in this document. That is not a guarantee that the document is accessible.
The mechanical fixes — alternative text, a marked table header row, the document title and its language — are applied for you only after you approve each one. Everything that needs authoring — headings, slide titles, and link text that has to describe where it goes — is flagged for you to make; this build does not correct those automatically.
What was measured: the document's own structure, read directly from the file. Word .docx and PowerPoint .pptx only in this version; PDF files are not read. The check finds missing alternative text, heading and title structure, unmarked table header rows, unclear link text, document language, and text contrast where the background is resolvable.
What this does not cover: automated structure checks find a subset of accessibility barriers. Reading order, whether an image is decorative, and text placed over an image cannot be determined from the file and are listed below as not determined. A document with no findings is not a guarantee that it is accessible — it means these checks found nothing in it.
This is not a determination of legal compliance with the ADA, Section 508, WCAG, or any other standard, and it is not a certification. It describes what this check measured in one document at one time.
Published by California Dept of Education · src-docx-1-uba2025-26.docx
UBA 2025-26 (child nutrition) · Word .docx · checked 2026-09-13
1 of 3 correctable mechanically on your approval
1 paragraph(s) look like headings by formatting but do not use a heading style
Formatting-only headings are not announced as headings by screen readers.
Where: 1 paragraph(s)
Flagged for a person — this build does not correct it automatically
1 table(s) have no row marked as a repeating header row
Without a header row, table data has no programmatic relationship to its column headings.
Where: 1 of 8 tables
Can be applied on your approval
1 link(s) do not describe their destination
"https://www.usda.gov/about-usda/general-information/staff-offices/office-assistant-secretary-civil-rights/how-file-program-discrimination-complaint" -> https://www.usda.gov/about-usda/general-information/staff-of
Where: 1 link(s)
Flagged for a person — this build does not correct it automatically
The mechanical fixes — alternative text, a marked table header row, the document title and its language — are applied for you only after you approve each one. Everything that needs authoring — headings, slide titles, and link text that has to describe where it goes — is flagged for you to make; this build does not correct those automatically.
What was measured: the document's own structure, read directly from the file. Word .docx and PowerPoint .pptx only in this version; PDF files are not read. The check finds missing alternative text, heading and title structure, unmarked table header rows, unclear link text, document language, and text contrast where the background is resolvable.
What this does not cover: automated structure checks find a subset of accessibility barriers. Reading order, whether an image is decorative, and text placed over an image cannot be determined from the file and are listed below as not determined. A document with no findings is not a guarantee that it is accessible — it means these checks found nothing in it.
This is not a determination of legal compliance with the ADA, Section 508, WCAG, or any other standard, and it is not a certification. It describes what this check measured in one document at one time.
Published by Washington State Dept of Health · src-docx-7-331-149.docx
Publication 331-149 · Word .docx · checked 2026-09-13
1 of 2 correctable mechanically on your approval
no heading styles used in a document of 198 text paragraphs
Screen-reader users cannot navigate by section. The document has no Heading 1-6 styles applied.
Where: whole document
Flagged for a person — this build does not correct it automatically
4 table(s) have no row marked as a repeating header row
Without a header row, table data has no programmatic relationship to its column headings.
Where: 4 of 6 tables
Can be applied on your approval
The mechanical fixes — alternative text, a marked table header row, the document title and its language — are applied for you only after you approve each one. Everything that needs authoring — headings, slide titles, and link text that has to describe where it goes — is flagged for you to make; this build does not correct those automatically.
What was measured: the document's own structure, read directly from the file. Word .docx and PowerPoint .pptx only in this version; PDF files are not read. The check finds missing alternative text, heading and title structure, unmarked table header rows, unclear link text, document language, and text contrast where the background is resolvable.
What this does not cover: automated structure checks find a subset of accessibility barriers. Reading order, whether an image is decorative, and text placed over an image cannot be determined from the file and are listed below as not determined. A document with no findings is not a guarantee that it is accessible — it means these checks found nothing in it.
This is not a determination of legal compliance with the ADA, Section 508, WCAG, or any other standard, and it is not a certification. It describes what this check measured in one document at one time.
Published by Carleton College, Science Education Resource Center · src-pptx-0-interactive_lectures_presentat.v2.pptx
Interactive Lectures v2 · PowerPoint .pptx · checked 2026-09-13
0 of 1 correctable mechanically on your approval
4 slide(s) have no title placeholder
Slides without a title: slide 13, slide 17, slide 18, slide 19. A slide with no title has nothing for a screen reader to announce as its heading.
Where: 4 of 25 slides
Flagged for a person — this build does not correct it automatically
The mechanical fixes — alternative text, a marked table header row, the document title and its language — are applied for you only after you approve each one. Everything that needs authoring — headings, slide titles, and link text that has to describe where it goes — is flagged for you to make; this build does not correct those automatically.
What was measured: the document's own structure, read directly from the file. Word .docx and PowerPoint .pptx only in this version; PDF files are not read. The check finds missing alternative text, heading and title structure, unmarked table header rows, unclear link text, document language, and text contrast where the background is resolvable.
What this does not cover: automated structure checks find a subset of accessibility barriers. Reading order, whether an image is decorative, and text placed over an image cannot be determined from the file and are listed below as not determined. A document with no findings is not a guarantee that it is accessible — it means these checks found nothing in it.
This is not a determination of legal compliance with the ADA, Section 508, WCAG, or any other standard, and it is not a certification. It describes what this check measured in one document at one time.
Published by Carleton College, Science Education Resource Center · src-pptx-1-natural_disasters_unit_presentation_14558136752117405746.pptx
Natural Disasters unit presentation · PowerPoint .pptx · checked 2026-09-13
2 of 4 correctable mechanically on your approval
5 image(s) have no alternative text
slide 4 "Shape 95": no alt text; slide 6 "Shape 106": no alt text; slide 6 "Shape 108": no alt text; slide 6 "Shape 110": no alt text; slide 7 "Shape 118": no alt text
Where: 5 of 5 images
Can be applied on your approval
2 slide(s) have no title placeholder
Slides without a title: slide 4, slide 6. A slide with no title has nothing for a screen reader to announce as its heading.
Where: 2 of 8 slides
Flagged for a person — this build does not correct it automatically
1 slide(s) contain only an image and no text alternative at all
A slide that is a single picture with no text is unreadable to a screen-reader user unless the picture carries alt text.
Where: 1 slide(s)
Flagged for a person — this build does not correct it automatically
no presentation title set
The title is announced for the presentation.
Where: document properties
Can be applied on your approval
The mechanical fixes — alternative text, a marked table header row, the document title and its language — are applied for you only after you approve each one. Everything that needs authoring — headings, slide titles, and link text that has to describe where it goes — is flagged for you to make; this build does not correct those automatically.
What was measured: the document's own structure, read directly from the file. Word .docx and PowerPoint .pptx only in this version; PDF files are not read. The check finds missing alternative text, heading and title structure, unmarked table header rows, unclear link text, document language, and text contrast where the background is resolvable.
What this does not cover: automated structure checks find a subset of accessibility barriers. Reading order, whether an image is decorative, and text placed over an image cannot be determined from the file and are listed below as not determined. A document with no findings is not a guarantee that it is accessible — it means these checks found nothing in it.
This is not a determination of legal compliance with the ADA, Section 508, WCAG, or any other standard, and it is not a certification. It describes what this check measured in one document at one time.
A paid run produces this same report for your document, plus the corrected file for the fixes you approve and a dated record hosted on our domain that you can attach to a client deliverable.
Check a document