Skip to content
https://opm.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
2
PASS
7
INFO
0
Checks
13
7 PASS 2 REVIEW 4 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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 Present
✗ 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.

F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
5 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 ORA: The Future of Federal Retirement St…
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h1 Manage your Retirement Annuity Online
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h1 How OPM is Preparing for the Surge in Re…
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h2 Featured Topics
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Topics
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Topics
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Topics
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Topics
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Topics
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Topics
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Topics
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Topics
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Topics
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Topics
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Topics
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Our Vision
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Our Mission
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Salaries and Wages
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Schedule A Hiring Authority
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 FEGLI Handbook
1.08:1
#000000
on
#0B0D0F
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient

8 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 ORA: The Future of F…1.08:13.0:1
#000000
#0B0D0F
Fail
h1 Manage your Retireme…1.08:13.0:1
#000000
#0B0D0F
Fail
h1 How OPM is Preparing…1.08:13.0:1
#000000
#0B0D0F
Fail
h2 Featured Topics1.08:13.0:1
#000000
#0B0D0F
Fail
h2 Featured Topics1.08:13.0:1
#000000
#0B0D0F
Fail
h2 Featured Topics1.08:13.0:1
#000000
#0B0D0F
Fail
h2 Featured Topics1.08:13.0:1
#000000
#0B0D0F
Fail
h2 Featured Topics1.08:13.0:1
#000000
#0B0D0F
Fail
h2 Featured Topics1.08:13.0:1
#000000
#0B0D0F
Fail
h2 Featured Topics1.08:13.0:1
#000000
#0B0D0F
Fail
h2 Featured Topics1.08:13.0:1
#000000
#0B0D0F
Fail
h2 Featured Topics1.08:13.0:1
#000000
#0B0D0F
Fail
h2 Featured Topics1.08:13.0:1
#000000
#0B0D0F
Fail
h2 Featured Topics1.08:13.0:1
#000000
#0B0D0F
Fail
h2 Featured Topics1.08:13.0:1
#000000
#0B0D0F
Fail
h3 Our Vision1.08:13.0:1
#000000
#0B0D0F
Fail
h3 Our Mission1.08:13.0:1
#000000
#0B0D0F
Fail
h3 Salaries and Wages1.08:13.0:1
#000000
#0B0D0F
Fail
h3 Schedule A Hiring Au…1.08:13.0:1
#000000
#0B0D0F
Fail
h3 FEGLI Handbook1.08:13.0:1
#000000
#0B0D0F
Fail

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
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
2 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary navigation" MAIN CONTENTINFO footer

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
42 headings
PASS
42 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 Featured Topics
  • H3 Our Vision
  • H3 Our Mission
  • H2 Featured Topics
  • H3 Salaries and Wages
  • H3 Schedule A Hiring Authority
  • H2 Featured Topics
  • H3 FEGLI Handbook
  • H3 Frequently Asked Questions
  • H2 Featured Topics
  • H3 Services Online
  • H2 Featured Topics
  • H3 Suitability Executive Agent (SuitEA)
  • H2 Featured Topics
  • H3 Telework: Is Your Agency Ready?
  • H3 Federal Executive Institute
  • H2 Featured Topics
  • H3 Our Vision
  • H3 Our Mission
  • H2 Featured Topics
  • H3 Salaries and Wages
  • H3 Schedule A Hiring Authority
  • H2 Featured Topics
  • H3 FEGLI Handbook
  • H3 Frequently Asked Questions
  • H2 Featured Topics
  • H3 Services Online
  • H2 Featured Topics
  • H3 Suitability Executive Agent (SuitEA)
  • H2 Featured Topics
  • H3 Telework: Is Your Agency Ready?
  • H3 Federal Executive Institute
  • H1 ORA: The Future of Federal Retirement Starts Here
  • H1 Manage your Retirement Annuity Online duplicate H1
  • H1 How OPM is Preparing for the Surge in Retirements duplicate H1
  • H2 Job Seekers
  • H2 Federal Employees & Annuitants
  • H2 HR Professionals
  • H2 Recent News
  • H2 Frequently Asked Questions
  • H3 Trending Topics
  • H3 In this section

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 11 images OK
PASS
All 11 images OK
Info::
7 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
11 images 4 good alt text 7 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="button" name="GoSearch" id="GoSearch">
Info::
3 control(s) properly labeled
4 controls
3 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#basic-search-field-smallsearchSearch all of OPMfor/id
#SiteSearchStringtextSearch forfor/id
#TopFAQsSearchTexttextTop FAQs search termaria-label
#GoSearchbutton(none)none

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

<input type="button" name="GoSearch" id="GoSearch">

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
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
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+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /css/print.css
Print Stylesheet ✓ Print Optimized
Print stylesheet /css/print.css ✓Inline @media print Not detected ✗
A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 27 passed
PASS
93

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.

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.grid-container > div.grid-row > div.featured-audience > a div.grid-container > div.grid-row > div.featured-audience > a
div.grid-container > div.grid-row > div.featured-audience > a div.grid-container > div.grid-row > div.featured-audience > a
div.grid-container > div.grid-row > div.featured-audience > a div.grid-container > div.grid-row > div.featured-audience > a

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.

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#htmBody > a.usa-skipnav

These are opportunities to improve keyboard navigation in your application.

○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
●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
●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
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[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
○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.
○`[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.
○Elements with visible text labels have matching accessible names.
○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.

Send Feedback