ai-ops

Does a perfect accessibility score mean your site is accessible?

Five accessibility scanners, the rule source of each read line by line, and what they actually check for moving content. Plus the five-minute check and the manual pass that cover the gap.

Open Markdown version

Open any marketing homepage and watch it for ten seconds without touching anything. Most pages come back with a hero slider, a logo band, a counter ticking up to 500, or a video behind the headline. Now open the last accessibility report anybody ran on it. The motion rules reviewed below check for obsolete elements or a legacy CSS blink value, and Lighthouse includes neither element rule.

What do accessibility scanners actually detect for moving content?

Two obsolete HTML elements, <marquee> and <blink>, and in two of the five engines the legacy CSS value text-decoration: blink. Lighthouse’s accessibility set contains neither element rule. None of these rules asks whether something on the page is moving, which is what the criterion is about.

Engine Rule tagged to WCAG 2.2.2 What the source actually matches Catches a slider or a logo band
axe-core 4.14.0 marquee, blink "selector": "marquee" and "selector": "blink" No
Pa11y (HTML_CodeSniffer, default runner) sniff 2_2_2 a <blink> element, or a computed text-decoration containing blink No
Lighthouse 13.5.0 none the 76 accessibility audits in its default config, no marquee or blink audit among them No
IBM Equal Access marquee_elem_avoid, blink_css_review context: "dom:marquee", and the literal string text-decoration:blink in style elements and inline style attributes No
ESLint eslint-plugin-astro jsx-a11y/no-distracting-elements <marquee> and <blink> only No

Every row comes from the tool’s own rule source, read at the version named. A slider, a logo band, a background video and a counter are none of those element names, whichever technique builds them, so none is matched.

The element rules reviewed here look for two obsolete element names, marquee and blink. The things that move on a homepage, a slider, a logo band, a background video, a scroll reveal and animated counters, are neither, so no motion rule reaches them. Moving parts need a check by hand.

Five details are worth knowing before you rely on any of them.

  • axe-core’s marquee rule is one element selector plus an on-screen check, and blink.json has the same shape with the element name swapped. Of the 105 rules the library registers, exactly two carry the wcag222 tag: those two.
  • Pa11y’s default engine does emit a generic notice reminding a human to check moving content, and pa11y suppresses it: “Issues with a type of notice are not directly actionable and so they are excluded by default”. The computed text-decoration: blink finding is a warning, and warnings are ignored by default too. For this sniff, a default run reports the literal blink error.
  • IBM’s blink_css_review runs against dom:style, dom:*[style] and tests for the literal string text-decoration:blink. A linked stylesheet is never opened, and the same declaration with a space after the colon does not match.
  • The ESLint rule is closed by design: “You cannot add any additional elements than what is offered, as the schema is only valid with the provided enumerated list”. It reads markup and never opens a stylesheet.
  • Astro’s dev toolbar audit, a sixth data point, hard-codes the identical pair: const a11y_distracting_elements = ['blink', 'marquee'];.

Each of these tools does what it says on the box. axe-core’s design goal is “zero false positives (bugs notwithstanding)”, the right trade for anything allowed to fail a build. The gap is structural and sits in the same place for all five, which is how a page with a band animating in its built HTML scores 100.

How do you check your own site for the defect no scanner sees?

Watch the page, list what moves, and test each item against the four conditions of WCAG 2.2.2. It takes about five minutes per page and needs nothing beyond a browser. What you are hunting for, all of it stock equipment on a marketing site:

  • Carousels and auto-advancing hero sliders
  • Scrolling logo and testimonial bands
  • Video that autoplays behind a headline
  • Parallax and scroll-triggered reveals
  • Animated counters

Then work each through these five steps.

  1. Load the page and watch it for ten seconds without touching anything. Write down everything that moves on its own, then scroll down and watch again. W3C’s Understanding document for 2.2.2 counts “scrolling an element into view” as an indirect interaction, so motion that starts there still counts as starting automatically.
  2. Test each item against the four conditions of WCAG 2.2.2. All four must apply before the criterion bites:
    • It starts automatically, with no click from the user
    • It runs longer than five seconds
    • It sits alongside other content, so a full-screen splash animation is a different case
    • It is not essential to a task the user is performing
  3. Find an accessible way to pause, stop or hide the motion. A clearly labelled control on the page is the practical option, and W3C’s technique G4 also accepts a documented keyboard shortcut. Either way a reader has to find it and use it, so a control that only appears on hover is a poor choice.
  4. Reach it with the keyboard. Tab from the top of the page and confirm you can get to the mechanism and use it without a mouse. A pause button nobody can reach fails the same criterion it was built to satisfy.
  5. Confirm the motion stays stopped. If JavaScript reveals the control, check that it appears and works, because a script failure leaves the button invisible and the check passes on nothing. Use it, then watch the content while you carry on with the rest of the page. One spot check for a developer, and only for a CSS animation paused through animation-play-state: getComputedStyle(document.querySelector('.your-band')).animationPlayState should read paused. A video or a script-driven counter has to be watched instead.

The pass condition: every item on your list either fails at least one of the four conditions, or has a keyboard-reachable mechanism that verifiably stops it.

Those four conditions cover one branch of the criterion: moving, blinking and scrolling content. The other branch is information that updates itself, such as a live ticker. It has no five-second allowance, and it adds another option, letting the reader control how often it updates. An auto-advancing presentation can land in either branch, so test both.

To build the list faster, search your compiled stylesheet for infinite and animation:. Every hit is a candidate. There is a deterministic version of that tripwire: @double-great/stylelint-a11y ships a11y/media-prefers-reduced-motion, which flags unguarded animation and transition declarations, as in this example. Two unguarded selectors give two errors and exit code 2, enough to fail a commit:

1:1  ✖  Expected .logo-track is used with @media (prefers-reduced-motion)          a11y/media-prefers-reduced-motion
5:1  ✖  Expected .logo-track-reverse is used with @media (prefers-reduced-motion)  a11y/media-prefers-reduced-motion

A stylesheet search has a gap of its own, which is why step one is a pair of eyes rather than a grep. A <video> with autoplay is in the markup, and a counter animating to 500 is usually a script watching the viewport. Neither shows up in a stylesheet. Search the templates for autoplay and the scripts for anything that fires when an element scrolls into view, usually an intersection observer.

Be precise about what that buys you: a tripwire that sends a person to look, not a test for the mechanism a reader needs, which is in markup no stylesheet can see. It matches selector by selector, so a global block collapsing animation duration still errors on each unguarded selector.

The manual pass: six areas, 20 to 30 minutes

This layer covers the motion check plus five further areas that need manual checks, which is why a scan is a thin substitute for what a proper website audit actually surfaces. Work through it in order.

# Area Time What you do Pass condition
1 Keyboard traversal 10 min Tab through from the address bar. Links respond to Enter, buttons to Enter and Space, checkboxes to Space, radio groups to arrows, dialogs close on Escape and return focus to the opener Every interactive element is reachable and leavable with the keyboard alone (2.1.1 and 2.1.2, both Level A)
2 Focus visibility 3 min Tab down a long page and watch the focus indicator, including under a sticky header The indicator is visible on every focused element (2.4.7, AA), and the focused component is never entirely hidden by content you added (2.4.11, AA)
3 Zoom and reflow 3 min Set the viewport to 1280 CSS pixels wide and zoom to 400 percent, which leaves content about 320 CSS pixels wide. Reset zoom, then resize text alone to 200 percent At 400 percent zoom, content reflows without two-dimensional scrolling or loss of information or functionality, except individual items that need a two-dimensional layout. At 200 percent text size, no content or functionality is lost (1.4.10 and 1.4.4, both AA)
4 Motion 2 min The five-step check above Every moving item either fails one of the four conditions or has a keyboard-reachable mechanism that stops it. Content that updates itself is tested against the second branch (2.2.2, Level A)
5 Forms and errors 5 min Submit the contact form empty, then again with a badly formed email address Every field carries a visible label, and every error is described in text rather than by a red border alone (3.3.1 and 3.3.2, both Level A)
6 Structure 5 min Disable CSS and read the page top to bottom A practical checklist, not a complete statement of the requirements: exactly one <main>, all content inside a landmark, headings in order with no skipped levels, a skip link, and source order that still makes sense

Two habits keep this repeatable.

  • One page per template type. On a brochure site that is usually five: home, a service page, the blog index, one post and the contact form.
  • Record the date, the pages and the result. An undated pass is worth nothing three months later.

Start with keyboard navigation. A keyboard trap is a whole-page failure under WCAG Conformance Requirement 5, so a mobile menu that swallows focus takes down every page it appears on. In row six, a CSS grid is where the order you see and the order in the code drift apart.

The times add up to 28 minutes, so allow roughly half an hour for a first page and more for each further template. GOV.UK’s broader basic-check guidance says “It’s likely the checks will take at least a few days”.

What is a green accessibility report actually evidence of?

An automated report covers only the checks it runs, and a perfect score does not establish conformance. Lighthouse 13.5.0 lists 76 accessibility audits in its default config, and 18 carry a weight of zero, so they cannot move the number. Ten of the 18 are marked scoreDisplayMode: "manual": the tool names the check and leaves it to a person. The other eight are ordinary automated audits, among them empty-heading and td-has-header, which can come back failed while the score still reads 100.

The ten manual ones sit in a report you already generated.

  1. Interactive controls are keyboard focusable
  2. The page has a logical tab order
  3. Visual order on the page follows DOM order
  4. User focus is not accidentally trapped in a region
  5. The user’s focus is directed to new content added to the page
  6. Interactive elements indicate their purpose and state
  7. HTML5 landmark elements are used to improve navigation
  8. Offscreen content is hidden from assistive technology
  9. Custom controls have associated labels
  10. Custom controls have ARIA roles

Motion, zoom and reflow appear nowhere on that list. Three published figures set how much automation reaches, each with its caveat attached in the same breath.

Figure Source What it counts Caveat
57 percent of WCAG issues found automatically Deque, in the axe-core README issue instances A vendor claim about its own product. The underlying audit data is not published
Automated issues for 16 of the 50 Success Criteria under WCAG 2.1 AA Deque’s own coverage report success criteria with any automated coverage Same vendor, same report. That is 32 percent of criteria
The best of 13 tools found 40 percent of 142 planted barriers UK Government Digital Service accessibility tool audit deliberately planted barriers Last updated April 2018. Treat the ordering as informative and the percentages as stale

Which number you quote depends on the question. Issue-instance counts describe how many findings automation detects. Count criteria when somebody asks whether a site conforms, because a criterion with no automated coverage is one the tool says nothing about.

Automate what can be automated: those defects are the high-frequency ones a person stops noticing at five o’clock on a Friday. The rule for anything allowed to gate a deploy comes from content QA pipelines before you ship: same answer on the same input every time, against a rule set a person can read. Every engine above clears that bar. These motion checks do not establish whether a reader can stop the motion.

The reduced-motion answer that will cost somebody a compliance claim

Ask whoever maintains your site what stops the carousel. If the answer comes back as “the site respects reduced motion”, that answer is incomplete.

Technique C39, using the CSS prefers-reduced-motion query to prevent motion, says on its own W3C page: “This technique relates to 2.3.3 Animation from Interactions.” That criterion is Level AAA and covers motion triggered by user interaction, a different question from a band that starts on page load. C39 appears nowhere among the seven techniques W3C lists for 2.2.2. Two examples suitable for a scrolling band are G4, pausing and restarting content, and G186, a control in the page that stops moving content. Both describe something the reader can use.

So the reduced-motion query on its own does not establish that the carousel meets 2.2.2. Ship it, then answer the question the criterion asks: what can a reader who has set no preference do to stop this. Check the behaviour on the page, not the rule in the stylesheet.

Where this stops being only a quality question

For some sites this is now law. The European Accessibility Act arrived in Austria as the Barrierefreiheitsgesetz and has applied since 28 June 2025. Start with service scope and the microenterprise exemption. The rest belongs in a conversation with somebody qualified to have it.

The first test is the service. § 2 Abs 2 lists the consumer services the law covers, and it is a closed list: electronic communications, services giving access to audiovisual media services, named elements of air, bus, rail and ship passenger transport, consumer banking services, e-books and the software for them, and services in electronic commerce. Check whether your site provides one of those. The e-commerce entry is the one most marketing sites have to weigh, and § 3 Z 27 defines it as a service delivered electronically, at the individual request of a consumer, aimed at concluding a consumer contract. A payment button is not the deciding test.

The second test is the size. § 6 exempts Kleinstunternehmen that offer or provide services from the accessibility requirements for services, and § 3 Z 19 defines the term: a business employing fewer than ten people that either has an annual turnover of at most € 2 million or a balance sheet total of at most € 2 million. The headcount test and the money test both have to hold, so a business that reaches ten people crosses the line without anything on the website changing.

An in-scope provider that is not exempt also owes a statement about conformity. § 14 Abs 2 with Anlage 3 puts it in the terms and conditions or a comparable document, saying how the service meets the requirements, in a form that is itself accessible. No audit tool produces it for you.

What to do this week

Run the five-minute motion check on your homepage. It is the page most likely to carry a band, a slider or a hero video, and the one you can least afford to be wrong about. Content that moves on its own and meets all four conditions needs an accessible way to pause, stop or hide it, and your last green report said nothing about whether one exists.

Then put the six-area pass on a date. An automated layer keeps returning its green number on the days something is broken in a way that matters, because the audits that ran were never looking at the thing that broke. That pass is either scheduled and written down, or nobody is doing it. If you want it on a schedule somebody owns, that is what our fractional marketing engineer service exists to carry.

Essential Code is your Fractional Marketing Engineer: a small senior team that joins your marketing team and builds what your marketing plan needs.

How the service worksNot sure yet? Start with an auditOr email us directly