Skip to content
https://starwoodhotels.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
8
REVIEW
2
PASS
3
INFO
0
Checks
13
3 PASS 2 REVIEW 8 FIX
F
Heading Hierarchy
Action
87 headings, 6 skip(s)
FIX
87 headings, 6 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Main navigation
  • H2 Main navigation
  • H1 Starwood Hotels
  • H2 Our Brands
  • H4 1 Hotels skipped
  • H4 Baccarat Hotels
  • H4 Treehouse Hotels
  • H4 SH Collection
  • H2 Our Brands
  • H4 1 Hotels skipped
  • H4 Baccarat Hotels
  • H4 Treehouse Hotels
  • H4 SH Collection
  • H2 Our Experiences
  • H3 Hotels & Resorts
  • H3 Residences
  • H3 Restaurants & Nightlife
  • H3 Wellness
  • H3 Meetings & Events
  • H2 Our Path of Growth & Development
  • H2 Our Locations
  • H4 1 Hotel Brooklyn Bridge skipped
  • H4 1 Hotel Hanalei Bay
  • H4 1 Hotel Mayfair
  • H4 1 Hotel San Francisco
  • H4 1 Hotel & Homes South Beach
  • H4 1 Hotel Toronto
  • H4 1 Hotel West Hollywood
  • H4 Treehouse London
  • H4 Baccarat Hotel & Residences New York
  • H4 1 Hotel Copenhagen
  • H4 1 Hotel Paris
  • H4 1 Hotel & Homes Elounda Hills
  • H4 1 Hotel & Homes Melbourne
  • H4 1 Hotel & Homes Cabo
  • H4 1 Hotel Austin
  • H4 1 Hotel Nashville
  • H4 1 Hotel Central Park
  • H4 Baccarat Residences Brickell
  • H4 Treehouse Manchester
  • H4 Treehouse Silicon Valley
  • H4 Treehouse Brickell
  • H4 Treehouse Adelaide
  • H4 1 Hotel Seattle
  • H4 Baccarat Hotel & Residences Dubai
  • H4 Baccarat Hotel Florence
  • H4 Baccarat Hotel & Residences Maldives
  • H4 Baccarat Hotel & Residences Diriyah
  • H4 Baccarat Hotel Rome
  • H4 1 Hotel & Homes San Miguel de Allende
  • H4 Treehouse Diriyah
  • H4 1 Hotel Diriyah
  • H4 1 Hotel & Homes Tokyo
  • H4 1 Hotel & Homes Hudson Valley
  • H4 Treehouse Miami Beach
  • H2 Sustainability in Every Step
  • H3 Sustainable Sourcing
  • H3 Community Empowerment
  • H3 Carbon Footprint
  • H3 Water Stewardship
  • H3 Waste & Circularity
  • H3 Sustainable Sourcing
  • H3 Community Empowerment
  • H3 Carbon Footprint
  • H3 Water Stewardship
  • H3 Waste & Circularity
  • H3 Sustainable Sourcing
  • H3 Community Empowerment
  • H2 What the World Is Saying
  • H2 Introducing Nature's Wellness Sanctuary at 1 Hotel Hanalei Bay
  • H4 1 Hotel Tokyo Reimagines Luxury In The Sky skipped
  • H4 1 Hotel Tokyo: First In
  • H4 Now Open: 1 Hotel Tokyo — A Nature-Infused Urban Sanctuary
  • H4 These are the hotel openings TPG is most excited for in 2026
  • H4 Now Open: 1 Hotel Tokyo — A Nature-Infused Urban Sanctuary
  • H4 These are the hotel openings TPG is most excited for in 2026
  • H2 Introducing Nature's Wellness Sanctuary at 1 Hotel Hanalei Bay
  • H4 1 Hotel Tokyo Reimagines Luxury In The Sky skipped
  • H4 1 Hotel Tokyo: First In
  • H4 Now Open: 1 Hotel Tokyo — A Nature-Infused Urban Sanctuary
  • H4 These are the hotel openings TPG is most excited for in 2026
  • H2 Introducing Nature's Wellness Sanctuary at 1 Hotel Hanalei Bay
  • H4 1 Hotel Tokyo Reimagines Luxury In The Sky skipped
  • H4 1 Hotel Tokyo: First In
  • H4 Now Open: 1 Hotel Tokyo — A Nature-Infused Urban Sanctuary
  • H4 These are the hotel openings TPG is most excited for in 2026
  • H2 Join the Journey

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

F
Form Accessibility
Action
11 of 19 controls have issues
FIX
11 of 19 controls have issues
Critical::
8 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="chainCode" id="bk-brand-field">; <select name="hotelCode" id="bk-property-field">; <input type="submit" name="op" id="edit-actions-submit">; <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="promoCode">; <input type="text" name="rateCode">; <input type="checkbox" name="accessibleRooms">
Info::
8 control(s) properly labeled
19 controls
8 labeled
3 placeholder only
8 unlabeled
ControlTypeLabelMethod
#mega-mapbox--field_brandselectBrandsfor/id
#mega-mapbox--field_property_typeselectHotel Or Residentialfor/id
#mega-mapbox--field_store_statusselectStatusfor/id
#edit-name-firsttextFirstfor/id
#edit-name-lasttextLastfor/id
#edit-email-addressemailEmail Addressfor/id
#edit-terms-and-conditionscheckboxTerms and conditionsfor/id
#edit-urltextLeave this field blankfor/id
accessibleRoomscheckbox(Accessible Rooms Only)placeholder only
promoCodetext(Promo Code)placeholder only
rateCodetext(Group Code)placeholder only
#edit-actions-submitsubmit(none)none
#bk-property-fieldselect(none)none
#bk-brand-fieldselect(none)none
#goog-gt-votingInputSrcLangtext(none)none
#goog-gt-votingInputTrgLangtext(none)none
#goog-gt-votingInputSrcTexttext(none)none
#goog-gt-votingInputTrgTexttext(none)none
#goog-gt-votingInputVotetext(none)none

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

<select name="chainCode" id="bk-brand-field">; <select name="hotelCode" id="bk-property-field">; <input type="submit" name="op" id="edit-actions-submit">; <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">

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="promoCode">; <input type="text" name="rateCode">; <input type="checkbox" name="accessibleRooms">

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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Page | Starwood Hotels ✓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 Starwood Hotels
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Main navigation
2.96:1
#000000
on
#70514A
needs 3.0:1 (large text)
24px · above the fold
h2 Main navigation
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Brands
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Brands
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Experiences
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Path of Growth & Development
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Locations
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sustainability in Every Step
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What the World Is Saying
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Introducing Nature's Wellness Sanctuary …
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Introducing Nature's Wellness Sanctuary …
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Introducing Nature's Wellness Sanctuary …
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Join the Journey
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Hotels & Resorts
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Residences
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Restaurants & Nightlife
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Wellness
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Meetings & Events
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sustainable Sourcing
1.45:1
#000000
on
#262B1E
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Starwood Hotels1.45:13.0:1
#000000
#262B1E
Fail
h2 Main navigation2.96:13.0:1
#000000
#70514A
Fail
h2 Main navigation1.45:13.0:1
#000000
#262B1E
Fail
h2 Our Brands1.45:13.0:1
#000000
#262B1E
Fail
h2 Our Brands1.45:13.0:1
#000000
#262B1E
Fail
h2 Our Experiences1.45:13.0:1
#000000
#262B1E
Fail
h2 Our Path of Growth &…1.45:13.0:1
#000000
#262B1E
Fail
h2 Our Locations1.45:13.0:1
#000000
#262B1E
Fail
h2 Sustainability in Ev…1.45:13.0:1
#000000
#262B1E
Fail
h2 What the World Is Sa…1.45:13.0:1
#000000
#262B1E
Fail
h2 Introducing Nature's…1.45:13.0:1
#000000
#262B1E
Fail
h2 Introducing Nature's…1.45:13.0:1
#000000
#262B1E
Fail
h2 Introducing Nature's…1.45:13.0:1
#000000
#262B1E
Fail
h2 Join the Journey1.45:13.0:1
#000000
#262B1E
Fail
h3 Hotels & Resorts1.45:13.0:1
#000000
#262B1E
Fail
h3 Residences1.45:13.0:1
#000000
#262B1E
Fail
h3 Restaurants & Nightl…1.45:13.0:1
#000000
#262B1E
Fail
h3 Wellness1.45:13.0:1
#000000
#262B1E
Fail
h3 Meetings & Events1.45:13.0:1
#000000
#262B1E
Fail
h3 Sustainable Sourcing1.45:13.0:1
#000000
#262B1E
Fail

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

A+
Landmark Structure
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
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 "block-starwood-main-menu-menu" MAIN CONTENTINFO footer
A+
Alt Text Quality
All 98 images OK
PASS
All 98 images OK
Info::
5 decorative image(s) correctly marked
Info::
93 image(s) with good alt text
98 images 93 good alt text 5 decorative
All images have appropriate alt text.
A
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 29 passed
PASS
91

Accessibility

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

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.mapboxgl-control-container > div.mapboxgl-ctrl-bottom-right > div.mapboxgl-ctrl > button.mapboxgl-ctrl-attrib-button div.mapboxgl-control-container > div.mapboxgl-ctrl-bottom-right > div.mapboxgl-ctrl > button.mapboxgl-ctrl-attrib-button

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
At Starwood Hotels, we're on a mission to improve the planet one hotel at a tim… section.basic-content > div.basic-content__inner > div.clearfix > p.font-size--big
Immersed in lifestyle and luxury that transcend the conventions of hospitality,… section.basic-content > div.basic-content__inner > div.clearfix > p.font-size--big
local cultures div.basic-content__inner > div.clearfix > p.font-size--big > em
transformative wellness div.basic-content__inner > div.clearfix > p.font-size--big > em
culinary excellence, div.basic-content__inner > div.clearfix > p.font-size--big > em
vibrant nightlife. div.basic-content__inner > div.clearfix > p.font-size--big > em
Our Path of Growth & Development section.basic-content--text-aligned-left > div.basic-content__inner > div.field > h2
Through thoughtful research and analysis, we continuously align our approach wi… section.basic-content--text-aligned-left > div.basic-content__inner > div.clearfix > p
These insights translate to unparalleled hospitality experiences as dynamic as … section.basic-content--text-aligned-left > div.basic-content__inner > div.clearfix > p
LEARN MORE div.paragraph > div.field > div.field__item > a.link

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
1 Hotels div.dynamic-background-hover-cards > div.container-bg > div.mobile-logo > h4

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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●Select elements have associated label elements.
●`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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○`<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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○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