Skip to content
https://gitter.im

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 MAIN (missing!) CONTENTINFO footer

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

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

C
Alt Text Quality
Action
8 of 17 images have issues
REVIEW
8 of 17 images have issues
Critical::
8 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 decorative image(s) correctly marked
Info::
8 image(s) with good alt text
17 images 8 good alt text 1 decorative 8 missing
IssueCount
missing8 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 13 fail WCAG AA
REVIEW

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

7 pass 13 fail WCAG AA 5 pass AA only
h1 Where communities thrive
2.75:1
#000000
on
#7332A8
needs 3.0:1 (large text)
32px · above the fold
title Gitter — Where developers come to talk…
2.46:1
#000000
on
#692F98
needs 4.5:1 (normal text)
16px · top of page (header area)
a Apps
2.92:1
#000000
on
#8132A3
needs 4.5:1 (normal text)
16px · top of page (header area)
a Documentation
3.43:1
#000000
on
#913BAC
needs 4.5:1 (normal text)
16px · top of page (header area)
a Open source
3.36:1
#000000
on
#8E3BAB
needs 4.5:1 (normal text)
16px · top of page (header area)
span Sign-in to start talking
3.14:1
#000000
on
#8538AA
needs 4.5:1 (normal text)
16px · above the fold
span Sign-in
2.82:1
#000000
on
#7732AA
needs 4.5:1 (normal text)
16px · above the fold
span Latest news
2.81:1
#000000
on
#7136AA
needs 4.5:1 (normal text)
16px · above the fold
span Gitter has migrated to Matrix
2.66:1
#000000
on
#6834AA
needs 4.5:1 (normal text)
16px · above the fold
p Gitter is a chat and networking platform…
2.95:1
#000000
on
#713BAF
needs 4.5:1 (normal text)
16px · above the fold
span Sign-in to start talking
3.20:1
#000000
on
#7841B2
needs 4.5:1 (normal text)
16px · above the fold
span Sign-in
3.33:1
#000000
on
#7945B5
needs 4.5:1 (normal text)
16px · above the fold
a Get the apps
3.33:1
#000000
on
#7A44B6
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Where communities th…2.75:13.0:1
#000000
#7332A8
Fail
h1 Trusted by4.44:13.0:1
#000000
#9A5F95
Pass
h1 Matrix native4.44:13.0:1
#000000
#9A5F95
Pass
h1 Get Gitter4.44:13.0:1
#000000
#9A5F95
Pass
h1 Loved by our users4.44:13.0:1
#000000
#9A5F95
Pass
h2 Built on Matrix3.99:13.0:1
#000000
#8852BD
Pass
h2 Simple to start4.80:13.0:1
#000000
#9F62AA
Pass
h2 Markdown and LaTeX4.55:13.0:1
#000000
#9D6096
Pass
title Gitter — Where dev…2.46:14.5:1
#000000
#692F98
Fail
a Apps2.92:14.5:1
#000000
#8132A3
Fail
a Documentation3.43:14.5:1
#000000
#913BAC
Fail
a Open source3.36:14.5:1
#000000
#8E3BAB
Fail
span Sign-in to start tal…3.14:14.5:1
#000000
#8538AA
Fail
span Sign-in2.82:14.5:1
#000000
#7732AA
Fail
span Latest news2.81:14.5:1
#000000
#7136AA
Fail
span Gitter has migrated …2.66:14.5:1
#000000
#6834AA
Fail
p Gitter is a chat and…2.95:14.5:1
#000000
#713BAF
Fail
span Sign-in to start tal…3.20:14.5:1
#000000
#7841B2
Fail
span Sign-in3.33:14.5:1
#000000
#7945B5
Fail
a Get the apps3.33:14.5:1
#000000
#7A44B6
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.

B
Lighthouse Accessibility Audits
Score 81/100 — 3 failing, 13 passed
REVIEW
81

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
SIGN-IN div.panel-content-wrapper > div.intro-panel-cta-button-block > a.button--kind-primary > span.sign-in-short-text
The Gitter webapp is available in all modern browsers, and there are a variety … section#apps > div.panel-content-wrapper > div.apps-content-wrapper > p.apps-main-description
GITTER WEB div.panel-content-wrapper > div.apps-content-wrapper > p.app-button-block > a.app-button
DOWNLOAD ELEMENT div.panel-content-wrapper > div.apps-content-wrapper > p.app-button-block > a.app-button
After downloading Element, be sure to specify gitter.im as the homeserver. section#apps > div.panel-content-wrapper > div.apps-content-wrapper > p.astro-J7PV25F6
gitter.im div.panel-content-wrapper > div.apps-content-wrapper > p.astro-J7PV25F6 > code.astro-J7PV25F6
Chris Nicholson div.testimonials-quotes > blockquote.testimonials-quote > cite.testimonials-quote-citation > strong.astro-J7PV25F6
, Deeplearning4j div.testimonials-quotes > blockquote.testimonials-quote > cite.testimonials-quote-citation > span.testimonial-cite-descriptor
Loved by our users section.testimonials-panel > div.testimonials-content-wrapper > div.testimonials-content-block > h1.testimonials-heading
Gitter is nothing without the people using it day in and day out. section.testimonials-panel > div.testimonials-content-wrapper > div.testimonials-content-block > p.testimonials-main-description
We need updated quotes! If you love Gitter, Tweet us @gitchat with what Gitter … section.testimonials-panel > div.testimonials-content-wrapper > div.testimonials-content-block > p.astro-J7PV25F6
@gitchat div.testimonials-content-wrapper > div.testimonials-content-block > p.astro-J7PV25F6 > a.astro-J7PV25F6
Copyright © 2025 New Vector Ltd footer.footer-bottom > div.footer-content-wrapper > div.footer-copyright-notice > small.astro-SZ7XMLTE
MATRIX API div.footer-content-wrapper > ul.footer-link-list > li.footer-link-list-item > a.bottom-panel-navigation-link
BLOG div.footer-content-wrapper > ul.footer-link-list > li.footer-link-list-item > a.bottom-panel-navigation-link
TWITTER div.footer-content-wrapper > ul.footer-link-list > li.footer-link-list-item > a.bottom-panel-navigation-link

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section#apps > div.panel-content-wrapper > div.apps-screenshot-wrapper > img.apps-screenshot-image section#apps > div.panel-content-wrapper > div.apps-screenshot-wrapper > img.apps-screenshot-image
div.testimonials-quotes > blockquote.testimonials-quote > div.testimonial-image-wrapper > img.astro-J7PV25F6 div.testimonials-quotes > blockquote.testimonials-quote > div.testimonial-image-wrapper > img.astro-J7PV25F6
div.testimonials-quotes > blockquote.testimonials-quote > div.testimonial-image-wrapper > img.astro-J7PV25F6 div.testimonials-quotes > blockquote.testimonials-quote > div.testimonial-image-wrapper > img.astro-J7PV25F6
div.testimonials-quotes > blockquote.testimonials-quote > div.testimonial-image-wrapper > img.astro-J7PV25F6 div.testimonials-quotes > blockquote.testimonials-quote > div.testimonial-image-wrapper > img.astro-J7PV25F6
div.testimonials-quotes > blockquote.testimonials-quote > div.testimonial-image-wrapper > img.astro-J7PV25F6 div.testimonials-quotes > blockquote.testimonials-quote > div.testimonial-image-wrapper > img.astro-J7PV25F6
div.testimonials-quotes > blockquote.testimonials-quote > div.testimonial-image-wrapper > img.astro-J7PV25F6 div.testimonials-quotes > blockquote.testimonials-quote > div.testimonial-image-wrapper > img.astro-J7PV25F6
div.testimonials-quotes > blockquote.testimonials-quote > div.testimonial-image-wrapper > img.astro-J7PV25F6 div.testimonials-quotes > blockquote.testimonials-quote > div.testimonial-image-wrapper > img.astro-J7PV25F6
div.testimonials-quotes > blockquote.testimonials-quote > div.testimonial-image-wrapper > img.astro-J7PV25F6 div.testimonials-quotes > blockquote.testimonials-quote > div.testimonial-image-wrapper > img.astro-J7PV25F6

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

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-hidden="true"]` is not present on the document `<body>`
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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.
○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.
A
Heading Hierarchy
8 headings
PASS
8 headings
Warning::
Multiple H1 headings (5 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Where communities thrive
  • H2 Built on Matrix
  • H2 Simple to start
  • H2 Markdown and LaTeX
  • H1 Trusted by duplicate H1
  • H1 Matrix native duplicate H1
  • H1 Get Gitter duplicate H1
  • H1 Loved by our users duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback