Skip to content
https://joinmastodon.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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'>.
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
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 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Social networking that's not for sale.
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Stay in control of your own timeline
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Build your audience in confidence
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Moderating the way it should be
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Unparalleled creativity
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What our users are saying
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Independent always
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Product
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Resources
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Company
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Why Mastodon?
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Decentralized
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Open Source
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Not for Sale
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Interoperable
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Supported by
1.09:1
#000000
on
#210026
needs 3.0:1 (large text)
19px · bottom of viewport
title Mastodon - Decentralized social media
1.05:1
#000000
on
#140117
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
1.05:1
#000000
on
#140117
needs 4.5:1 (normal text)
16px · top of page (header area)
a Apps
1.05:1
#000000
on
#140117
needs 4.5:1 (normal text)
16px · top of page (header area)
a For Institutions
1.05:1
#000000
on
#140117
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Social networking th…1.09:13.0:1
#000000
#210026
Fail
h2 Stay in control of y…1.09:13.0:1
#000000
#210026
Fail
h2 Build your audience …1.09:13.0:1
#000000
#210026
Fail
h2 Moderating the way i…1.09:13.0:1
#000000
#210026
Fail
h2 Unparalleled creativ…1.09:13.0:1
#000000
#210026
Fail
h2 What our users are s…1.09:13.0:1
#000000
#210026
Fail
h2 Independent always1.09:13.0:1
#000000
#210026
Fail
h2 Product1.09:13.0:1
#000000
#210026
Fail
h2 Resources1.09:13.0:1
#000000
#210026
Fail
h2 Company1.09:13.0:1
#000000
#210026
Fail
h3 Why Mastodon?1.09:13.0:1
#000000
#210026
Fail
h3 Decentralized1.09:13.0:1
#000000
#210026
Fail
h3 Open Source1.09:13.0:1
#000000
#210026
Fail
h3 Not for Sale1.09:13.0:1
#000000
#210026
Fail
h3 Interoperable1.09:13.0:1
#000000
#210026
Fail
h3 Supported by1.09:13.0:1
#000000
#210026
Fail
title Mastodon - Decentral…1.05:14.5:1
#000000
#140117
Fail
a Skip to main content1.05:14.5:1
#000000
#140117
Fail
a Apps1.05:14.5:1
#000000
#140117
Fail
a For Institutions1.05:14.5:1
#000000
#140117
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
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
16 headings
PASS
16 headings
Info::
Single H1 present
  • H1 Social networking that's not for sale.
  • H2 Stay in control of your own timeline
  • H2 Build your audience in confidence
  • H2 Moderating the way it should be
  • H2 Unparalleled creativity
  • H3 Why Mastodon?
  • H3 Decentralized
  • H3 Open Source
  • H3 Not for Sale
  • H3 Interoperable
  • H2 What our users are saying
  • H2 Independent always
  • H3 Supported by
  • H2 Product
  • H2 Resources
  • H2 Company
A+
Alt Text Quality
All 65 images OK
PASS
All 65 images OK
Info::
42 decorative image(s) correctly marked
Info::
23 image(s) with good alt text
65 images 23 good alt text 42 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 24 passed
PASS
92

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Join mastodon.social section.full-width-bg > div.full-width-bg__inner > div.flex > a.flex
Pick another server section.full-width-bg > div.full-width-bg__inner > div.flex > a.flex
Learn more div.full-width-bg > div.full-width-bg__inner > div.row-span-full > a.flex
Learn more div.full-width-bg > div.full-width-bg__inner > div.row-span-full > a.flex
Find a server div.full-width-bg > div.full-width-bg__inner > div.row-span-full > a.flex
Learn more div.full-width-bg > div.full-width-bg__inner > div.row-span-full > a.flex
Donate on Patreon div.py-20 > div.lg:col-span-8 > div.flex > a.flex
Donate directly div.py-20 > div.lg:col-span-8 > div.flex > a.flex
Learn more div.py-20 > div.lg:col-span-8 > div.flex > a.flex
Sponsorship does not equal influence. Mastodon is fully independent. div.mx-auto > main#main > section.grid > p.mt-8

These are opportunities to improve the legibility of your content.

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
Go to slide section.py-20 > div > div.flex > button.rounded-[50%]
Go to slide section.py-20 > div > div.flex > button.rounded-[50%]
Go to slide section.py-20 > div > div.flex > button.rounded-[50%]
Go to slide section.py-20 > div > div.flex > button.rounded-[50%]
Go to slide div.full-width-bg__inner > div > div.flex > button.rounded-[50%]
Go to slide div.full-width-bg__inner > div > div.flex > button.rounded-[50%]
Go to slide div.full-width-bg__inner > div > div.flex > button.rounded-[50%]
Go to slide div.full-width-bg__inner > div > div.flex > button.rounded-[50%]
Go to slide div.full-width-bg__inner > div > div.flex > button.rounded-[50%]
Go to slide div.full-width-bg__inner > div > div.flex > button.rounded-[50%]
Go to slide div.full-width-bg__inner > div > div.flex > button.rounded-[50%]
Go to slide div.full-width-bg__inner > div > div.flex > button.rounded-[50%]
Go to slide div.full-width-bg__inner > div > div.flex > button.rounded-[50%]
Go to slide div.full-width-bg__inner > div > div.flex > button.rounded-[50%]
Go to slide div.full-width-bg__inner > div > div.flex > button.rounded-[50%]
Go to slide div.full-width-bg__inner > div > div.flex > button.rounded-[50%]

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
●`[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
●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
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○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