Skip to content
https://mozdev.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
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::
1 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 1 <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
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 404: Page Not Found Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA
h2 Firefox browsers
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
24px · above the fold
h2 Mozilla VPN
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
24px · above the fold
h2 Mozilla Monitor
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
24px · above the fold
h2 Firefox Relay
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
24px · mid-page
h2 MDN Plus
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
24px · mid-page
h2 Thunderbird
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
24px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Welcome to Mozilla21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Help us improve your…8.23:13.0:1
#000000
#A2A2A2
Pass
h2 Firefox browsers1.16:13.0:1
#000000
#161616
Fail
h2 Mozilla VPN1.16:13.0:1
#000000
#161616
Fail
h2 Mozilla Monitor1.16:13.0:1
#000000
#161616
Fail
h2 Firefox Relay1.16:13.0:1
#000000
#161616
Fail
h2 MDN Plus1.16:13.0:1
#000000
#161616
Fail
h2 Thunderbird1.16:13.0:1
#000000
#161616
Fail
h2 Solo21.00:13.0:1
#000000
#FFFFFF
Pass
h2 0DIN21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Tabstack21.00:13.0:1
#000000
#FFFFFF
Pass
h2 About Mozilla21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The Mozilla Manifest…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get Involved21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Blog21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Mozilla Foundation21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Mozilla.ai21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Mozilla Ventures21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Mozilla Advertising21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Mozilla Builders21.00:13.0:1
#000000
#FFFFFF
Pass

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
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 "Primary" 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+
Heading Hierarchy
44 headings
PASS
44 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Help us improve your Mozilla experience
  • H2 Firefox browsers
  • H2 Mozilla VPN
  • H2 Mozilla Monitor
  • H2 Firefox Relay
  • H2 MDN Plus
  • H2 Thunderbird
  • H2 Solo
  • H2 0DIN
  • H2 Tabstack
  • H2 About Mozilla
  • H2 The Mozilla Manifesto
  • H2 Get Involved
  • H2 Blog
  • H2 Mozilla Foundation
  • H2 Mozilla.ai
  • H2 Mozilla Ventures
  • H2 Mozilla Advertising
  • H2 Mozilla Builders
  • H2 Mozilla New Products
  • H1 Welcome to Mozilla
  • H2 Love the internet again
  • H2 Donate to Mozilla Foundation
  • H2 Join the movement: AI for the people
  • H3 Mozilla Data Collective
  • H3 Own What You Build
  • H3 Choice First Stack
  • H3 Mozilla Ventures
  • H3 A Double Bottom Line for Tech
  • H3 Agent Platform
  • H3 You, AI and the internet — what’s really going on?
  • H2 State of Mozilla
  • H3 2025
  • H2 Explore issues shaping the future of the internet
  • H3 The Validation Machines
  • H3 Nothing Personal
  • H3 Get Firefox news
  • H3 Thanks!
  • H2 (empty)
  • H2 Company
  • H2 Support
  • H2 Developers
  • H2 Follow @Mozilla
  • H2 Follow @Firefox

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+
Alt Text Quality
All 23 images OK
PASS
All 23 images OK
Info::
18 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
23 images 5 good alt text 18 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 6 controls labeled
PASS
All 6 controls labeled
Info::
6 control(s) properly labeled
6 controls
6 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#id_newsletters_0checkboxnone
#id_emailemailYour email address:for/id
#id_countryselectSelect country or region:for/id
#id_langselectSelect language:for/id
#privacycheckboxnone
#page-language-selectselectLanguagefor/id
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 27 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
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.
Select elements have associated label elements.
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
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.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
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
`<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
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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.
`<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