Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

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 Present

✓ 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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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 ✗

Landmark Structure

1 landmarks

REVIEW

1 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found – Lawrence Berkeley National Laboratory ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

11 text elements analyzed, 8 fail WCAG AA

REVIEW

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

3 pass 8 fail WCAG AA

a Scientists Develop New Technology to Con…

1.21:1

#000000

#091B30

needs 4.5:1 (normal text)

16px · top of page (header area)

a AI for Science, Energy, and Security: Su…

1.76:1

#000000

#0F395D

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

p At Lawrence Berkeley National Laboratory…

1.37:1

#000000

#0B273E

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

p Berkeley Lab’s innovative research and…

1.05:1

#000000

#04080F

needs 4.5:1 (normal text)

16px · above the fold

a Three Berkeley Lab Researchers Named AAA…

1.06:1

#000000

#050A12

needs 4.5:1 (normal text)

16px · above the fold

a Solving a Mystery in Dark Matter Detecto…

1.49:1

#000000

#0E2C4D

needs 4.5:1 (normal text)

16px · above the fold

a Berkeley Lab Takes Major Step Toward Dou…

1.15:1

#000000

#091525

needs 4.5:1 (normal text)

16px · above the fold

p Notifications

1.11:1

#000000

#07111E

needs 4.5:1 (normal text)

16px · above the fold

2 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 (11)

Element	Ratio	Required	FG	BG	Result
h1 DESI Completes Plann…	20.08:1	3.0:1	#000000	#F9FAFA	Pass
title Home – Lawrence Be…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	18.82:1	4.5:1	#000000	#F0F3F3	Pass
a Scientists Develop N…	1.21:1	4.5:1	#000000	#091B30	Fail
a AI for Science, Ener…	1.76:1	4.5:1	#000000	#0F395D	Fail
p At Lawrence Berkeley…	1.37:1	4.5:1	#000000	#0B273E	Fail
p Berkeley Lab’s inn…	1.05:1	4.5:1	#000000	#04080F	Fail
a Three Berkeley Lab R…	1.06:1	4.5:1	#000000	#050A12	Fail
a Solving a Mystery in…	1.49:1	4.5:1	#000000	#0E2C4D	Fail
a Berkeley Lab Takes M…	1.15:1	4.5:1	#000000	#091525	Fail
p Notifications	1.11:1	4.5:1	#000000	#07111E	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+

Heading Hierarchy

6 headings

PASS

6 headings

Single H1 present

H1 DESI Completes Planned 3D Map of the Universe and Continues Exploring
H2 Scientists Develop New Technology to Continuously Monitor Geothermal Energy Operations
H2 AI for Science, Energy, and Security: Supporting DOE's Genesis Mission
H3 Three Berkeley Lab Researchers Named AAAS Fellows
H3 Solving a Mystery in Dark Matter Detectors Could Improve Quantum Computers
H3 Berkeley Lab Takes Major Step Toward Doudna with Delivery of Early Access System, Cech

A+

Alt Text Quality

All 10 images OK

PASS

All 10 images OK

1 image(s) with alt text over 125 characters

9 image(s) with good alt text

10 images 9 good alt text

Issue	Count
too long	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

6 links, 0 buttons — all OK

PASS

6 links, 0 buttons — all OK

3 link(s) open in new tab without warning

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

Got: https://newscenter.lbl.gov/2026/03/27/three-berkeley-lab-researchers-named-aa…; https://newscenter.lbl.gov/2026/03/17/solving-a-mystery-in-dark-matter-detect…; https://newscenter.lbl.gov/2026/03/17/berkeley-lab-takes-major-step-toward-do…

3 link(s) with descriptive text

6 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://newscenter.lbl.gov/2026/03/27/th…	Three Berkeley Lab Researchers…	new tab	Add '(opens in new tab)' to text
https://newscenter.lbl.gov/2026/03/17/so…	Solving a Mystery in Dark Matt…	new tab	Add '(opens in new tab)' to text
https://newscenter.lbl.gov/2026/03/17/be…	Berkeley Lab Takes Major Step …	new tab	Add '(opens in new tab)' to text

3 links and buttons have descriptive text

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

https://newscenter.lbl.gov/2026/03/27/three-berkeley-lab-researchers-named-aa…; https://newscenter.lbl.gov/2026/03/17/solving-a-mystery-in-dark-matter-detect…; https://newscenter.lbl.gov/2026/03/17/berkeley-lab-takes-major-step-toward-do…

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

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 20 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.

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
a.btn `a.btn`
a.btn `a.btn`

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ARTICLE `div.tags > ul > li > a`
COSMIC FRONTIERS `div.tags > ul > li > a`

These items highlight common accessibility best practices.

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

●`[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

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

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

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