Skip to content
https://www.cloudflare.com

Accessibility

· 23 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
9
REVIEW
3
PASS
11
INFO
0
Checks
23
11 PASS 3 REVIEW 9 FIX
F
Heading Hierarchy
Action
62 headings, 8 skip(s)
FIX
62 headings, 8 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H6 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
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 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Connect, protect, and build everywhere
  • H6 Join us at Connect San Francisco skipped
  • H6 New 2026 Security Signals Report
  • H2 Our connectivity cloud is the best place to connect your users, apps, clouds, and networksprotect everything you connect to the Internetbuild and scale applications
  • H3 Connect your workforce, AI agents, apps, and infrastructure
  • H6 Related skipped
  • H3 Protect and accelerate websites and AI-enabled apps
  • H6 Related skipped
  • H3 Build and secure AI agents
  • H6 Related skipped
  • H2 One global cloud network unlike any other
  • H2 Leading companies rely on Cloudflare
  • H4 Connect skipped
  • H4 Protect
  • H4 Build
  • H3 Connect users and apps securely
  • H3 Protect and accelerate websites
  • H3 Build and scale applications
  • H2 How Cloudflare can help
  • H6 Modernize remote access skipped
  • H6 Secure generative and agentic AI
  • H6 Deploy serverless code
  • H6 Deploy AI on the edge
  • H6 Stop DDoS attacks
  • H6 Block bot traffic
  • H2 News and resources
  • H5 What's new skipped
  • H5 Insights
  • H5 Library
  • H5 Events
  • H6 Cloudflare and GoDaddy partner to help enable an open agentic web
  • H6 Cloudflare named a ‘Leader’ in Forrester Wave for Edge Development Platforms for 2026
  • H6 2026 Cloudflare Threat Report
  • H6 Attend a Test Drive workshop to get hands-on experience with Cloudflare products
  • H6 Cloudflare strengthens content offering to AI companies with acquisition of Human Native
  • H6 Cloudflare acquires Astro to accelerate the future of high-performance web development
  • H6 Cloudflare 2025 Impact Report
  • H6 Cloudflare to acquire Replicate to build the most seamless AI Cloud for developers
  • H6 Cloudflare named a Challenger in 2025 Gartner® Magic Quadrant™ for CNAP
  • H6 Cloudflare named a Visionary in 2025 Gartner® Magic Quadrant™ for SASE Platforms
  • H6 Rethink what cyber resilience really means
  • H6 NCR Voyix on how a service mindset delivers better security outcomes
  • H6 CSO Grant Bourzikas shares strategies to curb AI misinformation
  • H6 Cloudflare CIO, Mike Hamilton on how AI is disrupting software purchases
  • H6 Protect modern organizations from threats without stifling innovation
  • H6 3 challenges of securing and connecting application services
  • H6 Explore more ebooks in Cloudflare's Resource Hub
  • H6 Increase developer velocity with a connectivity cloud
  • H6 Registration is now open for Cloudflare Connect 2026
  • H6 Join our solutions engineering team for a weekly application services demo
  • H6 Learn more about Cloudflare and meet our team at an upcoming event near you
  • H6 Enhance your knowledge and gain new skills with a live or on-demand webinar
  • H6 Security builders workshop series
  • H6 Security leaders forum series
  • H6 Architecture Workshop Series
  • H2 Get started with the connectivity cloud
  • H5 Get started for free skipped
  • H5 Need help choosing?
  • H5 Talk to an expert
  • H2 Speak to sales about SASE and workspace security.
  • H2 Thank You
  • H2 Our site uses cookies

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

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
Mobile Keyboard & Autofill
Action
3/4 eligible field(s) missing autocomplete or inputmode
FIX
3/4 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="email" name="Email" id="e7af6b44-3534-426a-9bd2-c0347ae582dd-modal-Email">
Warning::
2 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: tel, email.
Got: <input type="tel" name="Phone" id="e7af6b44-3534-426a-9bd2-c0347ae582dd-modal-Phone">, <input type="email" name="Email" id="e7af6b44-3534-426a-9bd2-c0347ae582dd-modal-Email">
D
404 Error Page
Action
HTTP 404, custom page
FIX
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
11 landmarks
REVIEW
11 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

C
Form Accessibility
Action
6 of 16 controls have issues
REVIEW
6 of 16 controls have issues
Critical::
6 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="Job_Level__c">; <input type="text" name="Job_Level__c-search-field">; <select name="Job_Function__c">; <input type="text" name="Job_Function__c-search-field">; <select name="Country">; <input type="text" name="Country-search-field">
Info::
10 control(s) properly labeled
16 controls
10 labeled
0 placeholder only
6 unlabeled
ControlTypeLabelMethod
#e7af6b44-3534-426a-9bd2-c0347ae582dd-modal-FirstNametextFirst name: *for/id
#e7af6b44-3534-426a-9bd2-c0347ae582dd-modal-LastNametextLast name: *for/id
#e7af6b44-3534-426a-9bd2-c0347ae582dd-modal-PhonetelPhone: *for/id
#e7af6b44-3534-426a-9bd2-c0347ae582dd-modal-EmailemailWork email: *for/id
#e7af6b44-3534-426a-9bd2-c0347ae582dd-modal-CompanytextCompany: *for/id
#e7af6b44-3534-426a-9bd2-c0347ae582dd-modal-marketingOptInConsentcheckboxnone
#e7af6b44-3534-426a-9bd2-c0347ae582dd-modal-consentTermsofServicecheckboxnone
#e7af6b44-3534-426a-9bd2-c0347ae582dd-modal-consentCollectionanduseofpersonalinformationcheckboxnone
#e7af6b44-3534-426a-9bd2-c0347ae582dd-modal-consentTransferpersonalinformationoverseascheckboxnone
#e7af6b44-3534-426a-9bd2-c0347ae582dd-modal-consentSharingpersonalinformationtothirdpartiescheckboxnone
Country-search-fieldtext(none)none
Job_Level__cselect(none)none
Job_Level__c-search-fieldtext(none)none
Job_Function__cselect(none)none
Job_Function__c-search-fieldtext(none)none
Countryselect(none)none

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

<select name="Job_Level__c">; <input type="text" name="Job_Level__c-search-field">; <select name="Job_Function__c">; <input type="text" name="Job_Function__c-search-field">; <select name="Country">; <input type="text" name="Country-search-field">

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

B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 4 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Connect, protect, an…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our connectivity clo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 One global cloud net…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Leading companies re…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 How Cloudflare can h…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 News and resources21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get started with the…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Speak to sales about…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Thank You21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our site uses cookie…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Connect your workfor…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Protect and accelera…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Build and secure AI …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Connect users and ap…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Protect and accelera…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Build and scale appl…21.00:13.0:1
#000000
#FFFFFF
Pass
title Connect, protect, an…5.24:14.5:1
#000000
#7F7F7F
Pass
a Log in5.24:14.5:1
#000000
#7F7F7F
Pass
a Support5.24:14.5:1
#000000
#7F7F7F
Pass
span Sales: 900 943 4675.24:14.5:1
#000000
#7F7F7F
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+
Alt Text Quality
All 76 images OK
PASS
All 76 images OK
Info::
76 image(s) with good alt text
76 images 76 good alt text
All images have appropriate alt text.
A
Form Input Types
3 input(s) using type=text where a specific type would help
PASS
3 input(s) using type=text where a specific type would help
Info::
Input "Job_Level__c-search-field" should use type="search" (currently type="text")
Field name "Job_Level__c-search-field" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "Job_Function__c-search-field" should use type="search" (currently type="text")
Field name "Job_Function__c-search-field" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "Country-search-field" should use type="search" (currently type="text")
Field name "Country-search-field" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
16 form control(s) checked, no input-semantic issues
PASS
16 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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+
Tabindex Anti-Patterns
299 explicit tabindex attribute(s) checked, no anti-patterns
PASS
299 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 45 visible text node(s) render at >= 12 CSS pixels
PASS
All 45 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 99/100 — 1 failing, 27 passed
PASS
99

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
Join us at Connect San Francisco div.flex > div.flex > div.md:flex-1 > h6.leading-[110%]
Related div.flex > div > div.space-y-4 > h6
Related div.flex > div > div.space-y-4 > h6
Related div.flex > div > div.space-y-4 > h6
Connect div.whitespace-nowrap > div.active > div.text-start > h4.text-[1rem]
Modernize remote access div.relative > div.fade-card-front > div.text-center > h6.leading-[110%]
What's new div.whitespace-nowrap > div.active > div.text-start > h5.text-[1rem]
Get started for free div > div.h-full > div.text-center > h5.leading-[110%]

These are opportunities to improve keyboard navigation in your application.

○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
●Image elements have `[alt]` attributes
●`[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
●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.
●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.
●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
○Form elements have associated labels
○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.
○`[lang]` attributes have a valid value
○`<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.
○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