Skip to content
https://ncsc.gov.uk

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
46
GRADE
F
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
Heading Hierarchy
Action
46 headings, 6 skip(s)
FIX
46 headings, 6 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Advice & guidance
  • H4 Find information for... skipped
  • H4 Popular topics
  • H4 Other resources
  • H2 Respond to a cyber attack
  • H4 Affecting you or your family skipped
  • H4 Affecting your small business
  • H4 Affecting your organisation
  • H2 Find a product or service
  • H4 In this section skipped
  • H4 Useful links
  • H2 Education & skills
  • H4 Find information for... skipped
  • H4 Education & academia resources
  • H4 Industry & skill resources
  • H2 News
  • H4 In this section skipped
  • H4 Stay up to date
  • H2 Search
  • H3 Popular Searches
  • H1 The National Cyber Security Centre
  • H4 Experienced a cyber attack? skipped
  • H2 Featured
  • H3 Cyber chief: UK faces "perfect storm" for cyber security
  • H3 Preparing for severe cyber threat: why leaders must act now
  • H3 New cross domain guidance for government, industry and the wider security community
  • H2 CYBERUK returns to Glasgow
  • H3 Advice for sole traders and small organisations to respond to cyber attacks
  • H3 Advice for medium to large organisations to help respond to a cyber incident
  • H3 Advice for individuals to respond to an online scam or cyber attack
  • H2 Find guidance and resources for . . .
  • H2 Popular content for organisations
  • H3 Cyber Assessment Framework
  • H3 Early Warning
  • H3 Cyber Security Toolkit for Boards
  • H2 Cyber criminals can find your business anywhere
  • H2 Popular content for you & your family
  • H3 Recovering a hacked account
  • H3 Managing your passwords
  • H3 Data breaches: guidance for individuals and families
  • H2 Free cyber security toolkit
  • H2 Popular topics
  • H2 Follow us
  • H2 About this website
  • H2 Contact the NCSC
  • H2 Useful links

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
6 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Alt Text Quality
Action
15 of 42 images have issues
REVIEW
15 of 42 images have issues
Critical::
14 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
1 image(s) with generic alt text
Info::
1 image(s) with alt text over 125 characters
Info::
11 decorative image(s) correctly marked
Info::
15 image(s) with good alt text
42 images 15 good alt text 11 decorative 1 generic 14 missing
IssueCount
missing14 image(s)
generic1 image(s)
too long1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

C
Form Accessibility
Action
4 of 10 controls have issues
REVIEW
4 of 10 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">
Info::
6 control(s) properly labeled
10 controls
6 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
#CybotCookiebotDialogBodyLevelButtonNecessarycheckboxNecessaryfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencescheckboxPreferencesfor/id
#CybotCookiebotDialogBodyLevelButtonStatisticscheckboxStatisticsfor/id
#CybotCookiebotDialogBodyLevelButtonMarketingcheckboxMarketingfor/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformationcheckboxDo not sell or share my personal informationfor/id
#global-searchsearchPlease enter a search termfor/id
#CybotCookiebotDialogBodyLevelButtonStatisticsInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonMarketingInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonNecessaryInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonPreferencesInlinecheckbox(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

0 pass 20 fail WCAG AA
h2 Advice & guidance
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Respond to a cyber attack
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Find a product or service
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Education & skills
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 News
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Search
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 CYBERUK returns to Glasgow
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Find guidance and resources for . . .
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Popular content for organisations
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Cyber criminals can find your business a…
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Popular content for you & your family
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Free cyber security toolkit
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Popular topics
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Follow us
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 About this website
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Contact the NCSC
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Useful links
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Popular Searches
1.76:1
#000000
on
#373737
needs 3.0:1 (large text)
19px · bottom of viewport
title The National Cyber Security Centre | Nat…
1.05:1
#000000
on
#030816
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Advice & guidance1.76:13.0:1
#000000
#373737
Fail
h2 Respond to a cyber a…1.76:13.0:1
#000000
#373737
Fail
h2 Find a product or se…1.76:13.0:1
#000000
#373737
Fail
h2 Education & skills1.76:13.0:1
#000000
#373737
Fail
h2 News1.76:13.0:1
#000000
#373737
Fail
h2 Search1.76:13.0:1
#000000
#373737
Fail
h2 Featured1.76:13.0:1
#000000
#373737
Fail
h2 CYBERUK returns to G…1.76:13.0:1
#000000
#373737
Fail
h2 Find guidance and re…1.76:13.0:1
#000000
#373737
Fail
h2 Popular content for …1.76:13.0:1
#000000
#373737
Fail
h2 Cyber criminals can …1.76:13.0:1
#000000
#373737
Fail
h2 Popular content for …1.76:13.0:1
#000000
#373737
Fail
h2 Free cyber security …1.76:13.0:1
#000000
#373737
Fail
h2 Popular topics1.76:13.0:1
#000000
#373737
Fail
h2 Follow us1.76:13.0:1
#000000
#373737
Fail
h2 About this website1.76:13.0:1
#000000
#373737
Fail
h2 Contact the NCSC1.76:13.0:1
#000000
#373737
Fail
h2 Useful links1.76:13.0:1
#000000
#373737
Fail
h3 Popular Searches1.76:13.0:1
#000000
#373737
Fail
title The National Cyber S…1.05:14.5:1
#000000
#030816
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV "Additional links" MAIN CONTENTINFO footer

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

A
Lighthouse Accessibility Audits
Score 91/100 — 4 failing, 26 passed
PASS
91

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Experienced a cyber attack? div.bg-notification > div.c-container > a.flex > h4.mb-0

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Experienced a cyber attack? div.bg-notification > div.c-container > a.flex > h4.mb-0

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.px-fl-sm > div.relative > img.w-32 div > div.px-fl-sm > div.relative > img.w-32
div > div.px-fl-sm > div.relative > img.w-32 div > div.px-fl-sm > div.relative > img.w-32
div > div.px-fl-sm > div.relative > img.w-32 div > div.px-fl-sm > div.relative > img.w-32
div > div.px-fl-sm > div.relative > img.w-32 div > div.px-fl-sm > div.relative > img.w-32
div > div.px-fl-sm > div.relative > img.w-32 div > div.px-fl-sm > div.relative > img.w-32
div > div.px-fl-sm > div.relative > img.w-32 div > div.px-fl-sm > div.relative > img.w-32
div.c-container > div.grid > div.relative > img.w-full div.c-container > div.grid > div.relative > img.w-full
div.c-container > div.grid > div.relative > img.w-full div.c-container > div.grid > div.relative > img.w-full
div.c-container > div.grid > div.relative > img.w-full div.c-container > div.grid > div.relative > img.w-full
div.c-container > div.grid > div.relative > img.w-full div.c-container > div.grid > div.relative > img.w-full
div.c-container > div.grid > div.relative > img.w-full div.c-container > div.grid > div.relative > img.w-full
div.c-container > div.grid > div.relative > img.w-full div.c-container > div.grid > div.relative > img.w-full
div.c-container > div.grid > div.relative > img.w-full div.c-container > div.grid > div.relative > img.w-full
div.c-container > div.grid > div.relative > img.w-full div.c-container > div.grid > div.relative > img.w-full

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NEW TODAY NEWS Cyber chief: UK faces "perfect storm" for cyber security As the… div.py-fl-lg > div.mt-fl-sm > article.c-teaser > a.h-full
BLOG POST Preparing for severe cyber threat: why leaders must act now A call t… div.mt-fl-sm > div.h-full > article.@container > a.w-full
NEW TODAY BLOG POST New cross domain guidance for government, industry and the … div.mt-fl-sm > div.h-full > article.@container > a.w-full
GUIDANCE Cyber Assessment Framework The CAF is a collection of cyber security … div.py-fl-lg > div.grid > article.c-teaser > a.h-full
GUIDANCE Cyber Security Toolkit for Boards Resources to help Boards implement … div.py-fl-lg > div.grid > article.c-teaser > a.h-full
GUIDANCE Recovering a hacked account A step by step guide to recovering online… div.py-fl-lg > div.grid > article.c-teaser > a.h-full
GUIDANCE Managing your passwords Why you should use a password manager to ‘rem… div.py-fl-lg > div.grid > article.c-teaser > a.h-full
GUIDANCE Data breaches: guidance for individuals and families How to protect y… div.py-fl-lg > div.grid > article.c-teaser > a.h-full
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback