Try It

Open a demo page, run Scan Page in the extension, and inspect the result. Many fixtures contain intentional accessibility issues so you can see how a finding appears.

Quick Start

Your first scanStart with a page containing intentional accessibility issues.Visual overlaysFind violations, tab order, and focus gaps on the page.Site crawlFollow links from a hub to five linked pages.

Validate the extension with a demo profile

Download a profile, open its matching demo page, then choose Test configuration → Form → Import JSON file in the extension. These profiles target this website. Use the profile builder to change the target for a local copy.

Core scan profile · Core fixture: scan for missing image descriptions, an unnamed button, and an unlabelled input.
Rule override profile: scan the core fixture again; the axe image-alt finding should disappear. Other rules remain enabled.
Crawl profile · Crawl hub: visit the hub and five linked pages, staying inside that path.
Responsive profile · Responsive fixture: request 375, 768, and 1280 px; check measured widths and window restoration.
Delayed content profile · Delayed fixture: wait for the table rows before scanning the page.

Check bad-config recovery

After applying the core profile, try the deliberately invalid JSON syntax, schema version, and unknown field files. Each should show an error and preserve the active profile. The Crawl + multi-viewport profile can be imported, but must explain why scanning is blocked. Import the core profile again to recover.

Check named findings and affected elements. Older demo guidance and total counts are illustrative; automated coverage is partial, and a scan does not prove WCAG conformance.

Explore by Category

Browse grouped demo pages for common interface patterns. Each fixture includes guidance on what to test.

Core scanningPage scan, overlays, tab order, viewport differences, crawl, and ARIA Page rulesLogin, interaction, and delayed content fixtures NavigationMenus, breadcrumbs, sidebars, tabs, and pagination FormsValidation, wizards, dates, files, search, and checkout Modals and overlaysDialogs, consent, lightboxes, and notifications Data displayTables, cards, scrolling, and accordions MediaVideo, images, and audio controls Interactive widgetsAutocomplete, sliders, selects, tooltips, and toggles LayoutSticky headers, skip links, footers, and responsive sidebars E-commerceProduct cards, carts, checkout, and price filters

What to look for

After scanning

Open a finding and inspect its affected elements.
Use Highlight or the Violations overlay to locate an element.
Check reading and keyboard order separately.

Other modes

Use Scan Movie to watch focusable elements after a scan.
Try the viewport fixture to see width-specific results.
Use Site Crawl on the linked mini-site.

Next steps

All demo pages Getting Started Build a scan profile