Skip to content
https://llnl.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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
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
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
Heading Hierarchy
28 headings, 2 skip(s)
REVIEW
28 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (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.
  • H2 Primary Menu
  • H2 Mobile Menu
  • H5 Site Menu skipped
  • H5 LLNL Menu
  • H1 LAWRENCE LIVERMORE NATIONAL LABORATORY
  • H2 Science and Technology on a Mission
  • H2 Our Mission-Driven Work
  • H2 Our Latest News
  • H2 Our Organizations
  • H3 Computing
  • H3 Global Security
  • H3 Operations and Business
  • H3 Strategic Deterrence
  • H3 Engineering
  • H3 National Ignition Facility and Photon Science
  • H3 Physical and Life Sciences
  • H2 Our World-Class Facilities
  • H2 Our Culture and Community
  • H2 Discover Your Next Career Opportunity
  • H4 LLNL.GOV skipped
  • H4 ORGANIZATIONS
  • H4 RESOURCES
  • H4 STAY CONNECTED
  • H4 STAY CONNECTED
  • H4 LLNL.GOV
  • H4 ORGANIZATIONS
  • H4 RESOURCES
  • H4 STAY CONNECTED

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

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, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA
a Our Science and Technology
2.06:1
#000000
on
#413F53
needs 4.5:1 (normal text)
16px · above the fold
span Open submenu
1.36:1
#000000
on
#2D202E
needs 4.5:1 (normal text)
16px · above the fold
a Our Science and Technology
1.16:1
#000000
on
#15132A
needs 4.5:1 (normal text)
16px · above the fold
a Advanced Materials and Manufacturing
1.13:1
#000000
on
#06112F
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 LAWRENCE LIVERMORE N…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Primary Menu21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Mobile Menu21.00:13.0:1
#000000
#FFFFFF
Pass
h2 and21.00:13.0:1
#000000
#FFFFFF
Pass
h2 on a21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Work21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our Latest News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our Organizations21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our World-Class Faci…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our Culture and Comm…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Discover Your Next21.00:13.0:1
#000000
#FFFFFF
Pass
title Lawrence Livermore N…18.43:14.5:1
#000000
#F0F0F0
Pass
span Menu18.43:14.5:1
#000000
#F0F0F0
Pass
a Our Purpose8.34:14.5:1
#000000
#91A3CF
Pass
span Open submenu18.10:14.5:1
#000000
#EEEEEE
Pass
a Our Science and Tech…2.06:14.5:1
#000000
#413F53
Fail
span Open submenu1.36:14.5:1
#000000
#2D202E
Fail
a Our Science and Tech…1.16:14.5:1
#000000
#15132A
Fail
a Advanced Materials a…1.13:14.5:1
#000000
#06112F
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
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "block-primary-menu-menu" MAIN CONTENTINFO footer

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

A
Alt Text Quality
All 26 images OK
PASS
All 26 images OK
Info::
7 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
17 image(s) with good alt text
26 images 17 good alt text 2 decorative
IssueCount
too long7 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
#edit-searchterm--20textSearcharia-label
#edit-searchterm--21textSearcharia-label
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /sites/www/files/css/css_hm9oz8jH2G52fOxPnijLrDwUBS9GyPLTDeLdGk47IXo.css?delta=1&language=en&theme=sienna&include=eJyFUtFu2zAM_CEtGgoM2N8QlM3YbCTREKk4-fvSTbNiq7A-GTqdqbvjoSoZcH2lyaTFSfWUREyt4QbdOLMxacCvtAmbdKUMqZtJBaObDXlSjaqtPUGlXWHDhUa8M8KZb6Q-qGxDAqH1RjMUmhkhZZkuQx4vMOFm7KIw81KLPw9DpqhRO-Zhftc1NLpSE0hYq1NXwpnrMuZJIbi-jK64-HBAs8ae1iHs7CFXsWEShRZ0zR08i9G9Z0DqvqBI4jwccWQIv37-fkQ6Ylxf_vP7PqFn6ItrqEMJd-nWk9vlmUTDJI3i3PqG-YSvePsL8GVlWYLXI3O9PNGPY8i5ZvjoCHhJ4lGSB6qEbVrj49M5vO89CpVEs--uFQ-UWtiw4eJ1XfU5-xM59br1lFlXmkMj3aQqXwmOeOM_58_if89shJdNuNq3VLW7-1yCMtWK8dg7tR_7vj-RrvusQe9exRITKoWd0uEO_uiJX5A3nO15Yw
Print Stylesheet ✓ Print Optimized
Print stylesheet /sites/www/files/css/css_hm9oz8jH2G52fOxPnijLrDwUBS9GyPLTDeLdGk47IXo.css?delta=1&language=en&theme=sienna&include=eJyFUtFu2zAM_CEtGgoM2N8QlM3YbCTREKk4-fvSTbNiq7A-GTqdqbvjoSoZcH2lyaTFSfWUREyt4QbdOLMxacCvtAmbdKUMqZtJBaObDXlSjaqtPUGlXWHDhUa8M8KZb6Q-qGxDAqH1RjMUmhkhZZkuQx4vMOFm7KIw81KLPw9DpqhRO-Zhftc1NLpSE0hYq1NXwpnrMuZJIbi-jK64-HBAs8ae1iHs7CFXsWEShRZ0zR08i9G9Z0DqvqBI4jwccWQIv37-fkQ6Ylxf_vP7PqFn6ItrqEMJd-nWk9vlmUTDJI3i3PqG-YSvePsL8GVlWYLXI3O9PNGPY8i5ZvjoCHhJ4lGSB6qEbVrj49M5vO89CpVEs--uFQ-UWtiw4eJ1XfU5-xM59br1lFlXmkMj3aQqXwmOeOM_58_if89shJdNuNq3VLW7-1yCMtWK8dg7tR_7vj-RrvusQe9exRITKoWd0uEO_uiJX5A3nO15Yw ✓Inline @media print Not detected ✗
A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 27 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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
LLNL.GOV Our Purpose Our Science and Technology Join Our Team Partner with Us N… div.dialog-off-canvas-main-canvas > footer.footer > div.container > div#footer-accordion

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
STAY CONNECTED div.container > div#footer-stay-connected > div.footer-social-media > h4

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]`s are contained by their required parent element
●`[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
●`<frame>` or `<iframe>` elements have a title
●`<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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[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 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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○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