Skip to content
https://riseup.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation
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
No landmarks
REVIEW
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
Info::
Skip navigation link present

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

C
Heading Hierarchy
Action
7 headings, 2 skip(s)
REVIEW
7 headings, 2 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Personal Services
  • H1 Mailing Lists duplicate H1
  • H1 Collaboration duplicate H1
  • H3 Resources skipped
  • H2 System Updates
  • H4 About this site skipped
  • H4 Riseup's Tor Onion Services

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

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

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

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

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

18 pass 2 fail WCAG AA 1 pass AA only
title Home - riseup.net
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · top of page (header area)
a Riseup Home
1.94:1
#000000
on
#263F5B
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 System Updates16.39:13.0:1
#000000
#E6E3DC
Pass
h3 Resources16.39:13.0:1
#000000
#E6E3DC
Pass
title Home - riseup.net1.32:14.5:1
#000000
#222222
Fail
a Skip to Main Content7.48:14.5:1
#000000
#5E9EE3
Pass
a Riseup Home1.94:14.5:1
#000000
#263F5B
Fail
a Home5.37:14.5:1
#000000
#5184BB
Pass
a Donate!10.36:14.5:1
#000000
#94BAE0
Pass
div Red Accounts16.39:14.5:1
#000000
#E6E3DC
Pass
a Account16.39:14.5:1
#000000
#E6E3DC
Pass
a Support16.39:14.5:1
#000000
#E6E3DC
Pass
a Email16.39:14.5:1
#000000
#E6E3DC
Pass
div Black Accounts16.39:14.5:1
#000000
#E6E3DC
Pass
a VPN16.39:14.5:1
#000000
#E6E3DC
Pass
div Other Services16.39:14.5:1
#000000
#E6E3DC
Pass
a Lists16.39:14.5:1
#000000
#E6E3DC
Pass
a Pad16.39:14.5:1
#000000
#E6E3DC
Pass
a Share16.39:14.5:1
#000000
#E6E3DC
Pass
a Groups16.39:14.5:1
#000000
#E6E3DC
Pass
a Home16.39:14.5:1
#000000
#E6E3DC
Pass
a Email16.39:14.5:1
#000000
#E6E3DC
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.

C
Lighthouse Accessibility Audits
Action
Score 75/100 — 5 failing, 11 passed
REVIEW
75

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
English div.row > div.col-sm-8 > div.locale-links > a.label
Email div.col-sm-8 > div#main-content > p > a
VPN div.col-sm-8 > div#main-content > p > a
Login to webmail div.col-sm-6 > ul.fa-ul > li > a
Email div.col-sm-6 > ul.fa-ul > li > a
VPN div.col-sm-6 > ul.fa-ul > li > a
Change my settings div.col-sm-6 > ul.fa-ul > li > a
Request an account div.col-sm-6 > ul.fa-ul > li > a
Reset lost password div.col-sm-6 > ul.fa-ul > li > a
Create a help ticket div.col-sm-6 > ul.fa-ul > li > a
Login to lists div.col-sm-6 > ul.fa-ul > li > a
Get help on lists div.col-sm-6 > ul.fa-ul > li > a
Request a list div.col-sm-6 > ul.fa-ul > li > a
Subscribe div.col-sm-6 > ul.fa-ul > li > a
Unsubscribe div.col-sm-6 > ul.fa-ul > li > a
we.riseup.net ul.fa-ul > li > b > a
pad.riseup.net ul.fa-ul > li > b > a
share.riseup.net ul.fa-ul > li > b > a
Security div.col-sm-8 > div#main-content > p > a
Riseup Help Desk div.col-sm-8 > div#main-content > p > a
Radical Servers div.col-sm-8 > div#main-content > p > a
Minor privacy policy update div.col-sm-4 > div.feed > div.item > div.label
Privacy Policy div.feed > div.item > div.text > a
We need your help! div.col-sm-4 > div.feed > div.item > div.label
Scheduled network outage div.col-sm-4 > div.feed > div.item > div.label
Update on switch outage div.col-sm-4 > div.feed > div.item > div.label
Network switch outage div.col-sm-4 > div.feed > div.item > div.label
Another minor Terms of Service update! div.col-sm-4 > div.feed > div.item > div.label
Terms of Service div.feed > div.item > div.text > a
Minor Terms of Service update div.col-sm-4 > div.feed > div.item > div.label
Terms of Service div.feed > div.item > div.text > a
Winter fundraising campaign div.col-sm-4 > div.feed > div.item > div.label
winter fundraising drive div.feed > div.item > div.text > a
Happy #N30! div.col-sm-4 > div.feed > div.item > div.label
Donate to keep Riseup working hard div.feed > div.item > div.text > a
Certificate update div.col-sm-4 > div.feed > div.item > div.label
certificates were updated div.feed > div.item > div.text > a
Un grand merci à SQiL for a successful translation event! div.col-sm-4 > div.feed > div.item > div.label
SQiL div.feed > div.item > div.text > a
anyone can help improve them div.feed > div.item > div.text > a

These are opportunities to improve the legibility of your content.

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
Resources div.row > div.col-sm-8 > div#main-content > h3
About this site div.row > div.col-sm-6 > div.footer-text > h4.text-center

These are opportunities to improve keyboard navigation in your application.

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.masthead-inner > div.title > div.sitename > a div.masthead-inner > div.title > div.sitename > 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
中文 div.row > div.col-sm-8 > div.locale-links > a.label
Español div.row > div.col-sm-8 > div.locale-links > a.label
English div.row > div.col-sm-8 > div.locale-links > a.label
Português div.row > div.col-sm-8 > div.locale-links > a.label
Pyccĸий div.row > div.col-sm-8 > div.locale-links > a.label
Deutsch div.row > div.col-sm-8 > div.locale-links > a.label
Français div.row > div.col-sm-8 > div.locale-links > a.label
Italiano div.row > div.col-sm-8 > div.locale-links > a.label
Polski div.row > div.col-sm-8 > div.locale-links > a.label
Ελληνικά div.row > div.col-sm-8 > div.locale-links > a.label
Català div.row > div.col-sm-8 > div.locale-links > a.label
Hindi div.row > div.col-sm-8 > div.locale-links > a.label
Request an account div.col-sm-6 > ul.fa-ul > li > a
Reset lost password div.col-sm-6 > ul.fa-ul > li > a
Create a help ticket div.col-sm-6 > ul.fa-ul > li > a
Login to lists div.col-sm-6 > ul.fa-ul > li > a
Get help on lists div.col-sm-6 > ul.fa-ul > li > a
Request a list div.col-sm-6 > ul.fa-ul > li > a
Subscribe div.col-sm-6 > ul.fa-ul > li > a
Unsubscribe div.col-sm-6 > ul.fa-ul > li > a

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.
●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.
●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
●`[lang]` attributes have a valid value
●Skip links are focusable.
○`[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-hidden="true"]` elements do not contain focusable descendents
○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.
○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.
○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.
○`<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.
○Identical links have the same purpose.
○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+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
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