Skip to content
https://cert.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
F
Heading Hierarchy
Action
41 headings, 8 skip(s)
FIX
41 headings, 8 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 CERT Division
  • H2 Leadership
  • H4 Greg Touhill skipped
  • H4 William R. Wilson
  • H4 Chris Inacio
  • H2 What We Do
  • H4 Autonomy Security and Resilience skipped
  • H4 Cybersecurity Center Development
  • H4 Cybersecurity Engineering
  • H4 Cyber Workforce Development
  • H4 Enterprise Risk and Resilience Management
  • H4 Insider Threat
  • H4 Reverse Engineering for Malware Analysis
  • H4 Situational Awareness
  • H4 Secure Development
  • H4 System and Platform Evaluation
  • H4 Security Vulnerabilities
  • H2 Careers in the CERT Division
  • H4 Associate Cybersecurity Operations Researcher skipped
  • H4 Cybersecurity Operations Researcher
  • H4 AI Security Researcher
  • H4 Assistant AI Security Researcher
  • H4 Technical Manager - Cyber Risk Management
  • H4 Senior Reverse Engineer Researcher
  • H4 Associate AI Security Researcher
  • H4 Senior AI Security Researcher
  • H4 Reverse Engineer Researcher
  • H2 Recently Published Vulnerabilities
  • H4 VU#518910: Ollama GGUF Quantization Remote Memory Leak skipped
  • H6 April 22, 2026 skipped
  • H4 VU#890999: Radware Alteon has a reflected XSS vulnerability that can execute JavaScript in the host browser
  • H6 April 21, 2026 skipped
  • H4 VU#414811: Terrarium contains a vulnerability that allows arbitrary code execution
  • H6 April 21, 2026 skipped
  • H2 Case Studies
  • H4 Cyber Lightning Case Study skipped
  • H4 SEI Hosts Crisis Simulation Exercise for Cyber Intelligence Research Consortium
  • H4 USPS Case Study
  • H2 History
  • H2 Former Director Richard Pethia
  • H2 Related Links

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ 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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV 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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

C
Form Accessibility
Action
3 of 6 controls have issues
REVIEW
3 of 6 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="radio" name="88e87e53-7c22-4a3d-a3f9-5217c6775d76" id="carousel-0-88e87e53-7c22-4a3d-a3f9-5217c6775d76">; <input type="radio" name="88e87e53-7c22-4a3d-a3f9-5217c6775d76" id="carousel-1-88e87e53-7c22-4a3d-a3f9-5217c6775d76">; <input type="radio" name="88e87e53-7c22-4a3d-a3f9-5217c6775d76" id="carousel-2-88e87e53-7c22-4a3d-a3f9-5217c6775d76">
Info::
3 control(s) properly labeled
6 controls
3 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#footer-dropdown-1checkboxSEIfor/id
#footer-dropdown-2checkboxHelpful linksfor/id
#footer-dropdown-3checkboxConnectfor/id
#carousel-0-88e87e53-7c22-4a3d-a3f9-5217c6775d76radio(none)none
#carousel-1-88e87e53-7c22-4a3d-a3f9-5217c6775d76radio(none)none
#carousel-2-88e87e53-7c22-4a3d-a3f9-5217c6775d76radio(none)none

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

<input type="radio" name="88e87e53-7c22-4a3d-a3f9-5217c6775d76" id="carousel-0-88e87e53-7c22-4a3d-a3f9-5217c6775d76">; <input type="radio" name="88e87e53-7c22-4a3d-a3f9-5217c6775d76" id="carousel-1-88e87e53-7c22-4a3d-a3f9-5217c6775d76">; <input type="radio" name="88e87e53-7c22-4a3d-a3f9-5217c6775d76" id="carousel-2-88e87e53-7c22-4a3d-a3f9-5217c6775d76">

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

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

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

10 pass 10 fail WCAG AA
h1 CERT Division
2.09:1
#000000
on
#462F93
needs 3.0:1 (large text)
32px · mid-page · over background image/gradient
title CERT
3.48:1
#000000
on
#C41230
needs 4.5:1 (normal text)
16px · top of page (header area)
span About
1.12:1
#000000
on
#1D082A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Research and Development
1.72:1
#000000
on
#47285A
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Publications and Media
2.41:1
#000000
on
#6C3672
needs 4.5:1 (normal text)
16px · above the fold
span Education
2.42:1
#000000
on
#7C2B6D
needs 4.5:1 (normal text)
16px · above the fold
span Careers
1.50:1
#000000
on
#45135D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Search
1.63:1
#000000
on
#421181
needs 4.5:1 (normal text)
16px · above the fold
span Mobile Menu
1.61:1
#000000
on
#510471
needs 4.5:1 (normal text)
16px · above the fold
a Home
3.20:1
#000000
on
#6B49AF
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

4 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 CERT Division2.09:13.0:1
#000000
#462F93
Fail
h2 Leadership21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What We Do21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Careers in the CERT …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Recently Published V…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Case Studies21.00:13.0:1
#000000
#FFFFFF
Pass
h2 History21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Former Director Rich…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Related Links21.00:13.0:1
#000000
#FFFFFF
Pass
title CERT3.48:14.5:1
#000000
#C41230
Fail
span Carnegie Mellon Univ…10.02:14.5:1
#000000
#E7A0AC
Pass
span Home19.09:14.5:1
#000000
#F4F4F4
Pass
span About1.12:14.5:1
#000000
#1D082A
Fail
span Research and Develop…1.72:14.5:1
#000000
#47285A
Fail
span Publications and Med…2.41:14.5:1
#000000
#6C3672
Fail
span Education2.42:14.5:1
#000000
#7C2B6D
Fail
span Careers1.50:14.5:1
#000000
#45135D
Fail
span Search1.63:14.5:1
#000000
#421181
Fail
span Mobile Menu1.61:14.5:1
#000000
#510471
Fail
a Home3.20:14.5:1
#000000
#6B49AF
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+
Alt Text Quality
All 9 images OK
PASS
All 9 images OK
Info::
9 image(s) with good alt text
9 images 9 good alt text
All images have appropriate alt text.
A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 22 passed
PASS
94

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

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Greg Touhill div.grid > div.flex > a > h4.text-2xl
Autonomy Security and Resilience div.max-container > div.grid > div.col-span-1 > h4
Associate Cybersecurity Operations Researcher div.carousel-item > div.bg-white > a > h4.text-xl
VU#518910: Ollama GGUF Quantization Remote Memory Leak div.flex > div > div.pb-6 > h4
APRIL 22, 2026 div.flex > div > div.pb-6 > h6
APRIL 21, 2026 div.flex > div > div.pb-6 > h6
APRIL 21, 2026 div.flex > div > div.pb-6 > h6
Cyber Lightning Case Study div.max-container > div.grid > div.col-span-1 > h4

These are opportunities to improve keyboard navigation in your application.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Carnegie Mellon University div.flex > div.flex > p > a
Richard Pethia div.grid > div.flex > p > a

These are opportunities to improve the legibility of your content.

○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-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]`s are contained by their required parent element
●`[role]` values are valid
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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 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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○ARIA attributes are used as specified for the element's role
○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 use only permitted ARIA attributes
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○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