Skip to content
https://discourse.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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.
C
Alt Text Quality
Action
6 of 88 images have issues
REVIEW
6 of 88 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
1 image(s) with generic alt text
Info::
82 image(s) with good alt text
88 images 82 good alt text 1 generic 5 missing
IssueCount
missing5 image(s)
generic1 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

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 ✓Page Title Discourse on YouTube ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
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
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 10 fail WCAG AA
REVIEW

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

10 pass 10 fail WCAG AA
h1 Where tech companies
1.38:1
#000000
on
#2E1C49
needs 3.0:1 (large text)
32px · mid-page
title Discourse | Where Tech Companies Build C…
1.38:1
#000000
on
#2E1C49
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.38:1
#000000
on
#2E1C49
needs 4.5:1 (normal text)
16px · top of page (header area)
button About
1.38:1
#000000
on
#2E1C49
needs 4.5:1 (normal text)
16px · top of page (header area)
a What is Discourse?
1.38:1
#000000
on
#2E1C49
needs 4.5:1 (normal text)
16px · top of page (header area)
a Who we are
1.38:1
#000000
on
#2E1C49
needs 4.5:1 (normal text)
16px · above the fold
a Open source
1.38:1
#000000
on
#2E1C49
needs 4.5:1 (normal text)
16px · above the fold
a Customers
1.38:1
#000000
on
#2E1C49
needs 4.5:1 (normal text)
16px · above the fold
a Wall of love
1.38:1
#000000
on
#2E1C49
needs 4.5:1 (normal text)
16px · above the fold
a Partners
1.38:1
#000000
on
#2E1C4A
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Where tech companies1.38:13.0:1
#000000
#2E1C49
Fail
h2 What would you like …19.86:13.0:1
#000000
#F9F8FC
Pass
h2 Enterprise-grade inf…19.86:13.0:1
#000000
#F9F8FC
Pass
h2 See Discourse in act…19.86:13.0:1
#000000
#F9F8FC
Pass
h2 Inspired?19.86:13.0:1
#000000
#F9F8FC
Pass
h2 Launch your communit…19.86:13.0:1
#000000
#F9F8FC
Pass
h3 Building blocks for …19.86:13.0:1
#000000
#F9F8FC
Pass
h3 You own your19.86:13.0:1
#000000
#F9F8FC
Pass
h3 What our19.86:13.0:1
#000000
#F9F8FC
Pass
h3 Local Guides19.86:13.0:1
#000000
#F9F8FC
Pass
h3 Support that19.86:13.0:1
#000000
#F9F8FC
Pass
title Discourse | Where Te…1.38:14.5:1
#000000
#2E1C49
Fail
a Skip to content1.38:14.5:1
#000000
#2E1C49
Fail
button About1.38:14.5:1
#000000
#2E1C49
Fail
a What is Discourse?1.38:14.5:1
#000000
#2E1C49
Fail
a Who we are1.38:14.5:1
#000000
#2E1C49
Fail
a Open source1.38:14.5:1
#000000
#2E1C49
Fail
a Customers1.38:14.5:1
#000000
#2E1C49
Fail
a Wall of love1.38:14.5:1
#000000
#2E1C49
Fail
a Partners1.38:14.5:1
#000000
#2E1C4A
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
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main menu" MAIN CONTENTINFO footer
A
Heading Hierarchy
19 headings, 1 skip(s)
PASS
19 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Where tech companies build communities
  • H2 What would you like to build?
  • H2 Enterprise-grade infrastructure for mission-critical communities
  • H3 Building blocks for a complete community platform
  • H3 You own your community and your data
  • H2 See Discourse in action across the internet's best communities
  • H2 Inspired?Launch your community in minutes.
  • H3 What our customers are saying
  • H3 Local Guides
  • H3 Support that understands your stack
  • H4 Expert support team
  • H4 Community forum
  • H4 Resource center
  • H4 Start building your community today
  • H6 Features & Pricing skipped
  • H6 Company
  • H6 Community & Support
  • H6 Compare
  • H6 Legal

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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 90/100 — 3 failing, 24 passed
PASS
90

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Features & Pricing div.site-footer__wrapper > div.site-footer__top > div.site-footer__col > h6

These are opportunities to improve keyboard navigation in your application.

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
div.features-section__inner > div.feature-card > div.feature-card__media > img div.features-section__inner > div.feature-card > div.feature-card__media > img
div.features-section__inner > div.feature-card > div.feature-card__media > img div.features-section__inner > div.feature-card > div.feature-card__media > img
div.features-section__inner > div.feature-card > div.feature-card__media > img div.features-section__inner > div.feature-card > div.feature-card__media > img
div.features-section__inner > div.feature-card > div.feature-card__media > img div.features-section__inner > div.feature-card > div.feature-card__media > img
div.features-section__inner > div.feature-card > div.feature-card__media > img div.features-section__inner > div.feature-card > div.feature-card__media > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.site-header-container > header.site-header > div.site-header-logo-container > a.logo div.site-header-container > header.site-header > div.site-header-logo-container > a.logo
div.site-footer__col > ul.site-footer__list > li > a.site-footer__link div.site-footer__col > ul.site-footer__list > li > a.site-footer__link
div.site-footer__col > ul.site-footer__list > li > a div.site-footer__col > ul.site-footer__list > li > a
div.site-footer__col > ul.site-footer__list > li > a.site-footer__link div.site-footer__col > ul.site-footer__list > li > a.site-footer__link
div.site-footer__col > ul.site-footer__list > li > a.site-footer__link div.site-footer__col > ul.site-footer__list > li > a.site-footer__link
div.site-footer__col > ul.site-footer__list > li > a.site-footer__link div.site-footer__col > ul.site-footer__list > li > a.site-footer__link
div.site-footer__col > ul.site-footer__list > li > a.site-footer__link div.site-footer__col > ul.site-footer__list > li > a.site-footer__link

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.

○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
●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
●`[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.
●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
●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.
●Document has a main landmark.
●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 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.
○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.

Send Feedback