Skip to content
https://cisa.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
66
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Breadcrumb navigation detected
Got: aria-label
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs aria-label navigation
Search
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Heading Hierarchy
28 headings
REVIEW
28 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 JOINT CYBERSECURITY ADVISORY WARNS OF IRANIAN-AFFILIATED CYBER ACTORS TARGETING US CRITICAL INFRASTRUCTURE
  • H3 PUBLIC SERVICE ANNOUNCEMENT WARNS AGAINST PHISHING ATTEMPTS TARGETING COMMERCIAL MESSAGING APPS
  • H3 CISA URGES ENDPOINT MANAGEMENT SYSTEMS HARDENING AFTER CYBERATTACK AGAINST US ORGANIZATION
  • H3 EMERGENCY DIRECTIVE TO ADDRESS VULNERABILITIES IN CISCO SYSTEMS
  • H3 Enhanced Vulnerability Management with OpenEoX
  • H3 CIRCIA Rulemaking Town Hall Meetings
  • H2 News Updates
  • H3 CISA Issues Updated RESURGE Malware Analysis Highlighting a Stealthy but Active Threat
  • H3 Immediate Action Required: CISA Issues Emergency Directive to Secure Cisco SD-WAN Systems
  • H3 The End is Just the Beginning of Better Security: Enhanced Vulnerability Management with OpenEoX
  • H3 CISA Announces New Town Halls to Engage with Stakeholders on Cyber Incident Reporting for Critical Infrastructure
  • H3 CISA’s 2025 Year in Review: Driving Security and Resilience Across Critical Infrastructure
  • H2 Latest Operational Information
  • H3 Siemens RUGGEDCOM CROSSBOW Secure Access Manager Primary
  • H3 Siemens TPM 2.0
  • H3 Hardy Barth Salia EV Charge Controller
  • H3 Siemens Analytics Toolkit
  • H3 Siemens SINEC NMS
  • H2 How can we help?
  • H3 Find Help Locally
  • H3 Industry
  • H3 Small and Medium Businesses
  • H3 Educational Institutions
  • H2 Additional CISA Resources
  • H3 CISA Resources & Tools
  • H3 CISA Events
  • H3 CISA Services Catalog
  • H3 CISA Training

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

B
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Lock ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 16 fail WCAG AA
REVIEW

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

4 pass 16 fail WCAG AA
h2 News Updates
1.44:1
#000000
on
#002B47
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Latest Operational Information
1.44:1
#000000
on
#002B47
needs 3.0:1 (large text)
24px · bottom of viewport
h3 JOINT CYBERSECURITY ADVISORY WARNS OF IR…
1.44:1
#000000
on
#002B47
needs 3.0:1 (large text)
19px · bottom of viewport
h3 PUBLIC SERVICE ANNOUNCEMENT WARNS AGAINS…
1.44:1
#000000
on
#002B47
needs 3.0:1 (large text)
19px · bottom of viewport
h3 CISA URGES ENDPOINT MANAGEMENT SYSTEMS H…
1.44:1
#000000
on
#002B47
needs 3.0:1 (large text)
19px · bottom of viewport
h3 EMERGENCY DIRECTIVE TO ADDRESS VULNERABI…
1.44:1
#000000
on
#002B47
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Enhanced Vulnerability Management with O…
1.44:1
#000000
on
#002B47
needs 3.0:1 (large text)
19px · bottom of viewport
h3 CIRCIA Rulemaking Town Hall Meetings
1.44:1
#000000
on
#002B47
needs 3.0:1 (large text)
19px · bottom of viewport
p An official website of the United States…
1.44:1
#000000
on
#002B47
needs 4.5:1 (normal text)
16px · top of page (header area)
p Here’s how you know
1.44:1
#000000
on
#002B47
needs 4.5:1 (normal text)
16px · top of page (header area)
span Here’s how you know
1.44:1
#000000
on
#002B47
needs 4.5:1 (normal text)
16px · above the fold
strong Official websites use .gov
1.44:1
#000000
on
#002B47
needs 3.0:1 (large text)
16px · above the fold
strong .gov
2.56:1
#000000
on
#005288
needs 3.0:1 (large text)
16px · above the fold
p website belongs to an official governmen…
2.56:1
#000000
on
#005288
needs 4.5:1 (normal text)
16px · above the fold
p ) or
2.86:1
#000000
on
#065C81
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
strong https://
1.30:1
#000000
on
#0B213C
needs 3.0:1 (large text)
16px · above the fold

1 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
h2 News Updates1.44:13.0:1
#000000
#002B47
Fail
h2 Latest Operational I…1.44:13.0:1
#000000
#002B47
Fail
h3 JOINT CYBERSECURITY …1.44:13.0:1
#000000
#002B47
Fail
h3 PUBLIC SERVICE ANNOU…1.44:13.0:1
#000000
#002B47
Fail
h3 CISA URGES ENDPOINT …1.44:13.0:1
#000000
#002B47
Fail
h3 EMERGENCY DIRECTIVE …1.44:13.0:1
#000000
#002B47
Fail
h3 Enhanced Vulnerabili…1.44:13.0:1
#000000
#002B47
Fail
h3 CIRCIA Rulemaking To…1.44:13.0:1
#000000
#002B47
Fail
title Home Page | CISA18.43:14.5:1
#000000
#F0F0F0
Pass
a Skip to main content7.88:14.5:1
#000000
#90A1AC
Pass
p An official website …1.44:14.5:1
#000000
#002B47
Fail
p Here’s how you kno…1.44:14.5:1
#000000
#002B47
Fail
span Here’s how you kno…1.44:14.5:1
#000000
#002B47
Fail
strong Official websites us…1.44:13.0:1
#000000
#002B47
Fail
strong .gov2.56:13.0:1
#000000
#005288
Fail
p website belongs to a…2.56:14.5:1
#000000
#005288
Fail
strong Secure .gov websites…21.00:13.0:1
#000000
#FFFFFF
Pass
strong lock21.00:13.0:1
#000000
#FFFFFF
Pass
p ) or2.86:14.5:1
#000000
#065C81
Fail
strong https://1.30:13.0:1
#000000
#0B213C
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
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary navigation" MAIN CONTENTINFO footer
A
Alt Text Quality
All 25 images OK
PASS
All 25 images OK
Info::
3 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
21 image(s) with good alt text
25 images 21 good alt text 1 decorative
IssueCount
too long3 image(s)
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#gsc-i-id1textsearcharia-label
#gsc-i-id2textsearcharia-label
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
●`<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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○`<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.
○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>`.
○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.
○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