Accessibility

F

Heading Hierarchy

Action

54 headings, 8 skip(s)

FIX

54 headings, 8 skip(s)

Multiple H1 headings (3 found)

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

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 Top Sports
H1 Community-Powered Motivation
H1 Community-Powered Motivation duplicate H1
H3 If you're active, Strava was made for you. Our mobile app and website enhance the experience of sport and connect millions of athletes from around the world. We're the social network for those who str skipped
H3 Start by sweating.
H3 Get better by analysis.
H3 Dive into details on desktop.
H4 Join Us Now
H2 Join for the tracking, stay for the community.
H4 Open, tap, go. skipped
H4 A no BS network.
H4 The ultimate athlete resource.
H2 Explore our features.
H4 Track & Analyze skipped
H4 Share & Connect
H4 Explore & Compete
H3 Ready to give it a shot?
H4 Join Us Now
H3 More features, more fun. We strive to deliver an experience to match their enthusiasm.
H2 Feature highlight: Beacon.
H2 Here's how a Strava subscription takes your experience to the next level.
H4 Track & Analyze skipped
H4 Share & Connect
H4 Explore & Compete
H4 Join Us Now
H3 You don't have to run or ride to love our features. Strava works with many of your other favorite sports, like skiing, kiteboarding, crossfit, kayaking, inline skating, rock climbing, surfing, yoga an
H3 Strava Features
H3 Strava Subscription
H1 Community-Powered Motivation duplicate H1
H3 If you're active, Strava was made for you. Our mobile app and website enhance the experience of sport and connect millions of athletes from around the world. We're the social network for those who str skipped
H3 Start by sweating.
H3 Get better by analysis.
H3 Dive into details on desktop.
H4 Join us for free.
H2 Join for the tracking, stay for the community.
H4 Open, tap, go. skipped
H4 A no BS network.
H4 The ultimate athlete resource.
H2 Explore our features.
H4 Track & Analyze skipped
H4 Share & Connect
H4 Explore & Compete
H3 Ready to give it a shot?
H4 Join Us Now
H3 More features, more fun. We strive to deliver an experience to match their enthusiasm.
H2 Feature highlight: Beacon.
H2 Here's how a Strava subscription takes your experience to the next level.
H4 Track & Analyze skipped
H4 Share & Connect
H4 Explore & Compete
H4 Try
H3 You don't have to run or ride to love our features. Strava works with many of your other favorite sports, like skiing, kiteboarding, crossfit, kayaking, inline skating, rock climbing, surfing, yoga an
H3 Strava Features
H3 Strava Subscription

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

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

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: strava

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

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

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

4 navigation landmark(s) detected

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 4 <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.

B

Landmark Structure

7 landmarks

REVIEW

7 landmarks

<main> landmark present

4 <nav> landmark(s) found

2 of 4 <nav> elements are unlabeled

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

No banner (header) landmark

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

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

5 of 10 controls have issues

REVIEW

5 of 10 controls have issues

5 control(s) without accessible label

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

Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">; <input type="checkbox" id="EZDrawer__checkbox_strava_mobile_menu">

5 control(s) properly labeled

10 controls

5 labeled

0 placeholder only

5 unlabeled

Control	Type	Label	Method
#CybotCookiebotDialogBodyLevelButtonNecessary	checkbox	Essential	for/id
#CybotCookiebotDialogBodyLevelButtonPreferences	checkbox	Functional	for/id
#CybotCookiebotDialogBodyLevelButtonStatistics	checkbox	Performance	for/id
#CybotCookiebotDialogBodyLevelButtonMarketing	checkbox	Targeting	for/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformation	checkbox	Do not sell or share my personal information	for/id
#CybotCookiebotDialogBodyLevelButtonPreferencesInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonStatisticsInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonMarketingInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonNecessaryInline	checkbox	(none)	none
#EZDrawer__checkbox_strava_mobile_menu	checkbox	(none)	none

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

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Favicon & Branding

20 icon(s) detected

REVIEW

20 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Alt Text Quality

1 of 60 images have issues

PASS

1 of 60 images have issues

1 image(s) with generic alt text

29 decorative image(s) correctly marked

30 image(s) with good alt text

60 images 30 good alt text 29 decorative 1 generic

Issue	Count
generic	1 image(s)

A

Link & Button Quality

110 links, 29 buttons — all OK

PASS

110 links, 29 buttons — all OK

21 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.cookiebot.com/en/what-is-behind-powered-by-cookiebot/?utm_source=banner_cb&utm_medium=referral&utm_content=v2; https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496; https://www.cookiebot.com/goto/privacy-policy/; https://www.strava.com/legal/privacy#cookies-and-similar-technologies; https://twitter.com/en/privacy; https://www.strava.com/legal/privacy#cookies-and-similar-technologies; https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496; https://www.strava.com/legal/privacy#cookies-and-similar-technologies; https://www.facebook.com/policy.php/; https://business.safety.google/privacy/ (+11 more)

89 link(s) with descriptive text

110 links

0 empty

0 generic text

21 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.cookiebot.com/en/what-is-beh…	Cookiebot by Usercentrics - op…	new tab	Add '(opens in new tab)' to text
https://www.amazon.com/gp/help/customer/…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.cookiebot.com/goto/privacy-p…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.strava.com/legal/privacy#coo…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://twitter.com/en/privacy	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.strava.com/legal/privacy#coo…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.amazon.com/gp/help/customer/…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.strava.com/legal/privacy#coo…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/policy.php/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.redditinc.com/policies/priva…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.strava.com/legal/privacy#coo…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/legal/privacy-pol…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.cookiebot.com	Cookiebot	new tab	Add '(opens in new tab)' to text
/legal/terms	Terms of Service	new tab	Add '(opens in new tab)' to text
/legal/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://twitter.com/strava	Twitter	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/stravainc	YouTube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/strava/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/strava-…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Strava	Facebook	new tab	Add '(opens in new tab)' to text

118 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://www.cookiebot.com/en/what-is-behind-powered-by-cookiebot/?utm_source=banner_cb&utm_medium=referral&utm_content=v2; https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496; https://www.cookiebot.com/goto/privacy-policy/; https://www.strava.com/legal/privacy#cookies-and-similar-technologies; https://twitter.com/en/privacy; https://www.strava.com/legal/privacy#cookies-and-similar-technologies; https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496; https://www.strava.com/legal/privacy#cookies-and-similar-technologies; https://www.facebook.com/policy.php/; https://business.safety.google/privacy/ (+11 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Strava

192x192 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Strava ✓192×192 icon ✓512×512 icon ✗Start URL /dashboard ✓Display Mode standalone ✓

Name Strava Display Mode standalone Theme Color #FC5200 Background Color #222222 Icons 6 icon(s)

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Community-Powered Mo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Community-Powered Mo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Community-Powered Mo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Top Sports	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Join for the trackin…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore our features…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Feature highlight: B…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Here's how a Strava …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Join for the trackin…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore our features…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Feature highlight: B…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Here's how a Strava …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 If you're active, St…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Start by sweating.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Get	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 by analysis.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Dive into details on…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Ready to give it a s…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 More features, more …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 You don't have to ru…	21.00:1	3.0:1	#000000	#FFFFFF	Pass

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

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 29 passed

PASS

95

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.

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
GET APP `div.Header_items__xlCyf > div.SmartBanner_wrapper__5eRa3 > div.SmartBanner_smartBanner__8x4sY > a.Button_btn__EdK33`
Sign Up `div.Header_items__xlCyf > div.MobileNav_container__ki3E9 > div.MobileNav_right__xVNWr > a.Button_btn__EdK33`
Join Us Now `div.Mobile_container__dzJVJ > section.Hero_container__dwBFb > div.Hero_overlay__pFJ6Z > a.PillButton_pillButton__lT2Fo`
Join Us Now `div.Mobile_container__dzJVJ > section.Section_container__4WNJ1 > a.JoinTryCta_container__ZJPGJ > h4`
EXPLORE `div.Community_container__WfglZ > section.Section_container__4WNJ1 > a.PillButton_pillButton__lT2Fo > span`
Join Us Now `div.Community_container__WfglZ > section.Section_container__4WNJ1 > a.JoinTryCta_container__ZJPGJ > h4`
STRAVA SUBSCRIPTION `div.Homepage_container__m8Vvy > div.Mobile_container__dzJVJ > section.Section_container__4WNJ1 > span.Subscription_header__7D445`
Strava Features `div.Mobile_container__dzJVJ > div.Summary_container__vWu0R > div.Summary_features__ixBz6 > h3`
EXPLORE `div.Summary_container__vWu0R > div.Summary_features__ixBz6 > a.PillButton_pillButton__lT2Fo > span`
Log In `li > ul > li > a.Footer_highlight__3ACCZ`

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
If you're active, Strava was made for you. Our mobile app and website enhance t… `div.Homepage_container__m8Vvy > div.Mobile_container__dzJVJ > section.Section_container__4WNJ1 > h3`
Open, tap, go. `div.JoinAndStay_content__acYij > div.JoinAndStay_paragraphs__dTdy9 > div.JoinAndStay_paragraph__guLbH > h4`
Track & Analyze `div.ItemGrid_container__lWVNA > div.ItemGrid_items__NEEM5 > div.ItemGrid_item__Z0wTV > h4`
Track & Analyze `div.ItemGrid_container__lWVNA > div.ItemGrid_items__NEEM5 > div.ItemGrid_item__Z0wTV > 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

●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

●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.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[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.

○`<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.

○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.