Docaccess

See exactly what a check delivers.

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 state education department child-nutrition document, and two college lecture decks. The numbers below are that run's output, not an illustration.

Sample Employment Application

Published by Minnesota Dept of Employment & Economic Development · src-docx-0-sample-employment-application_tcm1045-420557.docx

0 findings

Sample Employment Application · Word .docx · checked 2026-11-04

0 of 0 correctable mechanically on your approval

paragraphs
81
images
0
tables
0
headings
6

Findings

These checks found nothing in this document. That is not a guarantee that the document is accessible.

Not determined from the file

  • reading order and screen-reader flow
  • whether an image the file does not mark as decorative is decorative
  • content in headers, footers, footnotes and endnotes
  • text placed over an image
  • text colour inherited from a paragraph or character style, or from the document theme

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. In a Word file 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. In a PowerPoint file it finds missing alternative text on pictures, missing slide titles, the presentation title, document language, and text contrast where the background is resolvable; it does not check table header rows or link text on slides. The body of a Word file and the slides of a deck are read; headers, footers, footnotes and speaker notes are not.

What this does not cover: automated structure checks find a subset of accessibility barriers. Reading order, whether an image the file does not mark as decorative 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.

UBA 2025-26 (child nutrition)

Published by California Dept of Education · src-docx-1-uba2025-26.docx

3 findings

UBA 2025-26 (child nutrition) · Word .docx · checked 2026-11-04

1 of 3 correctable mechanically on your approval

paragraphs
284
images
0
tables
4
headings
28

Findings

Info and Relationships

WCAG 2.1 1.3.1 · Likely (heuristic)

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

Info and Relationships

WCAG 2.1 1.3.1 · Measured

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 4 tables

Can be applied on your approval

Link Purpose (In Context)

WCAG 2.1 2.4.4 · Measured

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

Not determined from the file

  • reading order and screen-reader flow
  • whether an image the file does not mark as decorative is decorative
  • content in headers, footers, footnotes and endnotes
  • text placed over an image
  • text colour inherited from a paragraph or character style, or from the document theme
  • 60 coloured run(s) sit on a background that could not be resolved (cells with no explicit fill, text boxes, shading from a style, patterned fills, or a page colour the file does not display)

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. In a Word file 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. In a PowerPoint file it finds missing alternative text on pictures, missing slide titles, the presentation title, document language, and text contrast where the background is resolvable; it does not check table header rows or link text on slides. The body of a Word file and the slides of a deck are read; headers, footers, footnotes and speaker notes are not.

What this does not cover: automated structure checks find a subset of accessibility barriers. Reading order, whether an image the file does not mark as decorative 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.

Publication 331-149

Published by Washington State Dept of Health · src-docx-7-331-149.docx

2 findings

Publication 331-149 · Word .docx · checked 2026-11-04

1 of 2 correctable mechanically on your approval

paragraphs
198
images
1
tables
4
headings
0

Findings

Info and Relationships

WCAG 2.1 1.3.1 · Measured

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

Info and Relationships

WCAG 2.1 1.3.1 · Measured

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 4 tables

Can be applied on your approval

Not determined from the file

  • reading order and screen-reader flow
  • whether an image the file does not mark as decorative is decorative
  • content in headers, footers, footnotes and endnotes
  • text placed over an image
  • text colour inherited from a paragraph or character style, or from the document theme
  • 76 coloured run(s) sit on a background that could not be resolved (cells with no explicit fill, text boxes, shading from a style, patterned fills, or a page colour the file does not display)

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. In a Word file 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. In a PowerPoint file it finds missing alternative text on pictures, missing slide titles, the presentation title, document language, and text contrast where the background is resolvable; it does not check table header rows or link text on slides. The body of a Word file and the slides of a deck are read; headers, footers, footnotes and speaker notes are not.

What this does not cover: automated structure checks find a subset of accessibility barriers. Reading order, whether an image the file does not mark as decorative 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.

Interactive Lectures v2

Published by Carleton College, Science Education Resource Center · src-pptx-0-interactive_lectures_presentat.v2.pptx

2 findings

Interactive Lectures v2 · PowerPoint .pptx · checked 2026-11-04

1 of 2 correctable mechanically on your approval

slides
25
images
19
textRuns
159

Findings

Non-text Content

WCAG 2.1 1.1.1 · Measured

18 image(s) carry placeholder alternative text

pptx-s10-pic-1 'Picture 3': placeholder alt text "jackhillsgniess.jpg"; pptx-s10-pic-2 'Picture 4': placeholder alt text "lunarrock.jpg"; pptx-s10-pic-3 'Picture 5': placeholder alt text "shergottite9.jpg"; pptx-s10-pic-4 'Picture 6': placeholder alt text "SikhoteAlinMeteorite.jpg"; pptx-s11-pic-1 'Picture 5': placeholder alt text "element.gif"; pptx-s11-pic-2 'Picture 7': placeholder alt text "element.gif"; pptx-s11-pic-3 'Picture 8': placeholder alt text "element.gif"; pptx-s11-pic-4 'Picture 17': placeholder alt text "match.jpg"; pptx-s11-pic-5 'Picture 19': placeholder alt text "alphaparticle.gif"; pptx-s13-pic-1 'Picture 3': placeholder alt text "decaychart.jpg"; pptx-s13-pic-2 'Picture 2': placeholder alt text "decaychain.jpg"; pptx-s15-pic-1 'Picture 8': placeholder alt text "mandm.jpg" …

Where: 18 of 19 images

Can be applied on your approval

Page Titled

WCAG 2.1 2.4.2 · Measured

4 slide(s) have no title

Slides without a title: 13, 17, 18, 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

Not determined from the file

  • reading order within a slide
  • whether an image the file does not mark as decorative is decorative
  • table header rows and link text on slides
  • charts, SmartArt and other graphics that are not pictures
  • text placed over an image
  • animations and transitions
  • text colour inherited from the slide master, layout or theme
  • 4 coloured run(s) sit on a background that could not be resolved (theme colours, gradients, pictures, overlapping shapes or a background inherited from the layout)

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. In a Word file 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. In a PowerPoint file it finds missing alternative text on pictures, missing slide titles, the presentation title, document language, and text contrast where the background is resolvable; it does not check table header rows or link text on slides. The body of a Word file and the slides of a deck are read; headers, footers, footnotes and speaker notes are not.

What this does not cover: automated structure checks find a subset of accessibility barriers. Reading order, whether an image the file does not mark as decorative 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.

Natural Disasters unit presentation

Published by Carleton College, Science Education Resource Center · src-pptx-1-natural_disasters_unit_presentation_14558136752117405746.pptx

4 findings

Natural Disasters unit presentation · PowerPoint .pptx · checked 2026-11-04

2 of 4 correctable mechanically on your approval

slides
8
images
5
textRuns
42

Findings

Non-text Content

WCAG 2.1 1.1.1 · Measured

5 image(s) have no alternative text

pptx-s4-pic-1 'Shape 95': no alt text; pptx-s6-pic-1 'Shape 106': no alt text; pptx-s6-pic-2 'Shape 108': no alt text; pptx-s6-pic-3 'Shape 110': no alt text; pptx-s7-pic-1 'Shape 118': no alt text

Where: 5 of 5 images

Can be applied on your approval

Page Titled

WCAG 2.1 2.4.2 · Measured

2 slide(s) have no title

Slides without a title: 4, 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

Non-text Content

WCAG 2.1 1.1.1 · Measured

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

Page Titled

WCAG 2.1 2.4.2 · Measured

no presentation title set

The title is announced for the presentation.

Where: document properties

Can be applied on your approval

Not determined from the file

  • reading order within a slide
  • whether an image the file does not mark as decorative is decorative
  • table header rows and link text on slides
  • charts, SmartArt and other graphics that are not pictures
  • text placed over an image
  • animations and transitions
  • text colour inherited from the slide master, layout or theme
  • 4 coloured run(s) sit on a background that could not be resolved (theme colours, gradients, pictures, overlapping shapes or a background inherited from the layout)

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. In a Word file 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. In a PowerPoint file it finds missing alternative text on pictures, missing slide titles, the presentation title, document language, and text contrast where the background is resolvable; it does not check table header rows or link text on slides. The body of a Word file and the slides of a deck are read; headers, footers, footnotes and speaker notes are not.

What this does not cover: automated structure checks find a subset of accessibility barriers. Reading order, whether an image the file does not mark as decorative 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