Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 2 REVIEW 7 FIX

Heading Hierarchy

Action

37 headings, 3 skip(s)

FIX

37 headings, 3 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

1 empty heading(s)

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

H3 Well Data Lifecycle
H4 WellView Allez
H4 RigView
H4 Well Reliability
H4 Well Integrity
H4 Peloton Frac
H4 SiteView Allez
H4 SiteView Go
H4 Peloton Ram
H4 Peloton Innova
H4 Peloton Equipment
H4 Peloton Water
H4 Peloton Water Go
H4 Peloton Dashboards
H3 Production Data Lifecycle
H4 ProdView
H4 ProdView Go
H4 Peloton Water
H4 Peloton Water Go
H4 Peloton Ops
H4 Peloton Dashboards
H3 Land Data Management
H4 LandView
H4 Peloton Water Go
H4 LandView Map
H4 Peloton Broker
H4 Peloton Dashboards
H2 (empty)
H2 PELOTON RENEWABLES
H2 BREAKING THE CYCLEOF BAD DATA
H5 WELL DATA LIFECYCLE skipped
H2 WELL DATA LIFECYCLE
H5 PRODUCTION DATA LIFECYCLE skipped
H2 PRODUCTION DATA LIFECYCLE
H5 LAND DATA MANAGEMENT skipped
H2 LAND DATA MANAGEMENT
H2 PELOTON RENEWABLES

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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 ▾

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 ▾

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

Link & Button Quality

Action

6 issue(s) across 301 links and 8 buttons

FIX

6 issue(s) across 301 links and 8 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.peloton.com/peloton-platform-overview?hsLang=en; https://www.peloton.com/peloton-platform-overview?hsLang=en

4 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://communications.peloton.com/2026-peloton-platforum?hsLang=en ("LEARN MORE"); https://starlink.typeform.com/peloton?utm_source=starlink&utm_medium=banner&utm_campaign=starlink_signup ("LEARN MORE"); https://www.peloton.com/products/well-data-lifecycle/peloton-innova?hsLang=en ("LEARN MORE"); https://www.peloton.com/renewables?hsLang=en ("LEARN MORE")

6 link(s) open in new tab without warning

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

Got: https://platformv2.peloton.com/?_gl=1*sf55bl*_gcl_au*MjAzMzI4MjM5Ny4xNzQ2NzAzMzgy*_ga*MTk2OTAxMjgxOC4xNzQ2NzAzMzgy*_ga_TZN35GWCZ2*czE3NDY3MjgxNzgkbzIkZzEkdDE3NDY3MjgzNDIkajYwJGwwJGgw; https://frac.peloton.com/?_gl=1*sf55bl*_gcl_au*MjAzMzI4MjM5Ny4xNzQ2NzAzMzgy*_ga*MTk2OTAxMjgxOC4xNzQ2NzAzMzgy*_ga_TZN35GWCZ2*czE3NDY3MjgxNzgkbzIkZzEkdDE3NDY3MjgzNDIkajYwJGwwJGgw; https://premiumsupport.peloton.com/Account/LogOn?ReturnUrl=%2f%3f_gl%3d1*xcosmu*_gcl_au*MjAzODY3NDQ0Ny4xNzQ3MDUxNjg2*_ga*MTU5ODI4MDA0NS4xNzQ3MDUxNjg2*_ga_TZN35GWCZ2*czE3NDc5NDYzODQkbzE1JGcxJHQxNzQ3OTQ2NDIxJGoyMyRsMCRoMCRkcEdMTkFHZzdwMWtJaW5vNUM3bW45alNmc2h3NmxjMlMyUQ..&_gl=1*xcosmu*_gcl_au*MjAzODY3NDQ0Ny4xNzQ3MDUxNjg2*_ga*MTU5ODI4MDA0NS4xNzQ3MDUxNjg2*_ga_TZN35GWCZ2*czE3NDc5NDYzODQkbzE1JGcxJHQxNzQ3OTQ2NDIxJGoyMyRsMCRoMCRkcEdMTkFHZzdwMWtJaW5vNUM3bW45alNmc2h3NmxjMlMyUQ..; https://pelotonwellfocused.bamboohr.com/careers/; https://pelotonwellfocused.bamboohr.com/careers/; https://www.peloton.com/hubfs/PELOTON_2024_Breaking_The_Cycle_of_Bad_Data.pdf?hsLang=en

289 link(s) with descriptive text

301 links

2 empty

4 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://platformv2.peloton.com/?_gl=1*sf…	Peloton Platform	new tab	Add '(opens in new tab)' to text
https://frac.peloton.com/?_gl=1sf55bl_…	Peloton Frac	new tab	Add '(opens in new tab)' to text
https://premiumsupport.peloton.com/Accou…	Locksmith	new tab	Add '(opens in new tab)' to text
https://pelotonwellfocused.bamboohr.com/…	Careers	new tab	Add '(opens in new tab)' to text
https://pelotonwellfocused.bamboohr.com/…	Careers	new tab	Add '(opens in new tab)' to text
https://www.peloton.com/peloton-platform…	(empty)	empty	Add link text or aria-label
https://www.peloton.com/peloton-platform…	(empty)	empty	Add link text or aria-label
https://communications.peloton.com/2026-…	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: 2026 Peloton Platforum?Hslang=En
https://starlink.typeform.com/peloton?ut…	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Peloton?Utm Source=Starlink&Utm Medium=Banner&Utm Campaign=Starlink Signup
https://www.peloton.com/products/well-da…	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Peloton Innova?Hslang=En
https://www.peloton.com/renewables?hsLan…	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Renewables?Hslang=En
https://www.peloton.com/hubfs/PELOTON_20…	READ STORY	new tab	Add '(opens in new tab)' to text

297 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.peloton.com/peloton-platform-overview?hsLang=en; https://www.peloton.com/peloton-platform-overview?hsLang=en

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

https://communications.peloton.com/2026-peloton-platforum?hsLang=en ("LEARN MORE"); https://starlink.typeform.com/peloton?utm_source=starlink&utm_medium=banner&utm_campaign=starlink_signup ("LEARN MORE"); https://www.peloton.com/products/well-data-lifecycle/peloton-innova?hsLang=en ("LEARN MORE"); https://www.peloton.com/renewables?hsLang=en ("LEARN MORE")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://platformv2.peloton.com/?_gl=1*sf55bl*_gcl_au*MjAzMzI4MjM5Ny4xNzQ2NzAzMzgy*_ga*MTk2OTAxMjgxOC4xNzQ2NzAzMzgy*_ga_TZN35GWCZ2*czE3NDY3MjgxNzgkbzIkZzEkdDE3NDY3MjgzNDIkajYwJGwwJGgw; https://frac.peloton.com/?_gl=1*sf55bl*_gcl_au*MjAzMzI4MjM5Ny4xNzQ2NzAzMzgy*_ga*MTk2OTAxMjgxOC4xNzQ2NzAzMzgy*_ga_TZN35GWCZ2*czE3NDY3MjgxNzgkbzIkZzEkdDE3NDY3MjgzNDIkajYwJGwwJGgw; https://premiumsupport.peloton.com/Account/LogOn?ReturnUrl=%2f%3f_gl%3d1*xcosmu*_gcl_au*MjAzODY3NDQ0Ny4xNzQ3MDUxNjg2*_ga*MTU5ODI4MDA0NS4xNzQ3MDUxNjg2*_ga_TZN35GWCZ2*czE3NDc5NDYzODQkbzE1JGcxJHQxNzQ3OTQ2NDIxJGoyMyRsMCRoMCRkcEdMTkFHZzdwMWtJaW5vNUM3bW45alNmc2h3NmxjMlMyUQ..&_gl=1*xcosmu*_gcl_au*MjAzODY3NDQ0Ny4xNzQ3MDUxNjg2*_ga*MTU5ODI4MDA0NS4xNzQ3MDUxNjg2*_ga_TZN35GWCZ2*czE3NDc5NDYzODQkbzE1JGcxJHQxNzQ3OTQ2NDIxJGoyMyRsMCRoMCRkcEdMTkFHZzdwMWtJaW5vNUM3bW45alNmc2h3NmxjMlMyUQ..; https://pelotonwellfocused.bamboohr.com/careers/; https://pelotonwellfocused.bamboohr.com/careers/; https://www.peloton.com/hubfs/PELOTON_2024_Breaking_The_Cycle_of_Bad_Data.pdf?hsLang=en

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

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

404 Error Page

Action

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

404 Page Quality ✓ Custom 404 Page

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

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

h2 OF BAD DATA

1.94:1

#000000

#393D4B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 WELL DATA LIFECYCLE

1.94:1

#000000

#393D4B

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h2 PRODUCTION DATA LIFECYCLE

1.94:1

#000000

#393D4B

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h2 LAND DATA MANAGEMENT

1.94:1

#000000

#393D4B

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h2 PELOTON RENEWABLES

1.94:1

#000000

#393D4B

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Well Data Lifecycle

1.94:1

#000000

#393D4A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Production Data Lifecycle

1.94:1

#000000

#393D4B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Land Data Management

1.94:1

#000000

#393D4B

needs 3.0:1 (large text)

19px · bottom of viewport

title Peloton | Oil & Gas Software Solutions f…

1.97:1

#000000

#393E4D

needs 4.5:1 (normal text)

16px · top of page (header area)

p By clicking “Accept”, you agree to t…

2.00:1

#000000

#393F4F

needs 4.5:1 (normal text)

16px · top of page (header area)

p If you decline, your information won’t…

1.97:1

#000000

#393E4D

needs 4.5:1 (normal text)

16px · top of page (header area)

button Cookies settings

1.97:1

#000000

#393E4D

needs 4.5:1 (normal text)

16px · top of page (header area)

button Accept

1.97:1

#000000

#393E4D

needs 4.5:1 (normal text)

16px · above the fold

button Decline

1.94:1

#000000

#383D4C

needs 4.5:1 (normal text)

16px · above the fold

a Skip to content

1.94:1

#000000

#383D4C

needs 4.5:1 (normal text)

16px · above the fold

span Login

1.94:1

#000000

#383D4C

needs 4.5:1 (normal text)

16px · above the fold

a Peloton Platform

1.94:1

#000000

#383D4C

needs 4.5:1 (normal text)

16px · above the fold

a Peloton Frac

1.94:1

#000000

#383D4D

needs 4.5:1 (normal text)

16px · above the fold

a Locksmith

1.94:1

#000000

#383D4D

needs 4.5:1 (normal text)

16px · above the fold

a Request A Demo

1.94:1

#000000

#383D4C

needs 4.5:1 (normal text)

16px · above the fold

3 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 OF BAD DATA	1.94:1	3.0:1	#000000	#393D4B	Fail
h2 WELL DATA LIFECYCLE	1.94:1	3.0:1	#000000	#393D4B	Fail
h2 PRODUCTION DATA LIFE…	1.94:1	3.0:1	#000000	#393D4B	Fail
h2 LAND DATA MANAGEMEN…	1.94:1	3.0:1	#000000	#393D4B	Fail
h2 PELOTON RENEWABLES	1.94:1	3.0:1	#000000	#393D4B	Fail
h3 Well Data Lifecycle	1.94:1	3.0:1	#000000	#393D4A	Fail
h3 Production Data Life…	1.94:1	3.0:1	#000000	#393D4B	Fail
h3 Land Data Management	1.94:1	3.0:1	#000000	#393D4B	Fail
title Peloton \| Oil & Gas …	1.97:1	4.5:1	#000000	#393E4D	Fail
p By clicking “Accep…	2.00:1	4.5:1	#000000	#393F4F	Fail
p If you decline, your…	1.97:1	4.5:1	#000000	#393E4D	Fail
button Cookies settings	1.97:1	4.5:1	#000000	#393E4D	Fail
button Accept	1.97:1	4.5:1	#000000	#393E4D	Fail
button Decline	1.94:1	4.5:1	#000000	#383D4C	Fail
a Skip to content	1.94:1	4.5:1	#000000	#383D4C	Fail
span Login	1.94:1	4.5:1	#000000	#383D4C	Fail
a Peloton Platform	1.94:1	4.5:1	#000000	#383D4C	Fail
a Peloton Frac	1.94:1	4.5:1	#000000	#383D4D	Fail
a Locksmith	1.94:1	4.5:1	#000000	#383D4D	Fail
a Request A Demo	1.94:1	4.5:1	#000000	#383D4C	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.

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

Skip navigation link present

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

A+

Alt Text Quality

All 49 images OK

PASS

All 49 images OK

1 decorative image(s) correctly marked

48 image(s) with good alt text

49 images 48 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
term	text	Search	aria-label

Lighthouse Accessibility Audits

Score 92/100 — 3 failing, 28 passed

PASS

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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header__navigation_mob > nav > div.mobile-menu-panel-header > div.header_close_icon `div.header__navigation_mob > nav > div.mobile-menu-panel-header > div.header_close_icon`

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.

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
Accept `div#hs-eu-cookie-confirmation-buttons-area > div#hs-eu-confirmation-button-group > div#hs-eu-opt-in-buttons > button#hs-eu-confirmation-button`
LEARN MORE `div.container > div.update-banner-row > div.update-banner-link > a`
USE CASES `div.use-cases-row > div.use-cases-heading-wrap > div.use-cases-heading-left > div.use-case-subtitle`
MORE USE CASES `div.container > div.use-cases-row > a.pb-more-btn > span`
Our Company `div.two-column-tab-content > div.two-column-tab-content-row > div.two-column-tab-buttons > button.two-column-tab-btn`
FIND OUT MORE `div.two-column-tab-content > div.two-column-tab-content-row > div#tab_1 > a.pt-btn`
FIND OUT MORE `div.two-column-img-text-section > div.two-column-section-content > div.two-column-section-content-wrap > a.pt-btn`

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
PRODUCTION DATA LIFECYCLE `div.box_circle_content > div.box_circle > div.bc_box_title > h5`

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

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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 buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

○Uses ARIA roles only on compatible elements

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