When this tool is useful
Finding basic metadata and tag-tree gaps before manual keyboard, screen-reader, visual, semantic, and formal conformance testing.
How local processing works
The preflight checks Catalog Lang, a non-empty title, DisplayDocTitle, MarkInfo Marked, StructTreeRoot, ParentTree, Alt text on reached Figure elements, and TU alternate names on reached top-level form fields.
How to use it
- Prepare a safe working copy: Keep every source unchanged and review the supported input, controls, and limits before processing. Finding basic metadata and tag-tree gaps before manual keyboard, screen-reader, visual, semantic, and formal conformance testing.
- Process locally: Run the documented operation in this browser and stop if an unsupported structure is reported. The preflight checks Catalog Lang, a non-empty title, DisplayDocTitle, MarkInfo Marked, StructTreeRoot, ParentTree, Alt text on reached Figure elements, and TU alternate names on reached top-level form fields.
- Download and verify: Test the document with keyboard-only navigation and representative screen readers, inspect tags and reading order manually, run a recognized validator, and include disabled users in acceptance testing.
Important limitations
This is not accessibility certification or a WCAG, PDF/UA, Section 508, screen-reader, or keyboard conformance result. Reading order, semantics, headings, tables, link purpose, contrast, language changes, complete alternatives, and real user experience are not judged.
Verify the downloaded result
Test the document with keyboard-only navigation and representative screen readers, inspect tags and reading order manually, run a recognized validator, and include disabled users in acceptance testing.
Private by design
Your files stay in this browser. The tool does not upload the source or output to our servers.
Questions and answers
When is this tool useful?
Finding basic metadata and tag-tree gaps before manual keyboard, screen-reader, visual, semantic, and formal conformance testing.
What does the browser actually do?
The preflight checks Catalog Lang, a non-empty title, DisplayDocTitle, MarkInfo Marked, StructTreeRoot, ParentTree, Alt text on reached Figure elements, and TU alternate names on reached top-level form fields.
Which limits must I understand?
This is not accessibility certification or a WCAG, PDF/UA, Section 508, screen-reader, or keyboard conformance result. Reading order, semantics, headings, tables, link purpose, contrast, language changes, complete alternatives, and real user experience are not judged.
How should I verify the result?
Test the document with keyboard-only navigation and representative screen readers, inspect tags and reading order manually, run a recognized validator, and include disabled users in acceptance testing.