Skip to content
https://redmine.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Redmine 404 error ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 2 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Redmine21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Features21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Documentation21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Online demo21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Support & getting he…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Contributing and hel…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Who uses Redmine?21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Redmine books21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Project21.00:13.0:1
#000000
#FFFFFF
Pass
h3 General21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Latest releases21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Resources21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Wiki21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Profile21.00:13.0:1
#000000
#FFFFFF
Pass
title Overview - Redmine6.00:14.5:1
#000000
#628DB6
Pass
label ⚲6.00:14.5:1
#000000
#628DB6
Pass
a Overview21.00:14.5:1
#000000
#FFFFFF
Pass
a Download21.00:14.5:1
#000000
#FFFFFF
Pass
a Activity21.00:14.5:1
#000000
#FFFFFF
Pass
a Roadmap21.00:14.5:1
#000000
#FFFFFF
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 23 passed
REVIEW
85

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
Table of contents div.wiki > ul.toc > li > strong
Powered by Redmine © 2006-2023 Jean-Philippe Lang div#wrapper > div#wrapper2 > div#wrapper3 > div#footer

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
wiki div.wiki > ul > li > a.wiki-page
forums div.wiki > ul > li > a.wiki-page
Custom fields div.wiki > ul > li > a.wiki-page
SCM integration div.wiki > ul > li > a.wiki-page
Redmine features div#content > div.wiki > p > a.wiki-page
Submission guidelines div#content > div.wiki > p > a.wiki-page
Contribute div#content > div.wiki > p > a.wiki-page
Teams div#content > div.wiki > p > a.wiki-page
Redmine Donors page div#content > div.wiki > p > a.wiki-page
This page lists div#content > div.wiki > p > a.wiki-page
Redmine div#wrapper2 > div#wrapper3 > div#footer > a

These are opportunities to improve the legibility of your content.

Names and labels

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#wrapper2 > div#wrapper3 > div#header > a.mobile-toggle-button div#wrapper2 > div#wrapper3 > div#header > a.mobile-toggle-button
tbody > tr > td > a tbody > tr > td > a
tbody > tr > td > a tbody > tr > td > a
tbody > tr > td > a tbody > tr > td > a

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

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
Redmine div.wiki > ul.toc > li > a
Features li > ul > li > a
Documentation li > ul > li > a
Online demo li > ul > li > a
Support & getting help li > ul > li > a
Contributing and helping out li > ul > li > a
Who uses Redmine? li > ul > li > a
Redmine books li > ul > li > a
Multiple projects support div.wiki > ul > li > a.wiki-page
Time tracking div.wiki > ul > li > a.wiki-page
Issue creation via email div.wiki > ul > li > a.wiki-page
User's Guide div.wiki > ul > li > a.wiki-page
Developer's Guide div.wiki > ul > li > a.wiki-page
Changelog div.wiki > ul > li > a.wiki-page
Security Advisories div.wiki > ul > li > a.wiki-page
Frequently Asked Questions div.wiki > ul > li > a.wiki-page
HowTos div.wiki > ul > li > a.wiki-page
Plugins div.wiki > ul > li > a.wiki-page
Themes div.wiki > ul > li > a.wiki-page
Logo and Icon div.wiki > ul > li > a.wiki-page
Third Party Tools div.wiki > ul > li > a.wiki-page

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
●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.
●`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
●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
●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.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<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
15 headings
PASS
15 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H3 Project
  • H3 General
  • H3 Latest releases¶
  • H3 Resources¶
  • H3 Wiki
  • H3 Profile
  • H1 Redmine
  • H1 Redmine¶ duplicate H1
  • H2 Features¶
  • H2 Documentation¶
  • H2 Online demo¶
  • H2 Support & getting help¶
  • H2 Contributing and helping out¶
  • H2 Who uses Redmine?¶
  • H2 Redmine books¶

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+
Alt Text Quality
All 3 images OK
PASS
All 3 images OK
Info::
3 decorative image(s) correctly marked
3 images 3 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="q" id="projects-quick-search">
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#flyout-searchtext⚲for/id
#qtextSearch:for/id
#projects-quick-searchtext(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="text" name="q" id="projects-quick-search">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback