Accesserty DevCheck
Run axe-core scans, simulations, AI-assisted semantic review, and PDF structure checks on the page in front of you, across local, staging, authenticated, and production environments.
Accessibility checks should not belong to one role
DevCheck does not replace accessibility expertise. It gives more team members a practical first step when they notice a concern.
You can inspect public pages, local builds, staging sites, authenticated flows, interaction states, and PDF documents without sending the page to an external URL scanner.
Most checks run locally in the browser. Only the optional AI Semantic Check sends extracted page text and selected images to Google Gemini after the user explicitly starts it.
What you can check first
These checks are meant to surface common risks early and make issues easier to discuss.
Automated accessibility scan
Use axe-core to check machine-detectable WCAG A/AA and best-practice issues, then locate affected page elements.
Visual and sensory scenarios
Switch color vision, text spacing, visual field loss, presbyopia, myopia, and cataract modes to see whether information remains readable and understandable.
Interaction states and focus
Check forms, dialogs, authenticated flows, and dynamic content after they appear in the browser.
AI-assisted semantic check
Review semantic quality that rule-based tools often cannot judge, such as whether link text explains its destination, language changes are marked, and image alt text matches the actual image, with suggested alt text improvements.
PDF structure signals
Inspect basic document signals such as language, tags, links, images, form fields, and bookmarks.
Who should use DevCheck?
- Designers
Use simulations for color vision, text spacing, visual conditions, and touch targets as concrete input for design reviews and cross-functional discussion.
- PMs and product teams
Use scans and simulations to turn a vague concern into evidence the team can discuss, track, and assign.
- Engineers and QA
Run scans and simulations in local builds, staging pages, authenticated flows, and regression checks so issues are found earlier and re-tested faster.
It does not replace a full audit
DevCheck is useful for first checks, issue discussion, and re-testing fixes. Formal accessibility audits still require human judgment, keyboard testing, assistive technology testing, and contextual review.
AI Semantic Check provides assistive suggestions, not a compliance guarantee. Do not use it on confidential or unauthorized pages, and review suggestions before applying them.
How to start checking
Install the Chrome extension, then open the page you want to inspect.
- Step 1. Install Accesserty DevCheck
Install the extension from the Chrome Web Store.
- Step 2. Open the page you want to check
It can be a public page, local build, staging site, authenticated flow, interaction state, or PDF document.
- Step 3. Run a scan, simulation, or semantic check
Run an automated scan, visual simulation, AI semantic check, or PDF structure signal check depending on the task.
Install Accesserty DevCheck
Frequently asked questions
Accesserty DevCheck is a free, in-browser web accessibility checker that combines axe-core automated scans, WCAG-related issue location, sensory simulation, AI semantic checks, image alt suggestions, and PDF structure signals so any role can find barriers earlier.
Yes, it is free. Install the browser extension and start checking — no paid plan required.
Yes. DevCheck axe-core scans, simulations, and PDF checks run inside your own browser, so you do not have to send pages to an external URL scanner. The optional AI Semantic Check sends extracted text and selected images to Google Gemini only after you start it.
It is for cross-functional roles — product, design, QA, engineering, content and operations — so more people can run a first check when they spot a risk. It is meant to bring that first check earlier, not to replace accessibility experts or real-user testing.