Skip to content
https://fentybeauty.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
44
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
F
Heading Hierarchy
Action
38 headings, 5 skip(s)
FIX
38 headings, 5 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
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 → H3 (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::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 New + Bestsellers
  • H4 DEW N PLUMP HYDRATING NECTAR FACE MIST skipped
  • H2 Makeup
  • H2 Skincare
  • H2 Hair
  • H2 Fragrance
  • H2 Discover
  • H4 WE KNOW YOUR TYPE skipped
  • H4 RIHANNA’S GO-TO ROUTINE FOR A REASON
  • H2 Sale
  • H3 THE ULTIMATE FENTY LINEUP
  • H3 Your Bag
  • H2 Your bag is empty.Explore our popular categories!
  • H4 HANDPICKED FOR YOU skipped
  • H2 Donate to the Clara Lionel Foundation
  • H1 THE FLASHY ONE 9-IN-1 TREATMENT OIL
  • H1 SHAKE ’N PLAY BUILDABLE LIQUID BLUSH duplicate H1
  • H1 THE WATTABRAT COLLECTION duplicate H1
  • H3 MUST-HAVES FOR EVERY MOOD skipped
  • H4 New arrivals + fam faves for every day.
  • H2 GLOSS BOMB IN WATTABRAT
  • H3 THE ULTIMATE FENTY LINEUP
  • H4 Get your hands on highly rated hits + fresh picks.
  • H2 MEET ROSE AMBER
  • H2 THE FENTY BEAUTY BRANDS
  • H4 fenty beauty skipped
  • H4 fenty skin
  • H4 fenty hair
  • H4 fenty fragrance
  • H3 STAY POSTED + UNLOCK EXCLUSIVE OFFERS
  • H2 CUSTOMER SERVICE
  • H2 CUSTOMER SERVICE
  • H2 ABOUT
  • H2 ABOUT
  • H2 Privacy + Terms
  • H2 Privacy + Terms
  • H3 (empty)
  • H2 Sign in

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
Alt Text Quality
Action
8 of 146 images have issues
FIX
8 of 146 images have issues
Critical::
8 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with alt text over 125 characters
Info::
10 decorative image(s) correctly marked
Info::
127 image(s) with good alt text
146 images 127 good alt text 10 decorative 8 missing
IssueCount
missing8 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Favicon & Branding
Action
14 icon(s) detected
FIX
14 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
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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 6 controls have issues
REVIEW
3 of 6 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="phone">; <input type="email" name="email">
Info::
3 control(s) properly labeled
6 controls
3 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
#search-inputtextSearch Productsfor/id
customer[email]emailEmailaria-label
customer[password]passwordPasswordaria-label
phonetext(Phone)placeholder only
emailemail(Email)placeholder only
selectselect(none)none

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

<select>

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="phone">; <input type="email" name="email">

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 Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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 THE FLASHY ONE
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 9-IN-1 TREATMENT OIL
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 SHAKE ’N PLAY
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 BUILDABLE
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 LIQUID BLUSH
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
32px · bottom of viewport
h1 THE WATTABRAT COLLECTION
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Your bag is empty.
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore our popular categories!
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Donate to the Clara Lionel Foundation
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 GLOSS BOMB IN WATTABRAT
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 MEET ROSE AMBER
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 THE FENTY BEAUTY BRANDS
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 CUSTOMER SERVICE
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ABOUT
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Privacy + Terms
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sign in
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h3 THE ULTIMATE FENTY LINEUP
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Your Bag
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 MUST-HAVES FOR EVERY MOOD
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 THE ULTIMATE FENTY LINEUP
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 THE FLASHY ONE1.27:13.0:1
#000000
#1F1F1F
Fail
h1 9-IN-1 TREATMENT OIL1.27:13.0:1
#000000
#1F1F1F
Fail
h1 SHAKE ’N PLAY1.27:13.0:1
#000000
#1F1F1F
Fail
h1 BUILDABLE1.27:13.0:1
#000000
#1F1F1F
Fail
h1 LIQUID BLUSH1.27:13.0:1
#000000
#1F1F1F
Fail
h1 THE WATTABRAT COLLEC…1.27:13.0:1
#000000
#1F1F1F
Fail
h2 Your bag is empty.1.27:13.0:1
#000000
#1F1F1F
Fail
h2 Explore our popular …1.27:13.0:1
#000000
#1F1F1F
Fail
h2 Donate to the Clara …1.27:13.0:1
#000000
#1F1F1F
Fail
h2 GLOSS BOMB IN WATTAB…1.27:13.0:1
#000000
#1F1F1F
Fail
h2 MEET ROSE AMBER1.27:13.0:1
#000000
#1F1F1F
Fail
h2 THE FENTY BEAUTY BRA…1.27:13.0:1
#000000
#1F1F1F
Fail
h2 CUSTOMER SERVICE1.27:13.0:1
#000000
#1F1F1F
Fail
h2 ABOUT1.27:13.0:1
#000000
#1F1F1F
Fail
h2 Privacy + Terms1.27:13.0:1
#000000
#1F1F1F
Fail
h2 Sign in1.27:13.0:1
#000000
#1F1F1F
Fail
h3 THE ULTIMATE FENTY L…1.27:13.0:1
#000000
#1F1F1F
Fail
h3 Your Bag1.27:13.0:1
#000000
#1F1F1F
Fail
h3 MUST-HAVES FOR EVERY…1.27:13.0:1
#000000
#1F1F1F
Fail
h3 THE ULTIMATE FENTY L…1.27:13.0:1
#000000
#1F1F1F
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.

C
Lighthouse Accessibility Audits
Action
Score 72/100 — 10 failing, 24 passed
REVIEW
72

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Rihanna New! div.header-nav__inner > ul.header-nav__items > div.header-nav__tabs-container > ul.header-nav__tabs

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Rihanna div.header-nav__tabs-container > ul.header-nav__tabs > li > button.header-nav__tab-item
New! div.header-nav__tabs-container > ul.header-nav__tabs > li > button.header-nav__tab-item

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.swiper-slide > div.hero-slider__slide-inner > div.hero-slider__slide-image > img.w-full div.swiper-slide > div.hero-slider__slide-inner > div.hero-slider__slide-image > img.w-full
div#swiper-wrapper-88d51d9ae259c60f > a.collection-slider__slide > div.collection-slider__slide-image__wrapper > img.w-full div#swiper-wrapper-88d51d9ae259c60f > a.collection-slider__slide > div.collection-slider__slide-image__wrapper > img.w-full
div#swiper-wrapper-88d51d9ae259c60f > a.collection-slider__slide > div.collection-slider__slide-image__wrapper > img.w-full div#swiper-wrapper-88d51d9ae259c60f > a.collection-slider__slide > div.collection-slider__slide-image__wrapper > img.w-full

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.promo-banner__slide-inner > div.promo-banner__slide-image > div.promo-banner__slide-video-wrapper > iframe.promo-banner__slide-video div.promo-banner__slide-inner > div.promo-banner__slide-image > div.promo-banner__slide-video-wrapper > iframe.promo-banner__slide-video

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy Policy body.fentybeauty-com > div.cc-window > span#cookieconsent:desc > a.cc-link
Privacy Settings body.fentybeauty-com > div.cc-window > span#cookieconsent:desc > button#consent-management-tool
Reject body.fentybeauty-com > div.cc-window > div.cc-compliance > button.cc-btn
Accept All body.fentybeauty-com > div.cc-window > div.cc-compliance > button.cc-btn

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
MUST-HAVES FOR EVERY MOOD div#shopify-section-featured_products_zwRkpX > div.featured-products > div.featured-products__content > h3.h1
FENTY BEAUTY div.collection-slider__carousel > div#swiper-wrapper-88d51d9ae259c60f > a.collection-slider__slide > h4.h4

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
New + Bestsellers Makeup Skincare Hair Fragrance Discover Sale Rihanna New! Rih… div.header__inner-wrapper > nav.header-nav > div.header-nav__inner > ul.header-nav__items

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Rihanna ul.header-nav__items > div.header-nav__tabs-container > ul.header-nav__tabs > li
New! ul.header-nav__items > div.header-nav__tabs-container > ul.header-nav__tabs > li

These are opportunities to improve the experience of reading tabular or list data using 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
Go to slide 0 div.hero-slider > div.swiper > div.swiper-pagination > button.swiper-pagination-bullet
Go to slide 1 div.hero-slider > div.swiper > div.swiper-pagination > button.swiper-pagination-bullet
Go to slide 2 div.hero-slider > div.swiper > div.swiper-pagination > button.swiper-pagination-bullet

These items highlight common accessibility best practices.

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
Privacy Policy body.fentybeauty-com > div.cc-window > span#cookieconsent:desc > a.cc-link
Privacy Settings body.fentybeauty-com > div.cc-window > span#cookieconsent:desc > button#consent-management-tool
Reject body.fentybeauty-com > div.cc-window > div.cc-compliance > button.cc-btn
Accept All body.fentybeauty-com > div.cc-window > div.cc-compliance > button.cc-btn
Makeup div.header-nav__inner > ul.header-nav__items > li.header-nav__item > button.header-nav__item-link
Skincare div.header-nav__inner > ul.header-nav__items > li.header-nav__item > button.header-nav__item-link
Hair div.header-nav__inner > ul.header-nav__items > li.header-nav__item > button.header-nav__item-link
Fragrance div.header-nav__inner > ul.header-nav__items > li.header-nav__item > button.header-nav__item-link
Discover div.header-nav__inner > ul.header-nav__items > li.header-nav__item > button.header-nav__item-link
Butta Drop Whipped Oil Body Cream with Tropical Oils + Shea Butter — Fenty Fres… div > div._centerTile_14cvz_143 > div#tolstoy-products-panel-0-088901e8-57bb-4b90-9e92-0726b5292847 > div.tolstoy-product-tile
Tiktok div.footer__socials > ul.socials > li > a
Instagram div.footer__socials > ul.socials > li > a
Facebook div.footer__socials > ul.socials > li > a
Twitter div.footer__socials > ul.socials > li > a
Youtube div.footer__socials > ul.socials > li > a
Tiktok div.footer__socials > ul.socials > li > a
Instagram div.footer__socials > ul.socials > li > a
Facebook div.footer__socials > ul.socials > li > a
Twitter div.footer__socials > ul.socials > li > a
Youtube div.footer__socials > ul.socials > li > a
Tiktok div.footer__socials > ul.socials > li > a
Instagram div.footer__socials > ul.socials > li > a
Facebook div.footer__socials > ul.socials > li > a
Twitter div.footer__socials > ul.socials > li > a
Youtube div.footer__socials > ul.socials > li > a
○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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○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
○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
○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.
○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.
A
Landmark Structure
16 landmarks
PASS
16 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
2 <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 "skip-to-main-content" MAIN CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback