Skip to content
https://supremecourt.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
49
GRADE
F
FIX
6
REVIEW
6
PASS
1
INFO
0
Checks
13
1 PASS 6 REVIEW 6 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
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No contentinfo (footer) landmark
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 MAIN (missing!) CONTENTINFO (missing!)

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

B
Heading Hierarchy
6 headings
REVIEW
6 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 Quick Links
  • H4 Today at the Court - Tuesday, Apr 21, 2026
  • H3 Recent Decisions
  • H4 (empty)
  • H3 Did You Know...
  • H4 Cushing’s Finest Hour

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

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

C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="ctl00$txbhidden" id="ctl00_txbhidden">; <input type="text">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="ctl00$txtSearch" id="ctl00_txtSearch">
3 controls
0 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#ctl00_txtSearchtext(Search Site for...)placeholder only
#ctl00_txbhiddentext(none)none
inputtext(none)none

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

<input type="text" name="ctl00$txbhidden" id="ctl00_txbhidden">; <input type="text">

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

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="ctl00$txtSearch" id="ctl00_txtSearch">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA 2 pass AA only
title Home - Supreme Court of the United State…
1.53:1
#000000
on
#222F37
needs 4.5:1 (normal text)
16px · top of page (header area)
span Search term too short
1.53:1
#000000
on
#222F37
needs 4.5:1 (normal text)
16px · top of page (header area)
span Invalid text in search term. Try again
1.53:1
#000000
on
#222F37
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 Quick Links7.80:13.0:1
#9C2426
#FFFFFF
Pass
h3 Recent Decisions7.80:13.0:1
#9C2426
#FFFFFF
Pass
h3 Did You Know...7.80:13.0:1
#9C2426
#FFFFFF
Pass
title Home - Supreme Court…1.53:14.5:1
#000000
#222F37
Fail
a SEARCH TIPS7.52:14.5:1
#D9BE65
#222F37
Pass
span Search term too shor…1.53:14.5:1
#000000
#222F37
Fail
span Invalid text in sear…1.53:14.5:1
#000000
#222F37
Fail
a ADVANCED SEARCH7.52:14.5:1
#D9BE65
#222F37
Pass
a DOCKET SEARCH6.25:14.5:1
#D9BE65
#383B33
Pass
a Search20.03:14.5:1
#FFFFFF
#080808
Pass
span Toggle navigation9.55:14.5:1
#000000
#B8AF8C
Pass
a OPINIONS9.87:14.5:1
#000000
#B3B2AB
Pass
a Opinions of the Cour…9.15:14.5:1
#000000
#ABABAC
Pass
a Opinions Relating to…6.61:14.5:1
#000000
#B08B3D
Pass
a In-Chambers Opinions17.94:14.5:1
#000000
#FBEEAD
Pass
a U. S. Reports20.47:14.5:1
#000000
#FEFCF6
Pass
a Online Sources Cited…20.82:14.5:1
#000000
#FEFEFE
Pass
a Media Files Cited in…20.82:14.5:1
#000000
#FEFEFE
Pass
a Case Citation Finder20.92:14.5:1
#000000
#FEFFFC
Pass
a FILING & RULES20.67:14.5:1
#000000
#FDFEF5
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.

C
Lighthouse Accessibility Audits
Action
Score 76/100 — 5 failing, 18 passed
REVIEW
76

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.

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
Electronic Filing div.container > div.center-block > div.col-md-2 > a
Courtroom Seating div.container > div.center-block > div.col-md-2 > a
Fellows Program div.container > div.center-block > div.col-md-2 > a
Contact Us div.container > div.center-block > div.col-md-2 > a
Live Audio div.col-md-2 > a > div > div
oral argument div#ctl00_MainEditable_RadEditToday > ul > li > a
24 tbody > tr.rcRow > td > a
Calendar Info/Key div.col-xs-12 > div.col-sm-6 > span > a
District of Columbia v. R.W. (25-248) div.col-lg-7 > div#opinionsbyday > div.casenamerow > span#ctl00_MainEditable_rptRecentDecisions_ctl01_rptRecentDecisionDay_ctl00_lblRecentCaseName
Per Curiam div.col-lg-7 > div#opinionsbyday > div.casenamerow > i
Chevron USA Inc. v. Plaquemines Parish (24-813) div.col-lg-7 > div#opinionsbyday > div.casenamerow > span#ctl00_MainEditable_rptRecentDecisions_ctl02_rptRecentDecisionDay_ctl00_lblRecentCaseName
Chiles v. Salazar (24-539) div.col-lg-7 > div#opinionsbyday > div.casenamerow > span#ctl00_MainEditable_rptRecentDecisions_ctl03_rptRecentDecisionDay_ctl00_lblRecentCaseName
More Opinions... div.container > div.col-lg-7 > span > a#ctl00_MainEditable_hypMoreOpinions
Opinions of the Court div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink30
Opinions Relating to Orders div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink31
In-Chambers Opinions div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink32
U. S. Reports div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink35
Online Sources Cited in Opinions div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink37
Media Files Cited in Opinions div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink36
Case Citation Finder div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink34
Electronic Filing div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink44f
Rules and Guidance div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink3
Supreme Court Bar div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink2
Argument Transcripts div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink13
Argument Audio div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink14
Calendars and Lists div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink6
Courtroom Seating div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink8
Docket Search div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_hypdocket
Orders of the Court div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_hypOrdersOfCourt
Orders by Circuit div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink67
Granted/Noted Cases List div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink68
Journal div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink39
Original Jurisdiction Records & Briefs div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HypOrigCasef
Services for News Media div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperlinkServicesft
Press Releases div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink57
Media Advisories div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink58
Press Credentials div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink61
Speeches div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink59
A Reporter's Guide to Applications (PDF) div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink62
Chief Justice's Year-End Reports on the Federal Judiciary div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink60
Justices div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink4
Supreme Court at Work div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink10
Code of Conduct for Justices div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink1
History and Traditions div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink7
The Supreme Court Building div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink49
Building Regulations div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink50
Frequently Asked Questions div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink45
Hours & Directions div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_hypHoursDirection
Prohibited Items div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_hypProhibitedItems
Visitor Guidelines div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperGuidelines
Accessibility div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HypAccessibility
Maps & Guides div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HypMapsBrochures
Courtroom Lectures div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_hypLectures
Exhibitions div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink9
Group Visits div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HypSchool
Activities for Students & Families div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink11
Café & Building Amenities div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HypBuildingAmenities

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.t-chrome html.t-chrome

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-sm-6 > div.legend > div#ctl00_MainEditable_pnlLegend > a#legendOpinion div.col-sm-6 > div.legend > div#ctl00_MainEditable_pnlLegend > a#legendOpinion
div.col-sm-6 > div.legend > div#ctl00_MainEditable_pnlLegend > a#legendconfOpinion div.col-sm-6 > div.legend > div#ctl00_MainEditable_pnlLegend > a#legendconfOpinion
div.col-sm-6 > div.legend > div#ctl00_MainEditable_pnlLegend > a#legendConfArg div.col-sm-6 > div.legend > div#ctl00_MainEditable_pnlLegend > a#legendConfArg

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
<< tbody > tr > td > a#ctl00_MainEditable_Cal_FNP
< tbody > tr > td > a#ctl00_MainEditable_Cal_NP
> tbody > tr > td > a#ctl00_MainEditable_Cal_NN
<< tbody > tr > td > a#ctl00_MainEditable_Cal_FNN
FILING & RULES div.container > div.col-md-6 > div.col-sm-4 > a#ctl00_wucFooterNav_HyperLink69
Electronic Filing div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink44f
Rules and Guidance div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink3
Supreme Court Bar div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink2
Calendars and Lists div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink6
Courtroom Seating div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink8
Media Advisories div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink58
Press Credentials div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink61
ABOUT div.container > div.col-md-6 > div.col-sm-4 > a#ctl00_wucFooterNav_hypAboutCourt
Justices div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_Hyperlink4
Prohibited Items div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_hypProhibitedItems
Visitor Guidelines div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperGuidelines
Exhibitions div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HyperLink9
Group Visits div.col-sm-4 > ul.footernavlist > li > a#ctl00_wucFooterNav_HypSchool

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.t-chrome html.t-chrome

These items highlight common accessibility best practices.

○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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●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.
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●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.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`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
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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 a valid value for its `[lang]` attribute
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<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>`.
○Uses ARIA roles only on compatible elements
○Elements with visible text labels have matching accessible names.
A
Alt Text Quality
1 of 7 images have issues
PASS
1 of 7 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
7 images 5 good alt text 1 decorative 1 missing
IssueCount
missing1 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

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

Send Feedback