Accessibility Audit Example: 12 WCAG 2.1 Violations Found

The most important thing to understand about any automated accessibility report, including this one: an automated tool can only detect a minority of WCAG failures. Industry testing consistently puts the figure at somewhere around a third. The rest — whether your alt text is meaningful, whether the focus order makes sense, whether an error message actually explains the error — cannot be determined by a machine.

So a score of 71/100 tells you there are at least twelve problems. It does not tell you there are only twelve. And a hypothetical score of 100 would not mean the site is accessible — it would mean the machine-checkable failures are cleared, which is the beginning of the work rather than the end of it.

The report separates violations into three levels, and they are frequently misread as "critical, important, nice-to-have". That is roughly true of the impact, but the levels actually describe conformance tiers, and only two of them are usually relevant.

AA is the target. The 2 Level AAA findings in this report are informational — they are not a failure against the standard almost anyone is held to, and chasing them before the Level A items are fixed is the wrong order. The 4 Level A violations are the ones that make the page genuinely unusable for somebody.

The report flags footer links at 3.8:1 against a 4.5:1 minimum. That threshold is not arbitrary and it is not the only one — there are three, and using the wrong one is the most common contrast mistake:

Two consequences people miss. First, 1.4.11 covers the border of your input fields and the outline of your buttons — a beautifully subtle 1px grey border on a white field is very frequently a failure, and no contrast checker aimed at text will catch it.

Second, placeholder text is text. Designers habitually set it to a pale grey because it is "only a hint" — but it is a hint that some users cannot read, and if it is the only label (see below), it is the only thing telling them what the field is for.

The report finds four inputs with placeholder text and no <label>. This is the single most common accessibility defect on the web, and it is worth understanding why it is critical rather than cosmetic:

• The placeholder disappears when you start typing. Anybody who is interrupted mid-form now has no idea what they were entering. This affects everyone, not just screen reader users.
• Screen readers announce the field type, not the purpose. "Edit text, blank" is what the user hears.
• You lose the click target. A properly associated <label> focuses its input when clicked — a real usability benefit for anyone with a motor impairment, and for anyone on a phone.
• Autofill degrades. Browsers use labels and autocomplete attributes to work out what a field wants.

Put the mouse down. Press Tab. Work through the whole page using only the keyboard, and watch for these five things — every one of them is a WCAG failure that the majority of automated reports will not catch:

• Can you see where you are? If the focus ring vanishes, you have found the outline: none the report flagged. Navigating a page you cannot see the focus on is impossible.
• Does the focus order follow the visual order? A CSS layout change that reorders elements visually without reordering them in the DOM produces a tab sequence that jumps around the screen.
• Can you escape? Open the modal. Does focus move into it? Does Esc close it? Does focus return to the button that opened it? A modal you can tab out of, into a page you cannot see, is a trap.
• Can you reach everything? Custom dropdowns, carousels and tabs built from <div>s are frequently unreachable by keyboard entirely.
• Is there a skip link? Tab once from the top of the page. If nothing appears, you have confirmed the 2.4.1 failure — and every keyboard user is tabbing through all fourteen navigation items on every single page.

Then set the browser zoom to 200% (WCAG 1.4.4) and narrow the window to 320px (1.4.10). Content must reflow without horizontal scrolling and nothing may be cut off. These two checks take a minute and find layout failures that no report will.

This is not a rhetorical overlap. Several items in this report are simultaneously WCAG failures and SEO defects, fixed by the same edit:

The reason is structural rather than coincidental: a screen reader and a crawler are both consuming your page as a document rather than a picture. Both need the meaning to be in the markup. A page built so that meaning is conveyed only by colour, position or visual styling is illegible to both — and increasingly, that includes the answer engines, which parse rather than render.

The report finds three images with no alt attribute. Fixing that is the easy part. Two subtler mistakes follow immediately and no automated checker catches either:

Accessibility is not solely a quality question, and the obligations have tightened:

• UK — Equality Act 2010. Service providers must make reasonable adjustments. It applies to websites, and it applies to private businesses.
• UK public sector. Public bodies are required to meet WCAG 2.1 Level AA and to publish an accessibility statement.
• EU — the European Accessibility Act. Its requirements began applying in June 2025 and reach a broad range of consumer-facing digital products and services, including e-commerce, sold into the EU. UK businesses selling into Europe are not outside it.
• US — the ADA. A large and growing volume of litigation, in which WCAG 2.1 AA is the standard courts routinely reference.

General information, not legal advice. The obligations that apply to a given business depend on its sector, size and markets. The practical point stands regardless: the standard being referenced, in every one of these regimes, is the same one this report measures against.

Why does accessibility matter for SEO?

Accessibility and SEO overlap significantly. Many accessibility fixes — alt text, heading structure, descriptive links, landmark regions — are also SEO best practices. Google's crawlers behave similarly to screen readers. Improving accessibility often directly improves SEO scores. Additionally, inaccessible sites face legal risk under the Equality Act 2010 (UK) and ADA (US).

What is WCAG 2.1?

WCAG (Web Content Accessibility Guidelines) 2.1 is the international standard for web accessibility, published by the W3C. It defines requirements at three levels: A (minimum), AA (recommended for most sites) and AAA (enhanced). Most organisations target Level AA compliance. The aiwebpageseo Accessibility Checker tests against all Level A and AA criteria.

What is a skip link?

A skip link is a hidden link at the top of the page (visible on keyboard focus) that lets keyboard users jump directly to the main content, bypassing navigation. Without a skip link, keyboard users must tab through every navigation item on every page load. It is a WCAG 2.4.1 Level A requirement.

Does a perfect automated score mean my site is accessible?

No. Automated tools detect only a minority of WCAG failures — commonly estimated at around a third. Whether alt text is meaningful, whether the focus order makes sense, whether an error message actually explains the error: none of these can be determined by a machine. A clean automated report clears the machine-checkable failures, which is where the work begins rather than where it ends.

Why is using a placeholder instead of a label a critical failure?

Because the placeholder disappears the moment someone starts typing, so anyone interrupted mid-form no longer knows what they were entering — which affects every user, not only screen reader users. Screen readers announce the field type rather than its purpose, the label's click target is lost, and browser autofill degrades. A native label element is preferable to an aria-label wherever it is possible: it is visible, clickable, and cannot silently override the accessible name.

Which contrast ratio applies to my buttons and input borders?

3:1, under WCAG 1.4.11, which covers user interface components and graphical objects. This is separate from the 4.5:1 minimum for normal text and the 3:1 minimum for large text (24px, or 18.66px bold). A subtle 1px grey border on a white input field is very often a failure, and a contrast checker aimed only at text will not catch it.

Do accessibility overlay widgets make a site compliant?

No. Widgets promising WCAG compliance from a single line of JavaScript do not achieve conformance, and their claims have attracted significant legal action. They cannot repair a missing label or a broken focus order, because those defects live in the page's own markup. There is no plugin that makes an inaccessible site accessible.