Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 5 REVIEW 6 FIX

Alt Text Quality

Action

3 of 44 images have issues

FIX

3 of 44 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

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

1 image(s) with generic alt text

24 decorative image(s) correctly marked

17 image(s) with good alt text

44 images 17 good alt text 24 decorative 1 generic 2 missing

Issue	Count
missing	2 image(s)
generic	1 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

404 Error Page

Action

HTTP 502, bare page

FIX

HTTP 502, bare page

Unexpected status code: HTTP 502

Expected HTTP 404 but received 502. This may confuse search engine crawlers.

Got: HTTP 502

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 502 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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 ✗

Heading Hierarchy

Action

22 headings, 2 skip(s)

REVIEW

22 headings, 2 skip(s)

Multiple H1 headings (2 found)

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

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 → H4 (missing H3)

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

H1 Experience better HR and payroll
H1 Welcome back! You're on the way to better HR and payroll duplicate H1
H2 Take a self-guided product tour
H2 Managing and paying your people has never been easier
H5 TRUSTED BY MORE THAN skipped
H5 1,100,000 Clients
H5 WE PAY EVERY
H5 1 in 6 workers in the U.S.
H5 HELPING BUSINESSES FOR
H5 75 years
H2 No matter your business size, we've got you covered
H3 Small Business
H3 Midsized Business
H3 Large Business
H2 These HR Trends will affect how you work in 2025
H2 Latest news and events
H4 Now available: The latest issue of Today at Work from ADP Research skipped
H4 A new era of work starts now
H3 RUN Powered by ADP® #1 for small businesses, two years running, by G2
H2 Awards and recognition
H2 Get pricing specific to your business
H2 Get pricing specific to your business

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Form Accessibility

Action

7 of 26 controls have issues

REVIEW

7 of 26 controls have issues

7 control(s) without accessible label

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

Got: <input type="text" id="nav-search-field">; <input type="submit" id="header-search-submit">; <input type="submit" name="fxb.f82ab3f0-fb87-44a0-a157-482f5561c825.b1984bbb-e54e-4c48-801e-be3e75bd8a82">; <input type="submit" name="fxb.5bebbe6a-d423-4877-9cd9-65470fd3e8a8.97bff4e5-6d75-4c5a-8bcf-f174c63e7349">; <input type="submit" name="fxb.dd631d0e-2600-4acd-8688-170b4638c7a5.354f9577-29a5-485e-986c-38fd88d885de">; <input type="submit" name="fxb.d0366632-6f9a-4118-b8f9-208cf19968ec.d6f959b4-5cbb-4451-b553-aadbb7dc1867">; <input type="submit" name="fxb.c2557eb6-7159-4f38-83b9-99c27b29718d.4b1bd080-628f-4c16-8f09-3bffdee72504">

19 control(s) properly labeled

26 controls

19 labeled

0 placeholder only

7 unlabeled

Control	Type	Label	Method
input	number	Number of Employees	aria-label
input	input	select an option	aria-label
fxb.f82ab3f0-fb87-44a0-a157-482f5561c825.Fields[a4be697c-949d-4a66-8a13-f1bb3d0a354b].Value	radio		none
fxb.f82ab3f0-fb87-44a0-a157-482f5561c825.Fields[a4be697c-949d-4a66-8a13-f1bb3d0a354b].Value	radio		none
#fxb_5bebbe6a-d423-4877-9cd9-65470fd3e8a8_Fields_b718e8e9-045a-4d8d-a7a7-f84b14206c28__Value	email	Business Email	for/id
#fxb_dd631d0e-2600-4acd-8688-170b4638c7a5_Fields_ecbca9fb-7d32-440e-b8c0-fd8896c233d9__Value	text	Full Name	for/id
#fxb_dd631d0e-2600-4acd-8688-170b4638c7a5_Fields_9975581c-407a-4890-ab98-370e29780982__Value	email	Email	for/id
#fxb_dd631d0e-2600-4acd-8688-170b4638c7a5_Fields_337fc026-6bb9-40f4-88d6-a1026c3b51b3__Value	tel	Phone Number	for/id
#fxb_dd631d0e-2600-4acd-8688-170b4638c7a5_Fields_9dbadf5d-0acf-47f0-a442-5b20a900b819__Value	text	Business Name	for/id
#fxb_dd631d0e-2600-4acd-8688-170b4638c7a5_Fields_b641bf84-b017-4bee-8b07-69d81bdda971__Value	number	# of Employees	for/id
#fxb_dd631d0e-2600-4acd-8688-170b4638c7a5_Fields_305e47a7-15c7-4d5e-bfb2-e03255042e8d__Value	select	Country	for/id
fxb.dd631d0e-2600-4acd-8688-170b4638c7a5.Fields[617b4d09-4fe9-463f-b538-8fa5f996469d].Value	radio		none
fxb.dd631d0e-2600-4acd-8688-170b4638c7a5.Fields[617b4d09-4fe9-463f-b538-8fa5f996469d].Value	radio		none
#fxb_dd631d0e-2600-4acd-8688-170b4638c7a5_Fields_41a0169c-e146-43fd-b1b6-e40c01637d3f__Value	checkbox		none
select	select	Country	aria-label
fxb.d0366632-6f9a-4118-b8f9-208cf19968ec.Fields[cafa6075-f85f-4350-bd3f-3a335798ce53].Value	radio		none
fxb.d0366632-6f9a-4118-b8f9-208cf19968ec.Fields[cafa6075-f85f-4350-bd3f-3a335798ce53].Value	radio		none
fxb.c2557eb6-7159-4f38-83b9-99c27b29718d.Fields[f71d7db1-16d2-4fc0-aa65-e89271c5f230].Value	radio		none
fxb.c2557eb6-7159-4f38-83b9-99c27b29718d.Fields[f71d7db1-16d2-4fc0-aa65-e89271c5f230].Value	radio		none
fxb.f82ab3f0-fb87-44a0-a157-482f5561c825.b1984bbb-e54e-4c48-801e-be3e75bd8a82	submit	(none)	none
#nav-search-field	text	(none)	none
fxb.5bebbe6a-d423-4877-9cd9-65470fd3e8a8.97bff4e5-6d75-4c5a-8bcf-f174c63e7349	submit	(none)	none
fxb.d0366632-6f9a-4118-b8f9-208cf19968ec.d6f959b4-5cbb-4451-b553-aadbb7dc1867	submit	(none)	none
#header-search-submit	submit	(none)	none
fxb.dd631d0e-2600-4acd-8688-170b4638c7a5.354f9577-29a5-485e-986c-38fd88d885de	submit	(none)	none
fxb.c2557eb6-7159-4f38-83b9-99c27b29718d.4b1bd080-628f-4c16-8f09-3bffdee72504	submit	(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

Link & Button Quality

Action

1 issue(s) across 310 links and 26 buttons

REVIEW

1 issue(s) across 310 links and 26 buttons

5 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/what-we-offer/payroll/payroll-for-1-49-employees/payroll-packages.aspx?segme…"]; a[href="/what-we-offer/payroll/payroll-for-1-49-employees/payroll-packages.aspx?segme…"]; a[href="/what-we-offer/products/lyric.aspx"]; a[href="#"]; a[href="https://signin.adp.com/"]

31 link(s) open in new tab without warning

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

Got: https://www.adpri.org/today-at-work; https://www.adpri.org/; https://www.adpri.org/; https://ventures.adp.com; https://jobs.adp.com/?rb=ADP_COM; https://jobs.adp.com/?rb=ADP_COM; https://tech.adp.com/; https://investors.adp.com/; https://mediacenter.adp.com/; /privacy.aspx (+21 more)

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.close-icn (#1862 on page)

274 link(s) with descriptive text

310 links

0 empty

0 generic text

31 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/what-we-offer/payroll/payroll-for-1-49-…	Compare Packages F…	img no alt	Add alt attribute to the image
/what-we-offer/payroll/payroll-for-1-49-…	Compare Packages …	img no alt	Add alt attribute to the image
/what-we-offer/products/lyric.aspx	Lyric HCM Empower…	img no alt	Add alt attribute to the image
https://www.adpri.org/today-at-work	Discover the latest Today at W…	new tab	Add '(opens in new tab)' to text
https://www.adpri.org/	ADP Research	new tab	Add '(opens in new tab)' to text
https://www.adpri.org/	Overview	new tab	Add '(opens in new tab)' to text
https://ventures.adp.com	ADP Ventures	new tab	Add '(opens in new tab)' to text
https://jobs.adp.com/?rb=ADP_COM	Careers	new tab	Add '(opens in new tab)' to text
https://jobs.adp.com/?rb=ADP_COM	All Open Roles	new tab	Add '(opens in new tab)' to text
https://tech.adp.com/	Tech Careers	new tab	Add '(opens in new tab)' to text
https://investors.adp.com/	Investors	new tab	Add '(opens in new tab)' to text
https://mediacenter.adp.com/	Media	new tab	Add '(opens in new tab)' to text
/privacy.aspx	Privacy Statement	new tab	Add '(opens in new tab)' to text
/legal.aspx	Terms of Use	new tab	Add '(opens in new tab)' to text
/privacy.aspx	privacy	new tab	Add '(opens in new tab)' to text
/privacy.aspx	Privacy Statement	new tab	Add '(opens in new tab)' to text
/legal.aspx	Terms of Use	new tab	Add '(opens in new tab)' to text
/privacy.aspx	privacy	new tab	Add '(opens in new tab)' to text
https://www.adpresearch.com/today-at-wor…	The latest issue of Today at W…	new tab	Add '(opens in new tab)' to text
https://info.adp.com/Women-at-Work-2026-…	Register	new tab	Add '(opens in new tab)' to text
tel:8002255237	800-225-5237	new tab	Add '(opens in new tab)' to text
/privacy.aspx	Privacy Statement	new tab	Add '(opens in new tab)' to text
/legal.aspx	Terms of Use	new tab	Add '(opens in new tab)' to text
/privacy.aspx	privacy	new tab	Add '(opens in new tab)' to text
https://jobs.adp.com/?rb=ADP_COM	Careers	new tab	Add '(opens in new tab)' to text
https://ventures.adp.com/	ADP Ventures	new tab	Add '(opens in new tab)' to text
https://investors.adp.com	Investors	new tab	Add '(opens in new tab)' to text
https://mediacenter.adp.com/	Media	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/AutomaticDataPr…	ADP Facebook Page	new tab	Add '(opens in new tab)' to text
https://twitter.com/adp	ADP X (Twitter) Page	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/adp	ADP YouTube Channel	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/adp	ADP LinkedIn Page	new tab	Add '(opens in new tab)' to text
#	Chat	img no alt	Add alt attribute to the image
https://signin.adp.com/	Sign In	img no alt	Add alt attribute to the image
/privacy.aspx	privacy	new tab	Add '(opens in new tab)' to text
/privacy.aspx	privacy	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

299 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/what-we-offer/payroll/payroll-for-1-49-employees/payroll-packages.aspx?segme…"]; a[href="/what-we-offer/payroll/payroll-for-1-49-employees/payroll-packages.aspx?segme…"]; a[href="/what-we-offer/products/lyric.aspx"]; a[href="#"]; a[href="https://signin.adp.com/"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://www.adpri.org/today-at-work; https://www.adpri.org/; https://www.adpri.org/; https://ventures.adp.com; https://jobs.adp.com/?rb=ADP_COM; https://jobs.adp.com/?rb=ADP_COM; https://tech.adp.com/; https://investors.adp.com/; https://mediacenter.adp.com/; /privacy.aspx (+21 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

Icon-only buttons need an aria-label so screen readers can announce them.

button.close-icn (#1862 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

9 icon(s) detected

REVIEW

9 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 Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 5 fail WCAG AA

REVIEW

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

15 pass 5 fail WCAG AA

title Payroll, HR and Tax Services | ADP Offic…

1.05:1

#000000

#010035

needs 4.5:1 (normal text)

16px · top of page (header area)

strong It's tax time!

1.05:1

#000000

#010035

needs 3.0:1 (large text)

16px · top of page (header area)

span Questions about W-2s or 1099s? Get guida…

1.05:1

#000000

#010035

needs 4.5:1 (normal text)

16px · top of page (header area)

a For Employees

1.05:1

#000000

#010035

needs 4.5:1 (normal text)

16px · top of page (header area)

span •

1.05:1

#000000

#010035

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Experience better HR…	18.89:1	3.0:1	#000000	#F2F3F3	Pass
h1 Welcome back! You'r…	18.89:1	3.0:1	#000000	#F2F3F3	Pass
h2 Take a self-guided p…	18.89:1	3.0:1	#000000	#F2F3F3	Pass
h2 Managing and paying …	18.89:1	3.0:1	#000000	#F2F3F3	Pass
h2 No matter your busin…	18.89:1	3.0:1	#000000	#F2F3F3	Pass
h2 These HR Trends will…	18.89:1	3.0:1	#000000	#F2F3F3	Pass
h2 Latest news and even…	18.89:1	3.0:1	#000000	#F2F3F3	Pass
h2 Awards and recogniti…	18.89:1	3.0:1	#000000	#F2F3F3	Pass
h2 Get pricing specific…	18.89:1	3.0:1	#000000	#F2F3F3	Pass
h2 Get pricing specific…	18.89:1	3.0:1	#000000	#F2F3F3	Pass
h3 Small Business	18.89:1	3.0:1	#000000	#F2F3F3	Pass
h3 Midsized Business	18.89:1	3.0:1	#000000	#F2F3F3	Pass
h3 Large Business	18.89:1	3.0:1	#000000	#F2F3F3	Pass
h3 RUN Powered by ADP®…	18.89:1	3.0:1	#000000	#F2F3F3	Pass
title Payroll, HR and Tax …	1.05:1	4.5:1	#000000	#010035	Fail
strong It's tax time!	1.05:1	3.0:1	#000000	#010035	Fail
span Questions about W-2s…	1.05:1	4.5:1	#000000	#010035	Fail
a For Employees	1.05:1	4.5:1	#000000	#010035	Fail
span •	1.05:1	4.5:1	#000000	#010035	Fail
a For Employers	21.00:1	4.5: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.

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 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

Lighthouse Accessibility Audits

Score 94/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.

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.mobile-nav > div.call-menu > div.menu-wrap > button.close-icn `div.mobile-nav > div.call-menu > div.menu-wrap > button.close-icn`

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

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
TRUSTED BY MORE THAN `div.col-xs-12 > div.card > div.card-body > h5.title-brow`
div.col-xs-12 > div.card > div.card-body > h4.title `div.col-xs-12 > div.card > div.card-body > h4.title`

These are opportunities to improve keyboard navigation in your application.

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
The latest issue of Today at Work from ADP Research `div.col-xs-12 > div.card > div.card-body > a.btn`

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

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

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

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

○`<object>` elements have alternate text

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

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