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 2 REVIEW 4 FIX

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: telephone=no

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 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

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

Heading Hierarchy

11 headings

PASS

11 headings

Single H1 present

3 empty heading(s)

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

H1 Material Design
H2 M3 Expressive: Design with emotion
H2 (empty)
H2 (empty)
H2 Expressive components
H2 (empty)
H2 How to apply M3 Expressive
H2 Popular resources
H3 Social
H3 Libraries
H3 Archived versions

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 10 images OK

PASS

All 10 images OK

10 decorative image(s) correctly marked

10 images 10 decorative

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

45 links, 2 buttons — all OK

PASS

45 links, 2 buttons — all OK

16 link(s) open in new tab without warning

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

Got: /get-started; https://www.figma.com/community/file/1035203688168086460; https://design.google/library/expressive-material-design-google-research?utm_…; /blog/m3-expressive-motion-theming?utm_source=homepage&utm_medium=tile&utm_ca…; https://io.google/2025/explore/technical-session-24?utm_source=homepage&utm_m…; https://www.figma.com/community/file/1035203688168086460; https://www.github.com/material-components; https://x.com/googledesign; https://www.youtube.com/@googledesign; https://material.io/feed.xml (+6 more)

29 link(s) with descriptive text

45 links

0 empty

0 generic text

16 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/get-started	Get started	new tab	Add '(opens in new tab)' to text
https://www.figma.com/community/file/103…	Updated: Figma M3 Design KitQu…	new tab	Add '(opens in new tab)' to text
/styles/shape/overview-principles?utm_so…	Expanded: Shape libraryNew set…	img no alt	Add alt attribute to the image
/blog/building-with-m3-expressive?utm_so…	Blog: Guide to our latest upda…	img no alt	Add alt attribute to the image
https://design.google/library/expressive…	Blog: Research InsightsDive in…	new tab	Add '(opens in new tab)' to text
/components/toolbars/overview?utm_source…	New: ToolbarsFlexible componen…	img no alt	Add alt attribute to the image
/components/split-button/overview?utm_so…	New: Split buttonPair a button…	img no alt	Add alt attribute to the image
/components/progress-indicators/overview…	Updated: Progress indicatorsAn…	img no alt	Add alt attribute to the image
/components/button-groups/overview?utm_s…	New: Button groupsA new way to…	img no alt	Add alt attribute to the image
/blog/building-with-m3-expressive?utm_so…	See all expressive componentsC…	img no alt	Add alt attribute to the image
/blog/m3-expressive-motion-theming?utm_s…	Blog: Using motion physicsLear…	new tab	Add '(opens in new tab)' to text
https://io.google/2025/explore/technical…	Watch: Build with M3 Expressiv…	new tab	Add '(opens in new tab)' to text
https://www.figma.com/community/file/103…	Figma M3 Design KitCustomizabl…	new tab	Add '(opens in new tab)' to text
https://www.github.com/material-componen…	Find us on Github	new tab	Add '(opens in new tab)' to text
https://x.com/googledesign	Find us on X	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@googledesign	Find us on Youtube	new tab	Add '(opens in new tab)' to text
https://material.io/feed.xml	Blog RSS	new tab	Add '(opens in new tab)' to text
https://m1.material.io	Material Design 1	new tab	Add '(opens in new tab)' to text
https://m2.material.io	Material Design 2	new tab	Add '(opens in new tab)' to text
https://www.google.com	Google	new tab	Add '(opens in new tab)' to text
https://policies.google.com/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://policies.google.com/terms	Terms of Service	new tab	Add '(opens in new tab)' to text
https://google.qualtrics.com/jfe/form/SV…	Join research studies	new tab	Add '(opens in new tab)' to text

31 links and buttons have descriptive text

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

/get-started; https://www.figma.com/community/file/1035203688168086460; https://design.google/library/expressive-material-design-google-research?utm_…; /blog/m3-expressive-motion-theming?utm_source=homepage&utm_medium=tile&utm_ca…; https://io.google/2025/explore/technical-session-24?utm_source=homepage&utm_m…; https://www.figma.com/community/file/1035203688168086460; https://www.github.com/material-components; https://x.com/googledesign; https://www.youtube.com/@googledesign; https://material.io/feed.xml (+6 more)

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

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Material Design	20.46:1	3.0:1	#000000	#FEFBFF	Pass
h2 M3 Expressive: Desig…	20.46:1	3.0:1	#000000	#FEFBFF	Pass
h2 Popular resources	20.46:1	3.0:1	#000000	#FEFBFF	Pass
h3 Social	20.46:1	3.0:1	#000000	#FEFBFF	Pass
h3 Libraries	20.46:1	3.0:1	#000000	#FEFBFF	Pass
h3 Archived versions	20.46:1	3.0:1	#000000	#FEFBFF	Pass
title Material Design 3 - …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span menu_open	20.46:1	4.5:1	#000000	#FEFBFF	Pass
span search	20.46:1	4.5:1	#000000	#FEFBFF	Pass
div Search	20.46:1	4.5:1	#000000	#FEFBFF	Pass
span material_design	20.46:1	4.5:1	#000000	#FEFBFF	Pass
div Home	20.46:1	4.5:1	#000000	#FEFBFF	Pass
span apps	20.46:1	4.5:1	#000000	#FEFBFF	Pass
div Get started	20.46:1	4.5:1	#000000	#FEFBFF	Pass
span code	20.46:1	4.5:1	#000000	#FEFBFF	Pass
div Develop	20.46:1	4.5:1	#000000	#FEFBFF	Pass
span arrow_forward	20.46:1	4.5:1	#000000	#FEFBFF	Pass
span book	20.46:1	4.5:1	#000000	#FEFBFF	Pass
div Foundations	20.46:1	4.5:1	#000000	#FEFBFF	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+

Lighthouse Accessibility Audits

Score 100/100 — 1 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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Material blog News, tutorials, and inspiration from the Material team `div.section > mio-card-set.ng-tns-c26-2 > mio-card.ng-tns-c26-2 > a`

○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

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●All heading elements contain content.

○`[accesskey]` values are unique

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

○Image elements have `[alt]` attributes

○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

○Tables have different content in the summary attribute and `<caption>`.

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