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 2 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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 Missing

✓ PNG Icons Present

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

Heading Hierarchy

21 headings

REVIEW

21 headings

No H1 heading found

Every page should have one H1 that describes the page content.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H2 Header Navigation
H2 In FY25, the EEOC Delivered Record-Breaking Recoveries for America’s Workers
H2 EEOC SECURES LARGEST COVID-19 VACCINATION-RELATED SETTLEMENT FOR WORKERS
H2 Chair Lucas Calls on Fortune 500 Executives to Comply with Title VII
H2 DEI-Related Discrimination: What To Do If You Experience It
H2 REPORT ANTI-AMERICAN EMPLOYMENT BIAS
H2 Newsroom
H2 What You Should Know
H2 Connect with us
H2 The 60th Anniversary of the Civil Rights Act
H2 DEI-Related Discrimination
H2 Tribal Programs
H2 (empty)
H3 Employees & Applicants
H3 Employers / Small Business
H3 Federal Agencies
H3 About EEOC
H2 U.S. Equal Employment Opportunity Commission
H3 EEOC Headquarters
H3 Questions?
H4 Connect With Us

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

Link & Button Quality

Action

9 issue(s) across 200 links and 16 buttons

REVIEW

9 issue(s) across 200 links and 16 buttons

7 link(s) with generic text

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

Got: https://www.eeoc.gov/newsroom/eeoc-highlights-record-breaking-results-agency-… ("Learn More"); https://www.eeoc.gov/newsroom/eeoc-reaches-15-million-conciliation-agreement-… ("Learn More"); https://www.eeoc.gov/what-do-if-you-experience-discrimination-related-dei-work ("Learn More"); https://www.eeoc.gov/discrimination-against-american-workers-against-law ("Learn More"); /history/60th-anniversary-title-vii-civil-rights-act-1964 ("Learn More"); https://www.eeoc.gov/sites/default/files/2025-03/One_Pagers_2025-2_%28002%29_… ("Learn More"); /tribal-programs ("Learn More")

1 link(s) open in new tab without warning

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

Got: /rss/newsroom

2 button(s) with no accessible text

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

Got: button.usa-button (#86 on page); button.usa-nav__close (#107 on page)

192 link(s) with descriptive text

200 links

0 empty

7 generic text

1 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://www.eeoc.gov/newsroom/eeoc-highl…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Eeoc Highlights Record Breaking Results Agency Reports
https://www.eeoc.gov/newsroom/eeoc-reach…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Eeoc Reaches 15 Million Conciliation Agreement Resolve Discrimination Claims Related Covid
https://www.eeoc.gov/what-do-if-you-expe…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: What Do If You Experience Discrimination Related Dei Work
https://www.eeoc.gov/discrimination-agai…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Discrimination Against American Workers Against Law
/rss/newsroom	Feed	new tab	Add '(opens in new tab)' to text
/history/60th-anniversary-title-vii-civi…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: 60th Anniversary Title Vii Civil Rights Act 1964
https://www.eeoc.gov/sites/default/files…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: One Pagers 2025 2 %28002%29 508.Pdf
/tribal-programs	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Tribal Programs
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

206 links and buttons have descriptive text

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

https://www.eeoc.gov/newsroom/eeoc-highlights-record-breaking-results-agency-… ("Learn More"); https://www.eeoc.gov/newsroom/eeoc-reaches-15-million-conciliation-agreement-… ("Learn More"); https://www.eeoc.gov/what-do-if-you-experience-discrimination-related-dei-work ("Learn More"); https://www.eeoc.gov/discrimination-against-american-workers-against-law ("Learn More"); /history/60th-anniversary-title-vii-civil-rights-act-1964 ("Learn More"); https://www.eeoc.gov/sites/default/files/2025-03/One_Pagers_2025-2_%28002%29_… ("Learn More"); /tribal-programs ("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

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

/rss/newsroom

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-button (#86 on page); button.usa-nav__close (#107 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

A+

Landmark Structure

11 landmarks

PASS

11 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Alt Text Quality

All 34 images OK

PASS

All 34 images OK

6 decorative image(s) correctly marked

28 image(s) with good alt text

34 images 28 good alt text 6 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#edit-search-keywords	text	Search the site	aria-label
#edit-submit-global-search	submit	Submit Search	aria-label

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Lock ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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 Header Navigation	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 In FY25, the EEOC De…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 EEOC SECURES LARGEST…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Chair Lucas Calls on…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 DEI-Related Discrimi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 REPORT ANTI-AMERICAN…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Newsroom	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What You Should Know	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Connect with us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The 60th Anniversary…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 DEI-Related Discrimi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Tribal Programs	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 U.S. Equal Employmen…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Employees & Applican…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Employers / Small Bu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Federal Agencies	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 About EEOC	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 EEOC Headquarters	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Questions?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Home \| U.S. Equal Em…	18.43:1	4.5:1	#000000	#F0F0F0	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 96/100 — 2 failing, 28 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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to main content `body.path-frontpage > a.visually-hidden`
Here’s how you know `div.usa-accordion > header.usa-banner__header > div.usa-banner__inner > button.usa-accordion__button`
U.S. Equal Employment Opportunity Commission `div.usa-navbar > div.region > div#logo > a`

These are opportunities to improve keyboard navigation in your application.

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
U.S. Equal Employment Opportunity Commission `div.usa-navbar > div.region > div#logo > a`

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

●`[accesskey]` values are unique

●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

●All heading elements contain content.

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

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

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

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