Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 3 REVIEW 3 FIX

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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

Action

4 landmarks

REVIEW

4 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Mozilla ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 14 fail WCAG AA

REVIEW

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

6 pass 14 fail WCAG AA

title MDN Web Docs

1.19:1

#000000

#18191B

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.24:1

#000000

#1C1D1F

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to search

1.35:1

#000000

#212426

needs 4.5:1 (normal text)

16px · top of page (header area)

span HTML

1.35:1

#000000

#212426

needs 4.5:1 (normal text)

16px · top of page (header area)

a HTML: Markup language

1.35:1

#000000

#212426

needs 4.5:1 (normal text)

16px · above the fold

dt HTML reference

1.35:1

#000000

#212426

needs 4.5:1 (normal text)

16px · above the fold

a Elements

1.35:1

#000000

#212426

needs 4.5:1 (normal text)

16px · above the fold

a Global attributes

1.35:1

#000000

#212426

needs 4.5:1 (normal text)

16px · above the fold

a Attributes

1.35:1

#000000

#212426

needs 4.5:1 (normal text)

16px · above the fold

a See all…

1.35:1

#000000

#212426

needs 4.5:1 (normal text)

16px · above the fold

dt HTML guides

1.35:1

#000000

#212426

needs 4.5:1 (normal text)

16px · above the fold

a Responsive images

1.35:1

#000000

#212426

needs 4.5:1 (normal text)

16px · above the fold

a HTML cheatsheet

1.35:1

#000000

#212426

needs 4.5:1 (normal text)

16px · above the fold

a Date & time formats

1.35:1

#000000

#212426

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Resources for Develo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 by Developers	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Featured articles	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Latest news	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Recent contributions	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Contributor Spotligh…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title MDN Web Docs	1.19:1	4.5:1	#000000	#18191B	Fail
a Skip to main content	1.24:1	4.5:1	#000000	#1C1D1F	Fail
a Skip to search	1.35:1	4.5:1	#000000	#212426	Fail
span HTML	1.35:1	4.5:1	#000000	#212426	Fail
a HTML: Markup languag…	1.35:1	4.5:1	#000000	#212426	Fail
dt HTML reference	1.35:1	4.5:1	#000000	#212426	Fail
a Elements	1.35:1	4.5:1	#000000	#212426	Fail
a Global attributes	1.35:1	4.5:1	#000000	#212426	Fail
a Attributes	1.35:1	4.5:1	#000000	#212426	Fail
a See all…	1.35:1	4.5:1	#000000	#212426	Fail
dt HTML guides	1.35:1	4.5:1	#000000	#212426	Fail
a Responsive images	1.35:1	4.5:1	#000000	#212426	Fail
a HTML cheatsheet	1.35:1	4.5:1	#000000	#212426	Fail
a Date & time formats	1.35:1	4.5:1	#000000	#212426	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

13 headings

PASS

13 headings

Single H1 present

H1 Resources for Developers, by Developers
H2 Featured articles
H3 Celebrating 20 years of MDN
H3 CSS Custom Highlight API
H3 Server timing
H3 JavaScript resource management
H2 Latest news
H3 Launching MDN's new front end
H3 Image formats: Pixel data from encoders to decoders
H3 Image formats: Color models for humans and devices
H3 Default styles for h1 elements are changing
H2 Recent contributions
H2 Contributor Spotlight

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

162 links, 9 buttons — all OK

PASS

162 links, 9 buttons — all OK

10 link(s) open in new tab without warning

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

Got: https://github.com/mdn/; https://bsky.app/profile/developer.mozilla.org; https://x.com/mozdevnet; https://mastodon.social/@mdn; /en-US/blog/rss.xml; https://www.mozilla.org/en-US/careers/listings/; https://support.mozilla.org/products/mdn-plus; /discord; https://github.com/mdn; https://hacks.mozilla.org/

152 link(s) with descriptive text

162 links

0 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://github.com/mdn/	MDN on GitHub	new tab	Add '(opens in new tab)' to text
https://bsky.app/profile/developer.mozil…	MDN on Bluesky	new tab	Add '(opens in new tab)' to text
https://x.com/mozdevnet	MDN on X	new tab	Add '(opens in new tab)' to text
https://mastodon.social/@mdn	MDN on Mastodon	new tab	Add '(opens in new tab)' to text
/en-US/blog/rss.xml	MDN blog RSS feed	new tab	Add '(opens in new tab)' to text
https://www.mozilla.org/en-US/careers/li…	Mozilla careers	new tab	Add '(opens in new tab)' to text
https://support.mozilla.org/products/mdn…	Product help	new tab	Add '(opens in new tab)' to text
/discord	MDN Discord	new tab	Add '(opens in new tab)' to text
https://github.com/mdn	MDN on GitHub	new tab	Add '(opens in new tab)' to text
https://hacks.mozilla.org/	Hacks blog	new tab	Add '(opens in new tab)' to text

161 links and buttons have descriptive text

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

https://github.com/mdn/; https://bsky.app/profile/developer.mozilla.org; https://x.com/mozdevnet; https://mastodon.social/@mdn; /en-US/blog/rss.xml; https://www.mozilla.org/en-US/careers/listings/; https://support.mozilla.org/products/mdn-plus; /discord; https://github.com/mdn; https://hacks.mozilla.org/

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

Favicon & Branding

6 icon(s) detected

PASS

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: MDN Web Docs

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name MDN Web Docs ✓192×192 icon ✓512×512 icon ✓Start URL . ✓Display Mode standalone ✓

Name MDN Web Docs Display Mode standalone Theme Color #000000 Background Color #ffffff Icons 2 icon(s)

A+

Lighthouse Accessibility Audits

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

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
Blog `ul.featured-articles > li > article.featured-articles__article > a.featured-articles__tag`
Web APIs `ul.featured-articles > li > article.featured-articles__article > a.featured-articles__tag`
JavaScript `ul.featured-articles > li > article.featured-articles__article > a.featured-articles__tag`
developer.mozilla.org `ul.latest-news > li > article.latest-news__item > a.latest-news__source`
developer.mozilla.org `ul.latest-news > li > article.latest-news__item > a.latest-news__source`
developer.mozilla.org `ul.latest-news > li > article.latest-news__item > a.latest-news__source`
developer.mozilla.org `ul.latest-news > li > article.latest-news__item > a.latest-news__source`
mdn/content `ul.recent-contributions > li.recent-contributions__item > span.recent-contributions__repo > a.external`
mdn/content `ul.recent-contributions > li.recent-contributions__item > span.recent-contributions__repo > a.external`
mdn/content `ul.recent-contributions > li.recent-contributions__item > span.recent-contributions__repo > a.external`
mdn/content `ul.recent-contributions > li.recent-contributions__item > span.recent-contributions__repo > a.external`
mdn/content `ul.recent-contributions > li.recent-contributions__item > span.recent-contributions__repo > a.external`
mdn/translated-content `ul.recent-contributions > li.recent-contributions__item > span.recent-contributions__repo > a.external`
mdn/translated-content `ul.recent-contributions > li.recent-contributions__item > span.recent-contributions__repo > a.external`
mdn/translated-content `ul.recent-contributions > li.recent-contributions__item > span.recent-contributions__repo > a.external`
mdn/translated-content `ul.recent-contributions > li.recent-contributions__item > span.recent-contributions__repo > a.external`
mdn/translated-content `ul.recent-contributions > li.recent-contributions__item > span.recent-contributions__repo > a.external`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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

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

●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

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

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

●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

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●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

○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

○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

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