Skip to content
https://roll20.net

Accessibility

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

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

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
Alt Text Quality
Action
4 of 91 images have issues
FIX
4 of 91 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
4 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
18 decorative image(s) correctly marked
Info::
69 image(s) with good alt text
91 images 69 good alt text 18 decorative 4 missing
IssueCount
missing4 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
✗ 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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
41 headings
REVIEW
41 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 Cookie Preferences
  • H3 Play Now
  • H3 Play Now
  • H3 Join a Game
  • H3 Join a Game
  • H3 Shop
  • H3 Shop
  • H3 Tools
  • H3 Tools
  • H3 Characters
  • H3 Characters
  • H3 Compendium
  • H3 Compendium
  • H3 Community
  • H3 Community
  • H3 Sign In
  • H3 Sign In
  • H2 The #1 Choice
  • H2 For D&D Online.
  • H2 Start with Ready-to-Play Adventures
  • H3 Sign Up Free
  • H3 Pick your Game
  • H3 Find your Party
  • H3 Play
  • H2 User Testimonials
  • H3 Customize Your Game
  • H4 Automate Rolls & Actions
  • H4 Character Sheets for Every System
  • H4 Advanced Customization (Optional)
  • H4 Dungeon Scrawl Free Map Creation with Dungeon Scrawl
  • H2 Join the Community
  • H2 Join the Community
  • H2 New to Tabletop Roleplaying Games? Start Here
  • H3 Is D&D For Me?
  • H3 How to Find Your First Group
  • H3 Roll20 Masterclass Series
  • H2 Latest News
  • H3 Roll20 x Demiplane Integration: Performance & Account Linking Enhancements
  • H3 Ravenloft: The Horrors Within – Limited Time Pre-Order Bonuses
  • H3 Roll20’s Ongoing Performance Updates
  • H3 Ready to start your adventure?

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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 Roll20: Online virtual tabletop for pen and paper RPGs and board games ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A+
Form Accessibility
All 17 controls labeled
PASS
All 17 controls labeled
Info::
17 control(s) properly labeled
17 controls
17 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cookie-modal-inputcheckboxAccept cookiesnone
#input_login-emailemailEmail Addressaria-label
#input_login-passwordpasswordPasswordaria-label
#input_login-emailemailEmail Addressaria-label
#input_login-passwordpasswordPasswordaria-label
#input_login-emailemailEmail Addressaria-label
#input_login-passwordpasswordPasswordaria-label
#input_login-emailemailEmail Addressaria-label
#input_login-passwordpasswordPasswordaria-label
#input_login-emailemailEmail Addressaria-label
#input_login-passwordpasswordPasswordaria-label
#input_login-emailemailEmail Addressaria-label
#input_login-passwordpasswordPasswordaria-label
#input_login-emailemailEmail Addressaria-label
#input_login-passwordpasswordPasswordaria-label
#input_login-emailemailEmail Addressaria-label
#input_login-passwordpasswordPasswordaria-label
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 The #1 Choice14.96:13.0:1
#000000
#D3DAE8
Pass
h2 For D&D Online.14.96:13.0:1
#000000
#D3DAE8
Pass
h2 Start with Ready-to-…14.96:13.0:1
#000000
#D3DAE8
Pass
h2 User Testimonials14.96:13.0:1
#000000
#D3DAE8
Pass
h2 Join the Community14.96:13.0:1
#000000
#D3DAE8
Pass
h2 Join the Community14.96:13.0:1
#000000
#D3DAE8
Pass
h2 New to Tabletop Role…14.96:13.0:1
#000000
#D3DAE8
Pass
h2 Latest News14.96:13.0:1
#000000
#D3DAE8
Pass
h3 Cookie Preferences8.07:13.0:1
#000000
#90A3B2
Pass
h3 Play Now9.48:13.0:1
#000000
#A2B0BD
Pass
h3 Play Now9.62:13.0:1
#000000
#A4B1BF
Pass
h3 Join a Game11.98:13.0:1
#000000
#B8C5D4
Pass
h3 Join a Game12.39:13.0:1
#000000
#BCC8D8
Pass
h3 Shop14.96:13.0:1
#000000
#D3DAE8
Pass
h3 Shop14.96:13.0:1
#000000
#D3DAE8
Pass
h3 Tools14.96:13.0:1
#000000
#D3DAE8
Pass
h3 Tools14.96:13.0:1
#000000
#D3DAE8
Pass
h3 Characters14.96:13.0:1
#000000
#D3DAE8
Pass
h3 Characters14.96:13.0:1
#000000
#D3DAE8
Pass
h3 Compendium14.96:13.0:1
#000000
#D3DAE8
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.

A+
Lighthouse Accessibility Audits
Score 95/100 — 3 failing, 27 passed
PASS
95

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. 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
here body > div#gdpr-notification > div.bottom-banner__message > a#banner-link-preferences

These are opportunities to improve the legibility of your content.

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Join Roll20 Discord div.community-content-div > div.community-content-wrapper > div.community-action-items-wrapper > button.community-visit
Find a Group div.community-content-div > div.community-content-wrapper > div.community-action-items-wrapper > button.community-visit
Browse Forums div.community-content-div > div.community-content-wrapper > div.community-action-items-wrapper > button.community-visit
Visit r/Roll20 div.community-content-div > div.community-content-wrapper > div.community-action-items-wrapper > button.community-visit
○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.
●`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
●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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●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
○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
○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.
○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.
○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