Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 7 FIX

Link & Button Quality

Action

6 issue(s) across 71 links and 9 buttons

FIX

6 issue(s) across 71 links and 9 buttons

4 link(s) with no accessible text

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

Got: a#IntroductiontotheADA; a#ServiceAnimals; a#Parking; a#EffectiveCommunication

1 link(s) with generic text

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

Got: # ("Continue")

1 link(s) open in new tab without warning

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

Got: https://touchpoints.digital.gov

1 button(s) with no accessible text

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

Got: button.usa-nav__close (#101 on page)

65 link(s) with descriptive text

71 links

4 empty

1 generic text

1 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
#	Continue	generic text	Replace with descriptive text
Before: Continue Suggested: #
https://touchpoints.digital.gov	Touchpoints	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

73 links and buttons have descriptive text

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

a#IntroductiontotheADA; a#ServiceAnimals; a#Parking; a#EffectiveCommunication

Why this matters

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

Source: WCAG 2.1 SC 2.4.4

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

# ("Continue")

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://touchpoints.digital.gov

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.usa-nav__close (#101 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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-y1z2wz

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

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

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://ada.gov/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://ada.gov/manifest.json

Manifest contains invalid JSON.

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 ✗

A+

Landmark Structure

14 landmarks

PASS

14 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

29 headings

PASS

29 headings

Multiple H1 headings (3 found)

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

H3 Changes to the ADA Title II Rule on Web Content and Mobile App Accessibility
H1 The Americans with Disabilities Act (ADA) protects people with disabilities from discrimination.
H2 New on ADA.gov
H3 State and Local Governments: First Steps Toward Complying with the Americans with Disabilities Act Title...
H3 Webinar: Americans with Disabilities Act Title II Web & Mobile Application Accessibility Rule
H3 Help
H2 What's on ADA.gov
H3 Topics
H3 Resources
H3 Laws & Regulations
H2 Service Animals and the ADA
H3 Topics
H3 Resources
H3 Laws & Regulations
H2 Topics
H3 Introduction to the ADA
H3 Service Animals
H3 Parking
H3 Effective Communication
H2 How to Report a Disability Rights Violation
H3 Report using our online form.
H3 We review your report.
H3 We determine next steps and get back to you.
H2 Think you or someone you know has experienced a disability rights violation?
H2 Subscribe to our newsletter for ADA updates
H1 You are now leaving a Department of Justice website duplicate H1
H1 Give Us Feedback duplicate H1
H2 Thank you!
H2 Error

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

A+

Alt Text Quality

All 23 images OK

PASS

All 23 images OK

9 decorative image(s) correctly marked

14 image(s) with good alt text

23 images 14 good alt text 9 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 6 controls labeled

PASS

All 6 controls labeled

6 control(s) properly labeled

6 controls

6 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#query	search	Search ADA.gov	for/id
#question_44337_answer_03	text	Name Optional.	for/id
#question_44338_answer_04	email	Email Optional. If provided, we may reach out for additional information	for/id
#question_option_47858	radio	Yes	for/id
#question_option_47859	radio	No	for/id
#question_44336_answer_02	textarea	Additional feedback about this page	for/id

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 The Americans with D…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 You are now leaving …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Give Us Feedback	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 New on ADA.gov	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What's on ADA.gov	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Service Animals and …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Topics	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 How to Report a Disa…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Think you or someone…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Subscribe to our new…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Thank you!	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Error	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Changes to the ADA T…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Topics	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Laws & Regulations	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Topics	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Laws & Regulations	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Introduction to the …	21.00:1	3.0: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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 25 passed

PASS

100

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.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` 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 buttons have discernible text.

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○No element has a `[tabindex]` value greater than 0

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

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