HTML Accessibility static check
Perform a basic accessibility audit on local HTML, checking alt, label, heading hierarchy, duplicate id, and empty controls.
How to use HTML accessibility static checking
HTML Accessibility static checking processes input only in the current browser; it does not upload, connect to the internet, or save user data.
Input content
Paste or select a local HTML file, maximum 512 KiB.
Select a processing method
Run static rule checks and display issues by line or node.
Check and export
Copy or download the inspection report, then fix each issue against the actual page.
Limitations and Notes
- Does not load external resources, is not a complete WCAG certification, and does not simulate all assistive technologies.
- Passing static checks does not mean the user experience is good; keyboards, screen readers, and real browsers still need to be tested.
- The tool only provides locally processed results; important configurations, secrets, documents, and published content must still be reviewed in the target environment.
FAQ
Will the input be uploaded to a server?
No. The page only uses browser memory, the local file API, and local resources already provided with the site.
Does checking whether it represents complete conformance to WCAG?
No. The tool covers only a set of local static rules and cannot replace a complete audit and real-user testing.
Why do the results still require manual review?
Edge-case syntax, regional standards, third-party readers, and target runtime environments may differ; the tool does not replace final validation.