Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 3 REVIEW 3 FIX

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.

Navigation UX

Action

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

7 navigation landmark(s) detected

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 7 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Link & Button Quality

Action

11 issue(s) across 421 links and 94 buttons

REVIEW

11 issue(s) across 421 links and 94 buttons

6 link(s) with generic text

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

Got: /priorities/rural-health-transformation-rht-program/overview ("Learn more"); /priorities/health-technology-ecosystem/overview ("Learn more"); /fraud ("Learn more"); /priorities/medicare-prescription-drug-affordability/overview/medicare-drug-p… ("Learn more"); /medicaid-chip/community-engagement-support/eligibility-made-easy ("Learn more"); /about-cms/web-policies-important-links/accessibility-nondiscrimination-disab… ("Learn more")

5 button(s) with no accessible text

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

Got: button#trigger-tabs-496753269; button#trigger-tabs-6005754; button#trigger-tabs-598929116; button#trigger-tabs-1900450577; button#trigger-tabs-715570034

415 link(s) with descriptive text

421 links

0 empty

6 generic text

0 new tab

5 empty buttons

Element	Text	Issue	Suggested Fix
/priorities/rural-health-transformation-…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Overview
/priorities/health-technology-ecosystem/…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Overview
/fraud	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Fraud
/priorities/medicare-prescription-drug-a…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Medicare Drug Price Negotiation Program
/medicaid-chip/community-engagement-supp…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Eligibility Made Easy
/about-cms/web-policies-important-links/…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Accessibility Nondiscrimination Disabilities Notice#1557
<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

504 links and buttons have descriptive text

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

/priorities/rural-health-transformation-rht-program/overview ("Learn more"); /priorities/health-technology-ecosystem/overview ("Learn more"); /fraud ("Learn more"); /priorities/medicare-prescription-drug-affordability/overview/medicare-drug-p… ("Learn more"); /medicaid-chip/community-engagement-support/eligibility-made-easy ("Learn more"); /about-cms/web-policies-important-links/accessibility-nondiscrimination-disab… ("Learn 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

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

button#trigger-tabs-496753269; button#trigger-tabs-6005754; button#trigger-tabs-598929116; button#trigger-tabs-1900450577; button#trigger-tabs-715570034

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

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title CMS.gov ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

A+

Landmark Structure

20 landmarks

PASS

20 landmarks

<main> landmark present

7 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

92 headings

PASS

92 headings

Single H1 present

H2 CMS Newsroom
H2 Search CMS.gov
H2 CMS.gov main menu
H2 Medicare
H3 Enrollment & renewal
H3 Coverage
H3 Regulations & guidance
H3 Coding & billing
H3 Payment
H3 Medicare-Medicaid coordination
H3 Appeals & grievances
H3 Quality
H3 Health & safety standards
H3 Employers & plan sponsors
H3 Innovation Center
H3 Audits & Compliance
H3 Forms & notices
H3 Health & drug plans
H3 Coordination of benefits & recovery
H3 Settlements
H2 Medicaid/CHIP
H3 What is Medicaid?
H3 Medicare-Medicaid Coordination
H3 Regulations & guidance
H3 Innovation Center
H3 Community engagement support
H2 Marketplace & Private Insurance
H3 About the Marketplace
H3 Private Health Insurance
H3 Regulations & guidance
H3 In-person assisters
H3 Agents & Brokers
H3 Health Plans & Issuers
H3 Employers & sponsors
H3 States
H3 Resources
H2 Initiatives
H3 Burden Reduction
H3 Crushing Fraud, Waste, & Abuse
H3 E-health
H3 Electronic Prior Authorization
H3 Flu
H3 Health Equity
H3 Health Technology Ecosystem
H3 Healthcare Advisory Committee
H3 Healthplan price transparency
H3 Hospital price transparency
H3 Innovation Center
H3 Lookup tools
H3 Make Hospital Food Healthier Pledge
H3 Marketplace Open Enrollment
H3 Maternal Health
H3 Medicare OE partner resources
H3 Medicare Open Enrollment
H3 Medicare Prescription Drug Affordability
H3 No Surprise Billing
H3 Nursing Home Careers
H3 Open Payments
H3 Opioids
H3 Rural Health Transformation (RHT) Program
H3 Your Patient Rights
H2 Training & Education
H3 Medicare Training
H3 Partner outreach resources
H3 Medicare Learning Network® (MLN)
H3 CMS Open Door Forums
H3 Look up topics
H3 Learn More
H3 Find your provider type
H1 Home - Centers for Medicare & Medicaid Services
H2 What are you looking for today?
H2 Rural Health Transformation Program
H3 Rural Health Transformation Program
H2 Health Technology Ecosystem
H3 Health Technology Ecosystem
H2 Crushing Fraud, Waste, & Abuse
H3 Crushing Fraud, Waste, & Abuse
H2 Medicare Drug Price Negotiation
H3 Medicare Drug Price Negotiation
H2 Innovation Center
H3 Innovation Center
H2 Top resources
H3 Medicare fee schedules
H3 Codes for claim reimbursement
H3 Marketplace partner resources
H3 Manuals, forms, & transmittals
H3 Medicare.gov
H3 InsureKidsNow.gov
H3 Healthcare.gov
H3 Medicaid.gov
H2 Get email updates
H2 Connect with CMS

A+

Alt Text Quality

All 6 images OK

PASS

All 6 images OK

6 image(s) with good alt text

6 images 6 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 4 controls have issues

PASS

1 of 4 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit" id="edit-submit--2">

3 control(s) properly labeled

4 controls

3 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#header-search-input	search	Search	for/id
#hero-search-input	search	Search	for/id
email	text	Enter your email address:	aria-label
#edit-submit--2	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

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /sites/default/files/css/css__W8GZS71Y_QESvlEdcqG6ej855Pyvcm9Wu-fljmo1o4.css?delta=2&language=en&theme=cms_evo&include=eJxVjWsOwjAMgy-0x5FQmpq1om2ipEXA6YEJhvgV67Nj8wUxd7ETMYvFLG091HI2aR0tTlz9hKus75ukQmnDH6zYqKKNA-Km1CKFgrmLZp6Z7NeTYDI7yDjNoQhfDsfgKs3z9fVHwXde6C6j-xrIX6tiWKMNpbLQ6MJStaB_jCZWqeQHJiWjzUiTf9M_soymI5TsCXHyu3fUvfwJXJRpAA

Print Stylesheet ✓ Print Optimized

Print stylesheet /sites/default/files/css/css__W8GZS71Y_QESvlEdcqG6ej855Pyvcm9Wu-fljmo1o4.css?delta=2&language=en&theme=cms_evo&include=eJxVjWsOwjAMgy-0x5FQmpq1om2ipEXA6YEJhvgV67Nj8wUxd7ETMYvFLG091HI2aR0tTlz9hKus75ukQmnDH6zYqKKNA-Km1CKFgrmLZp6Z7NeTYDI7yDjNoQhfDsfgKs3z9fVHwXde6C6j-xrIX6tiWKMNpbLQ6MJStaB_jCZWqeQHJiWjzUiTf9M_soymI5TsCXHyu3fUvfwJXJRpAA ✓Inline @media print Not detected ✗

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
h2 Search CMS.gov	19.45:1	3.0:1	#000000	#E7FBF0	Pass
h2 CMS.gov main menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Medicare	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Medicaid/CHIP	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Marketplace & Privat…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Initiatives	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Training & Education	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What are you looking…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Top resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Get email updates	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Connect with CMS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Enrollment & renewal	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Coverage	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Regulations & guidan…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Coding & billing	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Payment	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Medicare-Medicaid co…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Appeals & grievances	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Quality	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Health & safety stan…	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.

Lighthouse Accessibility Audits

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

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-496753269 `div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-496753269`
div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-6005754 `div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-6005754`
div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-598929116 `div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-598929116`
div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-1900450577 `div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-1900450577`
div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-715570034 `div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-715570034`

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
div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-496753269 `div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-496753269`
div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-6005754 `div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-6005754`
div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-598929116 `div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-598929116`
div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-1900450577 `div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-1900450577`
div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-715570034 `div.field__item > div.paragraph > div.ds-u-lg-display--none > button#trigger-tabs-715570034`

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.

○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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

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

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

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

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