Skip to content
https://wikimediafoundation.org

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
6
REVIEW
6
PASS
12
INFO
0
Checks
24
12 PASS 6 REVIEW 6 FIX
D
Heading Hierarchy
Action
53 headings, 2 skip(s)
FIX
53 headings, 2 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
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.
  • H2 We are the non-profit organization behind Wikipedia.
  • H3 People
  • H3 Reports
  • H3 Careers
  • H3 Frequently asked questions
  • H2 Our technology supports the backbone of knowledge on the internet.
  • H3 Wikimedia projects
  • H3 Technology
  • H3 Public policy
  • H3 Closing knowledge gaps
  • H2 The more people take part, the better the internet’s knowledge gets.
  • H3 Donate
  • H3 Volunteer
  • H3 Advocate
  • H2 Stay up to date on our efforts to protect free knowledge.
  • H4 The Wikimedia Foundation files to protect open knowledge in New York Times v OpenAI case skipped
  • H4 OpenAI “rogue” agent activities found on Wikimedia projects
  • H4 Human knowledge at stake: Wikimedia Foundation makes its case at the United Nations General Assembly
  • H2 We fundopensupport protect fund opensupportprotecthuman knowledge
  • H2 Celebrate Wikipedia’s 25th birthday
  • H2 By the numbers
  • H2 Our work
  • H4 The Wikimedia Foundation files to protect open knowledge in New York Times v OpenAI case skipped
  • H4 OpenAI “rogue” agent activities found on Wikimedia projects
  • H4 Human knowledge at stake: Wikimedia Foundation makes its case at the United Nations General Assembly
  • H4 Wikimedia Foundation Statement on US staff unionization
  • H4 Wikimedia Foundation welcomes Rena Kokalari as new Chief People Officer
  • H4 Wikimedia Foundation Statement on US unionization request
  • H4 Paris hosts Wikimania 2026 as Wikipedia celebrates 25 years of free knowledge
  • H4 The cost of ‘free’: How Wikimedia Enterprise protects Wikipedia in the AI era
  • H4 Wikimedia Foundation Challenges UK Online Safety Act Regulations
  • H2 Built for people, by people
  • H3 Taufik Rosman
  • H3 Siobhan Leachman
  • H3 Armine Aghayan-Flisch
  • H3 Donatien Kangah
  • H3 Wilfredo Rodríguez
  • H3 Ellie Méndez
  • H3 Mónica Paola Bonilla-Parra
  • H3 Alberto Leoncio
  • H3 Alaa Najjar
  • H3 Nkem Osuigwe
  • H3 Ananya Mondal
  • H3 Netha Hussain
  • H3 Rosie Stephenson-Goodknight
  • H3 Andrew Lih
  • H2 Help expandhuman knowledge
  • H2 Donate
  • H2 Edit
  • H2 Participate
  • H2 Advocate
  • H2 Subscribe for news
  • H2 Photo credits

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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
Tabindex Anti-Patterns
Action
0 positive, 14 -1-on-focusable
FIX
0 positive, 14 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
D
Tap Target Adequacy
Action
19 tap target(s) too small or too close together
FIX
19 tap target(s) too small or too close together
Warning::
19 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Form Accessibility
Action
3 of 8 controls have issues
REVIEW
3 of 8 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="mailchimp_sf_alt_email">; <input type="submit" name="mc_signup_submit" id="mc_signup_submit_c69c060af4_12">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="number" name="preSelect">
Info::
5 control(s) properly labeled
8 controls
5 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#wp-block-search__input-6searchSearchfor/id
frequencyradionone
frequencyradionone
#mc_mv_EMAIL_10textEmail Address*for/id
#mc_mv_OPTIN_11_0radioYes, I would like to receive updates, news, and promotional emails from the Wikimedia Foundation. I understand I can unsubscribe at any time.for/id
preSelectnumber(2.75)placeholder only
mailchimp_sf_alt_emailtext(none)none
#mc_signup_submit_c69c060af4_12submit(none)none

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

<input type="text" name="mailchimp_sf_alt_email">; <input type="submit" name="mc_signup_submit" id="mc_signup_submit_c69c060af4_12">

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

Placeholder text disappears on focus and is not a reliable label.

<input type="number" name="preSelect">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found – Wikimedia Foundation ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA
h2 The more people take part, the better th…
2.94:1
#000000
on
#0C57A8
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Stay up to date on our efforts to protec…
2.94:1
#000000
on
#0C57A8
needs 3.0:1 (large text)
24px · bottom of viewport
h2 human knowledge
2.94:1
#000000
on
#0C57A8
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Celebrate Wikipedia’s 25th birthday
2.94:1
#000000
on
#0C57A8
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 By the numbers
2.94:1
#000000
on
#0C57A8
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our work
2.94:1
#000000
on
#0C57A8
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Built for people, by people
2.94:1
#000000
on
#0C57A8
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Help expand
2.94:1
#000000
on
#0C57A8
needs 3.0:1 (large text)
24px · bottom of viewport
h2 human knowledge
2.94:1
#000000
on
#0C57A8
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Subscribe for news
2.94:1
#000000
on
#0C57A8
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Photo credits
2.94:1
#000000
on
#0C57A8
needs 3.0:1 (large text)
24px · bottom of viewport

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 We are the non-profi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our technology suppo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The more people take…2.94:13.0:1
#000000
#0C57A8
Fail
h2 Stay up to date on o…2.94:13.0:1
#000000
#0C57A8
Fail
h2 human knowledge2.94:13.0:1
#000000
#0C57A8
Fail
h2 Celebrate Wikipedia…2.94:13.0:1
#000000
#0C57A8
Fail
h2 By the numbers2.94:13.0:1
#000000
#0C57A8
Fail
h2 Our work2.94:13.0:1
#000000
#0C57A8
Fail
h2 Built for people, by…2.94:13.0:1
#000000
#0C57A8
Fail
h2 Help expand2.94:13.0:1
#000000
#0C57A8
Fail
h2 human knowledge2.94:13.0:1
#000000
#0C57A8
Fail
h2 Subscribe for news2.94:13.0:1
#000000
#0C57A8
Fail
h2 Photo credits2.94:13.0:1
#000000
#0C57A8
Fail
title Home – Wikimedia F…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
button Who we are21.00:14.5:1
#000000
#FFFFFF
Pass
a Get to know us21.00:14.5:1
#000000
#FFFFFF
Pass
a People21.00:14.5:1
#000000
#FFFFFF
Pass
a Board of Trustees21.00:14.5:1
#000000
#FFFFFF
Pass
a Executive team21.00:14.5:1
#000000
#FFFFFF
Pass

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
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Header Menu w/ mega menus" MAIN CONTENTINFO footer
A+
Heading Text Quality
All 53 heading(s) have substantive, well-formed text
PASS
All 53 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 63 images OK
PASS
All 63 images OK
Info::
57 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
63 images 6 good alt text 57 decorative
All images have appropriate alt text.
A
Form Input Types
2 input(s) using type=text where a specific type would help
PASS
2 input(s) using type=text where a specific type would help
Info::
Input "mc_mv_EMAIL" should use type="email" (currently type="text")
Field name "mc_mv_EMAIL" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
Info::
Input "mailchimp_sf_alt_email" should use type="email" (currently type="text")
Field name "mailchimp_sf_alt_email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A+
Form Input Quality
8 form control(s) checked, no input-semantic issues
PASS
8 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Mobile-Readable Font Sizes
All 128 visible text node(s) render at >= 12 CSS pixels
PASS
All 128 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 29 passed
PASS
92

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.

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
The Wikimedia Foundation files to protect open knowledge in New York Times v Op… ul#splide01-list > li#splide01-slide01 > div.wp-block-group > h4.wp-block-post-title

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wp-block-group > div#download-the-app > figure.wp-block-image > a div.wp-block-group > div#download-the-app > figure.wp-block-image > a
div.wp-block-group > div#download-the-app > figure.wp-block-image > a div.wp-block-group > div#download-the-app > figure.wp-block-image > a

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper
File provided by Wikimedia Commons div.attribution-item > div.attribution-item__content > div > a.commons-tooltip-wrapper

These items highlight common accessibility best practices.

○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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●ARIA `tooltip` elements have accessible names
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields 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
○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 type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○`[lang]` attributes have a valid value
○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.
○Elements with visible text labels have matching accessible names.
○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