Accessibility checker

Check your website for accessibility issues

Accessibility problems are rarely deliberate. They are a contrast ratio nobody measured, a button that is really a div, a form field with no label, a focus outline someone removed for aesthetic reasons. VeriFixScan checks your pages for the barriers that automated testing can reliably detect, and reports the elements responsible.

What automated checking can and cannot find

Automated tests reliably catch a meaningful share of accessibility problems — missing alternatives, invalid ARIA, insufficient contrast, unlabelled controls, broken focus order. They cannot judge whether alternative text is meaningful, whether a page makes sense read aloud, or whether a workflow is usable with a screen reader. Treat the report as the floor, not the ceiling: fix what it finds, then test with real assistive technology.

Measured on the rendered page, not guessed from markup

Contrast is computed against the real background an element sits on, focus visibility is observed on interactive elements, and tab traversal is actually performed to find focus traps and broken ordering. Checks that need a browser run in one, because a static reading of the HTML would either miss these or report them wrongly.

Mobile accessibility is part of it

Touch target size and spacing, rendered text size and line height, and whether the mobile menu toggle is wired up for assistive technology are measured on a phone-sized screen. A site can be perfectly accessible on a desktop and unusable on a phone.

On compliance

VeriFixScan helps identify accessibility issues. It does not certify conformance with WCAG, the European Accessibility Act, Section 508 or any other standard, and no automated tool honestly can. What it gives you is a concrete list of things to fix, which is what a real conformance effort starts from.

The accessibility checks that run

Each reports the elements it found the problem on, so a finding can be located and fixed.

  • Image alternatives

    Images carry an alt attribute.

  • Colour contrast

    Contrast ratio between text and its real background.

  • Semantic landmarks

    Presence of the document landmarks screen readers navigate with.

  • Keyboard navigation

    Tab traversal of interactive elements, focus order and keyboard traps.

  • Visible focus

    Focus indicator really visible on interactive elements.

  • Interactive elements

    Interactive elements use a real interactive tag and expose an accessible name.

  • ARIA validity

    ARIA attributes and roles are spelled correctly and carry a value.

  • ARIA references

    aria-labelledby, aria-controls and aria-describedby point at elements that exist.

  • Form error handling

    Signs that validation errors are announced to assistive technology.

  • Form autocomplete

    Fields collecting personal data expose the matching autocomplete token.

  • Skip link

    A link allowing keyboard users to skip repeated navigation.

  • Iframe titles

    Every embedded frame carries a descriptive title.

  • Touch targets

    Size and spacing of interactive elements measured on a touch screen.

Automated accessibility testing finds a portion of the barriers on a site. It is a starting point for a conformance effort, not a substitute for testing with assistive technology and with disabled users.

Run a free scan

Enter your website address and VeriFixScan analyses it straight away. No account, no installation, nothing to add to your site.

Frequently asked questions

How do I check my website's accessibility?
Run a scan and read the accessibility findings. They report contrast failures, missing alternatives, invalid ARIA, unlabelled controls and focus problems, with the elements responsible.
Does this make my site WCAG compliant?
No. It helps identify accessibility issues so you can fix them. Conformance is a judgement about your whole site and cannot be certified by an automated tool.
Is colour contrast really measured?
Yes, against the real background an element renders on rather than the value declared in the stylesheet, which is often not the same thing.
Does it test keyboard navigation?
Yes. Tab traversal is performed on the rendered page to find focus traps, broken ordering and interactive elements that cannot be reached.
What about accessibility on mobile?
Touch target size and spacing, text size and the mobile menu's assistive-technology wiring are checked on a phone-sized screen.

Keep looking

This page in other languages