Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 6 REVIEW 7 FIX

Link & Button Quality

Action

16 issue(s) across 199 links and 70 buttons

FIX

16 issue(s) across 199 links and 70 buttons

6 link(s) with generic text

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

Got: /even-better ("More"); /future-perfect ("More"); /explainers ("More"); /politics ("More"); /culture ("More"); /advice ("More")

11 link(s) open in new tab without warning

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

Got: https://www.nbcnews.com/business/consumer/canada-trump-tariffs-talks-hockey-s…; https://apnews.com/article/iran-war-southeast-asia-cambodia-education-fe1b94c…; https://www.hollywoodreporter.com/tv/tv-news/hayden-panettiere-dead-actress-h…; https://www.rollingstone.com/culture/culture-news/lindsay-clancy-murder-trial…; https://www.nbcnews.com/business/consumer/canada-trump-tariffs-talks-hockey-s…; https://apnews.com/article/iran-war-southeast-asia-cambodia-education-fe1b94c…; https://www.hollywoodreporter.com/tv/tv-news/hayden-panettiere-dead-actress-h…; https://www.rollingstone.com/culture/culture-news/lindsay-clancy-murder-trial…; https://www.voxmedia.com/legal/cookie-policy; https://www.voxmedia.com/legal/cookie-policy (+1 more)

10 button(s) with no accessible text

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

Got: button (#2706 on page); button (#2735 on page); button (#2835 on page); button (#2867 on page); button (#2883 on page); button (#2934 on page); button (#2958 on page); button (#2989 on page); button (#3051 on page); button (#3069 on page)

182 link(s) with descriptive text

199 links

0 empty

6 generic text

11 new tab

10 empty buttons

Element	Text	Issue	Suggested Fix
https://www.nbcnews.com/business/consume…	Canada is racing to reach a tr…	new tab	Add '(opens in new tab)' to text
https://apnews.com/article/iran-war-sout…	threatening education for mill…	new tab	Add '(opens in new tab)' to text
https://www.hollywoodreporter.com/tv/tv-…	died at age 36	new tab	Add '(opens in new tab)' to text
https://www.rollingstone.com/culture/cul…	A GoFundMe for Lindsay Clancy�…	new tab	Add '(opens in new tab)' to text
https://www.nbcnews.com/business/consume…	Canada is racing to reach a tr…	new tab	Add '(opens in new tab)' to text
https://apnews.com/article/iran-war-sout…	threatening education for mill…	new tab	Add '(opens in new tab)' to text
https://www.hollywoodreporter.com/tv/tv-…	died at age 36	new tab	Add '(opens in new tab)' to text
https://www.rollingstone.com/culture/cul…	A GoFundMe for Lindsay Clancy�…	new tab	Add '(opens in new tab)' to text
/even-better	More	generic text	Replace with descriptive text
Before: More Suggested: Even Better
/future-perfect	More	generic text	Replace with descriptive text
Before: More Suggested: Future Perfect
/explainers	More	generic text	Replace with descriptive text
Before: More Suggested: Explainers
/politics	More	generic text	Replace with descriptive text
Before: More Suggested: Politics
/culture	More	generic text	Replace with descriptive text
Before: More Suggested: Culture
/advice	More	generic text	Replace with descriptive text
Before: More Suggested: Advice
https://www.voxmedia.com/legal/cookie-po…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.voxmedia.com/legal/cookie-po…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

242 links and buttons have descriptive text

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

/even-better ("More"); /future-perfect ("More"); /explainers ("More"); /politics ("More"); /culture ("More"); /advice ("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://www.nbcnews.com/business/consumer/canada-trump-tariffs-talks-hockey-s…; https://apnews.com/article/iran-war-southeast-asia-cambodia-education-fe1b94c…; https://www.hollywoodreporter.com/tv/tv-news/hayden-panettiere-dead-actress-h…; https://www.rollingstone.com/culture/culture-news/lindsay-clancy-murder-trial…; https://www.nbcnews.com/business/consumer/canada-trump-tariffs-talks-hockey-s…; https://apnews.com/article/iran-war-southeast-asia-cambodia-education-fe1b94c…; https://www.hollywoodreporter.com/tv/tv-news/hayden-panettiere-dead-actress-h…; https://www.rollingstone.com/culture/culture-news/lindsay-clancy-murder-trial…; https://www.voxmedia.com/legal/cookie-policy; https://www.voxmedia.com/legal/cookie-policy (+1 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 (#2706 on page); button (#2735 on page); button (#2835 on page); button (#2867 on page); button (#2883 on page); button (#2934 on page); button (#2958 on page); button (#2989 on page); button (#3051 on page); button (#3069 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

Mobile Keyboard & Autofill

Action

2/2 eligible field(s) missing autocomplete or inputmode

FIX

2/2 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email" name="email" id="email">

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" name="email" id="email">

Mobile-Readable Font Sizes

Action

52% of visible text renders at >= 12 CSS px (155 below threshold)

FIX

52% of visible text renders at >= 12 CSS px (155 below threshold)

155 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <a> 11.0px ("Become a Member"); <span> 11.0px ("Climate"); <span> 11.0px ("By"); <span> 11.0px ("Benji Jones"); <span> 11.0px ("Policy").

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

43 headings

REVIEW

43 headings

No H1 heading found

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

H2 Making sense of it all:
H2 Politics
H2 Recommended For You
H2 Even Better
H2 Future Perfect
H2 Most Popular
H2 Listen
H2 Today, Explained
H2 Explainers
H2 Politics
H2 Culture
H2 Advice
H2 More News
H2 Pagination
H2 Privacy Notice
H3 Ways we may use your data:
H2 Privacy Center
H3 Manage Consent Preferences
H4 Strictly Necessary Cookies 114 partners can use this purpose
H5 Ensure security, prevent and detect fraud, and fix errors 114 partners can use this special purpose
H4 Functional Cookies 153 partners can use this purpose
H5 Use limited data to select advertising 122 partners can use this purpose
H5 Use limited data to select content 30 partners can use this purpose
H5 Use profiles to select personalised content 27 partners can use this purpose
H5 Create profiles to personalise content 30 partners can use this purpose
H5 Deliver and present advertising and content 106 partners can use this special purpose
H5 Identify devices based on information transmitted automatically 89 partners can use this feature
H4 Performance Cookies 49 partners can use this purpose
H5 Link different devices 49 partners can use this feature
H4 Social Media & Embedded Content
H4 Targeting Cookies 91 partners can use this purpose
H5 Actively scan device characteristics for identification 26 partners can use this special feature
H5 Use precise geolocation data 47 partners can use this special feature
H5 Match and combine data from other data sources 68 partners can use this feature
H4 Measure content performance 53 partners can use this purpose
H4 Use profiles to select personalised advertising 86 partners can use this purpose
H5 Create profiles for personalised advertising 90 partners can use this purpose
H4 Understand audiences through statistics or combinations of data from different sources 96 partners can use this purpose
H5 Develop and improve services 116 partners can use this purpose
H5 Measure advertising performance 150 partners can use this purpose
H4 Store and/or access information on a device 129 partners can use this purpose
H4 Save and communicate privacy choices 98 partners can use this special purpose
H3 Vendors List

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

Iframe Accessibility

2/5 iframe(s) missing title; 0 placeholder(s)

REVIEW

2/5 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

Tap Target Adequacy

Action

4 tap target(s) too small or too close together

REVIEW

4 tap target(s) too small or too close together

4 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

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 ✓Page Title TikTok ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

7 icon(s) detected

REVIEW

7 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

title Vox

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Making sense of it a…	17.95:1	3.0:1	#000000	#FFF200	Pass
h2 Politics	17.95:1	3.0:1	#000000	#FFF200	Pass
h2 Recommended For You	17.95:1	3.0:1	#000000	#FFF200	Pass
h2 Even Better	17.95:1	3.0:1	#000000	#FFF200	Pass
h2 Future Perfect	17.95:1	3.0:1	#000000	#FFF200	Pass
h2 Most Popular	17.95:1	3.0:1	#000000	#FFF200	Pass
h2 Listen	17.95:1	3.0:1	#000000	#FFF200	Pass
h2 Today, Explained	17.95:1	3.0:1	#000000	#FFF200	Pass
h2 Explainers	17.95:1	3.0:1	#000000	#FFF200	Pass
h2 Politics	17.95:1	3.0:1	#000000	#FFF200	Pass
h2 Culture	17.95:1	3.0:1	#000000	#FFF200	Pass
h2 Advice	17.95:1	3.0:1	#000000	#FFF200	Pass
h2 More News	17.95:1	3.0:1	#000000	#FFF200	Pass
h2 Pagination	17.95:1	3.0:1	#000000	#FFF200	Pass
h2 Privacy Notice	17.95:1	3.0:1	#000000	#FFF200	Pass
h2 Privacy Center	17.95:1	3.0:1	#000000	#FFF200	Pass
h3 Ways we may use your…	17.95:1	3.0:1	#000000	#FFF200	Pass
h3 Manage Consent Prefe…	17.95:1	3.0:1	#000000	#FFF200	Pass
h3 Vendors List	17.95:1	3.0:1	#000000	#FFF200	Pass
title Vox	1.00:1	4.5:1	#000000	#000000	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

7 landmarks

PASS

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

Heading Text Quality

All 43 heading(s) have substantive, well-formed text

PASS

All 43 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 137 images OK

PASS

All 137 images OK

137 image(s) with good alt text

137 images 137 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 25 controls have issues

PASS

1 of 25 controls have issues

1 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

24 control(s) properly labeled

25 controls

24 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#:Rkqgr96:	text	Search	for/id
#email	email	Email (required)	for/id
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#ot-sub-group-id-IAB2V2_2	checkbox	Use limited data to select advertising	aria-label
#ot-sub-group-id-IAB2V2_11	checkbox	Use limited data to select content	aria-label
#ot-sub-group-id-IAB2V2_6	checkbox	Use profiles to select personalised content	aria-label
#ot-sub-group-id-IAB2V2_5	checkbox	Create profiles to personalise content	aria-label
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#ot-group-id-C0005	checkbox	Social Media & Embedded Content	for/id
#ot-group-id-C0004	checkbox	Targeting Cookies	for/id
#ot-sub-group-id-ISF2V2_2	checkbox	Actively scan device characteristics for identification	aria-label
#ot-sub-group-id-ISF2V2_1	checkbox	Use precise geolocation data	aria-label
#ot-group-id-IAB2V2_8	checkbox	Measure content performance	for/id
#ot-group-id-IAB2V2_4	checkbox	Use profiles to select personalised advertising	for/id
#ot-sub-group-id-IAB2V2_3	checkbox	Create profiles for personalised advertising	aria-label
#ot-group-id-IAB2V2_9	checkbox	Understand audiences through statistics or combinations of data from different sources	for/id
#ot-sub-group-id-IAB2V2_10	checkbox	Develop and improve services	aria-label
#ot-sub-group-id-IAB2V2_7	checkbox	Measure advertising performance	aria-label
#ot-group-id-IAB2V2_1	checkbox	Store and/or access information on a device	for/id
#vendor-search-handler	text	Vendor list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
#g-recaptcha-response-100000	textarea	(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

Form Input Types

2 input(s) using type=text where a specific type would help

PASS

2 input(s) using type=text where a specific type would help

Input "query" should use type="search" (currently type="text")

Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "vendor-search-handler" should use type="search" (currently type="text")

Field name "vendor-search-handler" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

25 form control(s) checked, no input-semantic issues

PASS

25 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

5 explicit tabindex attribute(s) checked, no anti-patterns

PASS

5 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Lighthouse Accessibility Audits

Score 97/100 — 2 failing, 29 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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy Notice `div.gezj8c0 > ul.gezj8c1 > li.gezj8c2 > a.gezj8c3`
Terms of Use `div.gezj8c0 > ul.gezj8c1 > li.gezj8c2 > a.gezj8c3`
Platform Status `div.gezj8c0 > ul.gezj8c1 > li.gezj8c2 > a.gezj8c3`
Careers `div.gezj8c0 > ul.gezj8c1 > li.gezj8c2 > a.gezj8c3`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookie Policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●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

●Heading elements appear in a sequentially-descending order

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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