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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
5
REVIEW
7
PASS
1
INFO
0
Checks
13
1 PASS 7 REVIEW 5 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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 (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
Heading Hierarchy
Action
108 headings, 6 skip(s)
FIX
108 headings, 6 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
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 → 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: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H6 Divi Changes Everything. Give It A Test Drive!
  • H3 Divi Features
  • H3 All Features
  • H3 200+ Elements
  • H3 2,000+ Layouts
  • H3 Quick Sites New!
  • H3 No-Code Design
  • H3 Theme Builder
  • H3 Ecommerce
  • H3 Workflow
  • H3 Marketing
  • H3 Developers
  • H3 Site Examples
  • H3 Integrations
  • H3 Divi Products & Services
  • H3 Divi Theme & Builder
  • H3 Divi 5 Now Available!
  • H3 Divi Marketplace
  • H3 Divi AI
  • H3 Divi Cloud
  • H3 Divi Hosting
  • H3 Divi VIP
  • H3 Divi Teams
  • H3 Divi Dash
  • H3 Web Design Agencies
  • H3 Web Design Freelancers
  • H3 Small Business Owners
  • H3 Online Store Owners
  • H3 Divi Theme & Page Builder
  • H3 Divi Page Builder Plugin
  • H3 Extra Magazine Theme
  • H3 Bloom Email Opt-Ins
  • H3 Monarch Social Sharing
  • H3 Get In Touch
  • H3 Chat With Sales
  • H3 Accounts & Billing
  • H3 Technical Support
  • H3 Ask The Community
  • H3 Documentation
  • H3 Product Downloads
  • H3 Divi Cloud
  • H3 Manage Team
  • H3 Username & API Key
  • H3 Account Details
  • H3 Billing Info
  • H3 Subscriptions
  • H3 Special Offers
  • H3 Customer Support
  • H3 Log Out
  • H1 WordPress unleashed—the ultimate visual page builder & website framework.
  • H4 Join 974,872 empowered web design professionals & business owners skipped
  • H2 Divi
  • H4 The ultimate theme and website building framework for WordPress skipped
  • H4 Build any type of website with full-site, drag & drop editing
  • H4 Launch unlimited websites with a single license
  • H4 Build a personal site or power your business with one membership
  • H4 The Divi Experience
  • H2 Full-site editing, collaboration, website management, & an unrivaled community
  • H4 Limitless drag & drop visual editing skipped
  • H4 Launch websites within minutes of activation
  • H4 Edit, scale, and manage your website with ease.
  • H4 Divi is for everyone
  • H4 Portfolios & CVs
  • H4 Online stores
  • H4 SMB's
  • H4 Coaching
  • H4 Makers
  • H4 Non-profits
  • H4 Restaurants
  • H4 Events
  • H4 Health
  • H4 Products
  • H4 Services
  • H4 Beauty
  • H4 The Divi Ecosystem & Divi PRO★
  • H2 Divi is more than just a builder. Level up your web design toolkit with cloud storage, AI tools, VIP support & more.
  • H6 Divi AI skipped
  • H5 Build layouts, images, text & code with AI
  • H6 Divi Cloud
  • H5 Store & access your Divi items on the cloud
  • H6 The Divi Marketplace
  • H5 Download Divi Child Themes, Extensions and Layouts
  • H6 Divi VIP
  • H5 Enjoy faster support & other Exclusive benefits
  • H6 Divi Dash
  • H5 Update & monitor all your websites in one place
  • H6 Divi Teams
  • H5 Work with your team across the Divi Ecosystem
  • H2 Power Your Entire Company, Team, or Personal Website With a Single License
  • H5 Unlimited website usage skipped
  • H5 Constant updates
  • H5 Rock solid security
  • H5 24/7 Customer support
  • H5 Satisfaction guaranteed
  • H5 Active Community
  • H3 974,872 customers are already building amazing websites with Divi. Join the most empowered WordPress community.
  • H6 Facebook skipped
  • H6 Facebook Group
  • H6 X
  • H6 Newsletter
  • H6 YouTube
  • H6 LinkedIn
  • H6 Divi Features
  • H6 Products
  • H6 Resources
  • H6 Blog
  • H6 Community
  • H6 Company

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
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::
1 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 1 <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
Form Accessibility
Action
3 of 4 controls have issues
REVIEW
3 of 4 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="submit" id="et-wp-submit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="username">; <input type="password" name="password">
Info::
1 control(s) properly labeled
4 controls
1 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
#remember_mecheckboxnone
passwordpassword(Password)placeholder only
usernametext(Username)placeholder only
#et-wp-submitsubmit(none)none

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

<input type="submit" name="submit" id="et-wp-submit">

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="text" name="username">; <input type="password" name="password">

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
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 ✓Page Title 404 - This Page Does Not Exist ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
5 icon(s) detected
REVIEW
5 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'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ 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, 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
h1 WordPress unleashed—the ultimate visua…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Divi
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Full-site editing, collaboration, websit…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Divi is more than just a builder.
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Power Your Entire Company, Team, or Pers…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Divi Features
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · above the fold
h3 All Features
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · above the fold
h3 200+ Elements
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · above the fold
h3 2,000+ Layouts
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · above the fold
h3 Quick Sites
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · above the fold
h3 No-Code Design
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · above the fold
h3 Theme Builder
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · above the fold
h3 Ecommerce
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · mid-page
h3 Workflow
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · mid-page
h3 Marketing
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · mid-page
h3 Developers
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · mid-page
h3 Site Examples
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · mid-page
h3 Integrations
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · mid-page
h3 Divi Products & Services
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · mid-page
h3 Divi Theme & Builder
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 WordPress unleashed…1.00:13.0:1
#000000
#000000
Fail
h2 Divi1.00:13.0:1
#000000
#000000
Fail
h2 Full-site editing, c…1.00:13.0:1
#000000
#000000
Fail
h2 Divi is more than ju…1.00:13.0:1
#000000
#000000
Fail
h2 Power Your Entire Co…1.00:13.0:1
#000000
#000000
Fail
h3 Divi Features1.00:13.0:1
#000000
#000000
Fail
h3 All Features1.00:13.0:1
#000000
#000000
Fail
h3 200+ Elements1.00:13.0:1
#000000
#000000
Fail
h3 2,000+ Layouts1.00:13.0:1
#000000
#000000
Fail
h3 Quick Sites1.00:13.0:1
#000000
#000000
Fail
h3 No-Code Design1.00:13.0:1
#000000
#000000
Fail
h3 Theme Builder1.00:13.0:1
#000000
#000000
Fail
h3 Ecommerce1.00:13.0:1
#000000
#000000
Fail
h3 Workflow1.00:13.0:1
#000000
#000000
Fail
h3 Marketing1.00:13.0:1
#000000
#000000
Fail
h3 Developers1.00:13.0:1
#000000
#000000
Fail
h3 Site Examples1.00:13.0:1
#000000
#000000
Fail
h3 Integrations1.00:13.0:1
#000000
#000000
Fail
h3 Divi Products & Serv…1.00:13.0:1
#000000
#000000
Fail
h3 Divi Theme & Builder1.00:13.0:1
#000000
#000000
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.

B
Lighthouse Accessibility Audits
Score 82/100 — 6 failing, 23 passed
REVIEW
82

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot

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.

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
Join 974,872 empowered web design professionals & business owners section#divi-hero > div.grid-row > div.col > h4.text-gray
Divi is for everyone section > div.grid-row > div.col > h4.text-accent
The Divi Ecosystem & Divi PRO★ section > div.grid-row > div.col > h4.text-accent
Divi Cloud section > div.grid-row > div.col > h6.text-accent

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Divi Dash div.grid-row > div.col > p > a

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
Join 974,872 empowered web design professionals & business owners section#divi-hero > div.grid-row > div.col > h4.text-gray
The ultimate theme and website building framework for WordPress section#divi-cta > div.grid-row > div.col > h4
Limitless drag & drop visual editing section.rounded-lg > div.grid-row > div.col > h4
Divi AI section > div.grid-row > div.col > h6.text-accent
Unlimited website usage div.grid-row-container > div.grid-row > div.col > h5
Facebook section#main-footer > div.grid-row > a#facebook > h6

These are opportunities to improve keyboard navigation in your application.

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
❮ div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-prev
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-dot
❯ div.col > div.testimonial-slider > div.testimonial-slider-nav > button.testimonial-slider-next

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 `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
○`<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
○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.
A+
Alt Text Quality
All 23 images OK
PASS
All 23 images OK
Info::
23 image(s) with good alt text
23 images 23 good alt text
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback