Skip to content
https://www.usatoday.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #0098fe ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA
title USA TODAY - Breaking News and Latest New…
1.45:1
#000000
on
#1F2B33
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Follow the madness 🏀
1.64:1
#000000
on
#323232
needs 4.5:1 (normal text)
16px · top of page (header area)
a America's birthday 🎂
1.19:1
#000000
on
#191919
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Discover PLAY 🤩
1.27:1
#000000
on
#221E1B
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Check home prices 🏠
1.19:1
#000000
on
#1B1815
needs 4.5:1 (normal text)
16px · above the fold
a U.S.
1.29:1
#000000
on
#22201D
needs 4.5:1 (normal text)
16px · above the fold
a Politics
1.50:1
#000000
on
#2C2C2A
needs 4.5:1 (normal text)
16px · above the fold
a Sports
1.44:1
#000000
on
#282926
needs 4.5:1 (normal text)
16px · above the fold
a Entertainment
1.29:1
#000000
on
#20201D
needs 4.5:1 (normal text)
16px · above the fold
a Opinion
3.61:1
#000000
on
#576777
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Crossword
2.12:1
#000000
on
#434343
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
div ONLY AT USA TODAY:
1.11:1
#000000
on
#12100E
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Newsletters
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a For Subscribers
1.06:1
#000000
on
#080A09
needs 4.5:1 (normal text)
16px · mid-page
a Real Estate
1.10:1
#000000
on
#101010
needs 4.5:1 (normal text)
16px · mid-page
a From the Archives
1.08:1
#000000
on
#0D0D0C
needs 4.5:1 (normal text)
16px · mid-page
a USA TODAY PLAY
1.10:1
#000000
on
#0F1010
needs 4.5:1 (normal text)
16px · mid-page

6 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)
ElementRatioRequiredFGBGResult
title USA TODAY - Breaking…1.45:14.5:1
#000000
#1F2B33
Fail
a Follow the madness …1.64:14.5:1
#000000
#323232
Fail
a America's birthday …1.19:14.5:1
#000000
#191919
Fail
a Discover PLAY 🤩1.27:14.5:1
#000000
#221E1B
Fail
a Check home prices …1.19:14.5:1
#000000
#1B1815
Fail
a U.S.1.29:14.5:1
#000000
#22201D
Fail
a Politics1.50:14.5:1
#000000
#2C2C2A
Fail
a Sports1.44:14.5:1
#000000
#282926
Fail
a Entertainment1.29:14.5:1
#000000
#20201D
Fail
a Life10.94:14.5:1
#000000
#C1BAB3
Pass
a Money9.50:14.5:1
#000000
#B8ACA8
Pass
a Travel7.24:14.5:1
#000000
#9298A2
Pass
a Opinion3.61:14.5:1
#000000
#576777
Fail
a Crossword2.12:14.5:1
#000000
#434343
Fail
div ONLY AT USA TODAY:1.11:14.5:1
#000000
#12100E
Fail
a Newsletters1.00:14.5:1
#000000
#000000
Fail
a For Subscribers1.06:14.5:1
#000000
#080A09
Fail
a Real Estate1.10:14.5:1
#000000
#101010
Fail
a From the Archives1.08:14.5:1
#000000
#0D0D0C
Fail
a USA TODAY PLAY1.10:14.5:1
#000000
#0F1010
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.

C
Lighthouse Accessibility Audits
Action
Score 79/100 — 6 failing, 23 passed
REVIEW
79

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Close Special Offer body > div#gnt_mol_oy

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.

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
main.gnt_cw > div.dd-widget-wrapper > div.dd-widget-input-wrapper > button.dd-widget-input-send-button main.gnt_cw > div.dd-widget-wrapper > div.dd-widget-input-wrapper > button.dd-widget-input-send-button

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i
main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i main.gnt_cw > div.gnt_m > a.gnt_m_lm_a > img.gnt_m_lm_i

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.dd-widget-wrapper > div.dd-widget-input-wrapper > div.dd-widget-input-field > input.dd-widget-input-field-textarea div.dd-widget-wrapper > div.dd-widget-input-wrapper > div.dd-widget-input-field > input.dd-widget-input-field-textarea

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.

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
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Subscription Terms & Conditions footer.gnt_ft > div.gnt_ft_lw > div.gnt_ft_ls > a.gnt_ft_a
Terms of Service footer.gnt_ft > div.gnt_ft_lw > div.gnt_ft_ls > a.gnt_ft_a
Careers footer.gnt_ft > div.gnt_ft_lw > div.gnt_ft_ls > a.gnt_ft_a

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
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_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
●`[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
●`[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
●`<frame>` or `<iframe>` elements have a title
●`<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
●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
●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
○`<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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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
○`<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
○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.
A
Landmark Structure
23 landmarks
PASS
23 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Warning::
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
BANNER header NAV "Global navigation" MAIN ASIDE "advertisement" CONTENTINFO footer

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

A+
Alt Text Quality
All 40 images OK
PASS
All 40 images OK
Info::
40 decorative image(s) correctly marked
40 images 40 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input>
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
emailemailEmail addressaria-label
inputinput(none)none

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

<input>

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

A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found (404) | USA TODAY ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback