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 1 REVIEW 6 FIX

404 Error Page

Action

HTTP 404, custom page

FIX

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

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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

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 ✗

Link & Button Quality

3 issue(s) across 127 links and 20 buttons

REVIEW

3 issue(s) across 127 links and 20 buttons

3 link(s) with generic text

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

Got: https://www.facebook.com/Healthcare.gov ("Continue"); https://twitter.com/HealthCareGov ("Continue"); https://www.youtube.com/HealthCareGov ("Continue")

10 link(s) open in new tab without warning

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

Got: https://www.hhs.gov/healthcare/index.html; https://www.cms.gov/marketplace/about/oversight; https://www.cms.gov/marketplace/in-person-assisters/information-partners; https://www.cms.gov/marketplace/agents-brokers/resources; https://www.cms.gov/about-cms/contact/newsroom; /health-and-dental-plan-datasets-for-researchers-and-issuers/; https://www.cms.gov/marketplace/states/state-marketplace-resources; /language-resource/; /contact-us/; https://localhelp.healthcare.gov/

114 link(s) with descriptive text

127 links

0 empty

3 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.hhs.gov/healthcare/index.htm…	About the Affordable Care Act	new tab	Add '(opens in new tab)' to text
https://www.cms.gov/marketplace/about/ov…	Regulatory and Policy Informat…	new tab	Add '(opens in new tab)' to text
https://www.cms.gov/marketplace/in-perso…	For Navigators, Assisters & Pa…	new tab	Add '(opens in new tab)' to text
https://www.cms.gov/marketplace/agents-b…	For Agents and Brokers	new tab	Add '(opens in new tab)' to text
https://www.cms.gov/about-cms/contact/ne…	For the Media	new tab	Add '(opens in new tab)' to text
/health-and-dental-plan-datasets-for-res…	For Researchers	new tab	Add '(opens in new tab)' to text
https://www.cms.gov/marketplace/states/s…	For States	new tab	Add '(opens in new tab)' to text
/language-resource/	Information in other languages	new tab	Add '(opens in new tab)' to text
/contact-us/	Questions? Call 1-800-318-2596	new tab	Add '(opens in new tab)' to text
https://localhelp.healthcare.gov/	Find Local Help	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Healthcare.gov	Continue	generic text	Replace with descriptive text
Before: Continue Suggested: Healthcare.Gov
https://twitter.com/HealthCareGov	Continue	generic text	Replace with descriptive text
Before: Continue Suggested: Healthcaregov
https://www.youtube.com/HealthCareGov	Continue	generic text	Replace with descriptive text
Before: Continue Suggested: Healthcaregov

134 links and buttons have descriptive text

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

https://www.facebook.com/Healthcare.gov ("Continue"); https://twitter.com/HealthCareGov ("Continue"); https://www.youtube.com/HealthCareGov ("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://www.hhs.gov/healthcare/index.html; https://www.cms.gov/marketplace/about/oversight; https://www.cms.gov/marketplace/in-person-assisters/information-partners; https://www.cms.gov/marketplace/agents-brokers/resources; https://www.cms.gov/about-cms/contact/newsroom; /health-and-dental-plan-datasets-for-researchers-and-issuers/; https://www.cms.gov/marketplace/states/state-marketplace-resources; /language-resource/; /contact-us/; https://localhelp.healthcare.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

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

3 <nav> landmark(s) found

2 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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 Hierarchy

13 headings

PASS

13 headings

Single H1 present

H2 Enroll in health insurance
H2 Make changes
H2 Save money
H2 How to...
H2 More details if you...
H2 Taxes
H1 Welcome to the Health Insurance Marketplace®
H2 Get important news & updates
H2 Resources
H2 Connect with us
H2 You are leaving HealthCare.gov.
H2 You are leaving HealthCare.gov.
H2 You are leaving HealthCare.gov.

A+

Alt Text Quality

All 5 images OK

PASS

All 5 images OK

5 decorative image(s) correctly marked

5 images 5 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#input-main-nav-search-mobile	input	Site Search	aria-label
#input-main-nav-search-desktop	input	Site Search	aria-label
#sign-up-email-field	text	Enter your email address	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 Welcome to the Healt…	18.50:1	3.0:1	#000000	#E8F2F9	Pass
h2 Enroll in health ins…	18.50:1	3.0:1	#000000	#E8F2F9	Pass
h2 Make changes	18.50:1	3.0:1	#000000	#E8F2F9	Pass
h2 Save money	18.50:1	3.0:1	#000000	#E8F2F9	Pass
h2 How to...	18.50:1	3.0:1	#000000	#E8F2F9	Pass
h2 More details if you.…	18.50:1	3.0:1	#000000	#E8F2F9	Pass
h2 Taxes	18.50:1	3.0:1	#000000	#E8F2F9	Pass
h2 Get important news &…	18.50:1	3.0:1	#000000	#E8F2F9	Pass
h2 Resources	18.50:1	3.0:1	#000000	#E8F2F9	Pass
h2 Connect with us	18.50:1	3.0:1	#000000	#E8F2F9	Pass
h2 You are leaving Heal…	18.50:1	3.0:1	#000000	#E8F2F9	Pass
h2 You are leaving Heal…	18.50:1	3.0:1	#000000	#E8F2F9	Pass
h2 You are leaving Heal…	18.50:1	3.0:1	#000000	#E8F2F9	Pass
title Welcome to the Healt…	18.76:1	4.5:1	#000000	#F2F2F2	Pass
a Skip to main content	18.76:1	4.5:1	#000000	#F2F2F2	Pass
p An official website …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Here's how you know	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Here's how you know	21.00:1	4.5:1	#000000	#FFFFFF	Pass
strong Official websites us…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
strong .gov	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, 32 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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

●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

●`<frame>` or `<iframe>` elements have a title

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

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

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

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

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