Skip to content
https://lichess.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
Alt Text Quality
Action
10 of 23 images have issues
FIX
10 of 23 images have issues
Critical::
10 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
10 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
8 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
23 images 5 good alt text 8 decorative 10 missing
IssueCount
missing10 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

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #2e2a24
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 ModePartial Dark Mode
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.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO (missing!)

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

B
Heading Hierarchy
16 headings
REVIEW
16 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Titled Arenas Announcement — April to June 2026
  • H2 This is how much ELO you are losing in the opening
  • H2 Game of the Week 12/52
  • H2 Verrassingen in de opening zoeken... en (automatisch) vinden?
  • H2 Human Estimate Eval Function
  • H2 Bobby Fischer's GOATed Endgame
  • H2 'Looking for trouble' puzzles: do you smell the danger?
  • H2 My Most Beautiful Checkmate Ever
  • H2 Lichess lonewolf S40 round 1: My first Lonewolf season
  • H2 What's Wrong With Engine Analysis
  • H2 Tactics in the closed Spanish
  • H2 Fun stats about the Lichess 2026 Spring Marathon (2 0)
  • H2 White Played a Ponziani Masterpiece — and Still Lost
  • H2 A case for gambits in modern top level tournaments
  • H2 Endgame Bootcamp 7: Mating Nets
  • H2 Open tournaments

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 Page not found • lichess.org Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
14 icon(s) detected
REVIEW
14 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'>.
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Titled Arenas Announcement — April to …
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 This is how much ELO you are losing in t…
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Game of the Week 12/52
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Verrassingen in de opening zoeken... en …
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Human Estimate Eval Function
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Bobby Fischer's GOATed Endgame
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 'Looking for trouble' puzzles: do you sm…
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 My Most Beautiful Checkmate Ever
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Lichess lonewolf S40 round 1: My first L…
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What's Wrong With Engine Analysis
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tactics in the closed Spanish
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Fun stats about the Lichess 2026 Spring …
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 White Played a Ponziani Masterpiece — …
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 A case for gambits in modern top level t…
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Endgame Bootcamp 7: Mating Nets
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Open tournaments
1.15:1
#000000
on
#161512
needs 3.0:1 (large text)
24px · bottom of viewport
title lichess.org • Free Online Chess
1.43:1
#000000
on
#2B2822
needs 4.5:1 (normal text)
16px · top of page (header area)
button Accessibility - Enable blind mode
1.33:1
#000000
on
#25221D
needs 4.5:1 (normal text)
16px · top of page (header area)
div lichess
1.23:1
#000000
on
#1E1C18
needs 4.5:1 (normal text)
16px · top of page (header area)
span .org
1.31:1
#000000
on
#23211E
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Titled Arenas Announ…1.15:13.0:1
#000000
#161512
Fail
h2 This is how much ELO…1.15:13.0:1
#000000
#161512
Fail
h2 Game of the Week 12/…1.15:13.0:1
#000000
#161512
Fail
h2 Verrassingen in de o…1.15:13.0:1
#000000
#161512
Fail
h2 Human Estimate Eval …1.15:13.0:1
#000000
#161512
Fail
h2 Bobby Fischer's GOAT…1.15:13.0:1
#000000
#161512
Fail
h2 'Looking for trouble…1.15:13.0:1
#000000
#161512
Fail
h2 My Most Beautiful Ch…1.15:13.0:1
#000000
#161512
Fail
h2 Lichess lonewolf S40…1.15:13.0:1
#000000
#161512
Fail
h2 What's Wrong With En…1.15:13.0:1
#000000
#161512
Fail
h2 Tactics in the close…1.15:13.0:1
#000000
#161512
Fail
h2 Fun stats about the …1.15:13.0:1
#000000
#161512
Fail
h2 White Played a Ponzi…1.15:13.0:1
#000000
#161512
Fail
h2 A case for gambits i…1.15:13.0:1
#000000
#161512
Fail
h2 Endgame Bootcamp 7: …1.15:13.0:1
#000000
#161512
Fail
h2 Open tournaments1.15:13.0:1
#000000
#161512
Fail
title lichess.org • Free…1.43:14.5:1
#000000
#2B2822
Fail
button Accessibility - Enab…1.33:14.5:1
#000000
#25221D
Fail
div lichess1.23:14.5:1
#000000
#1E1C18
Fail
span .org1.31:14.5:1
#000000
#23211E
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 — 6 failing, 24 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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main.lobby > div.lobby__blog > div.carousel__controls > button.carousel__prev main.lobby > div.lobby__blog > div.carousel__controls > button.carousel__prev
main.lobby > div.lobby__blog > div.carousel__controls > button.carousel__next main.lobby > div.lobby__blog > div.carousel__controls > button.carousel__next

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.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image
div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image div.carousel__track > a.ublog-post-card > span.ublog-post-card__top > img.ublog-post-image

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.

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
REGISTER header#top > div.site-buttons > div.signin-or-signup > a.button
31 hours ago div.daily-feed__update > div > a.daily-feed__update__day > time.set
45 hours ago div.daily-feed__update > div > a.daily-feed__update__day > time.set
2 days ago div.daily-feed__update > div > a.daily-feed__update__day > time.set
2 days ago div.daily-feed__update > div > a.daily-feed__update__day > time.set
3 days ago div.daily-feed__update > div > a.daily-feed__update__day > time.set
3 days ago div.daily-feed__update > div > a.daily-feed__update__day > time.set
4 days ago div.daily-feed__update > div > a.daily-feed__update__day > time.set
All updates » div.daily-feed__updates > div.daily-feed__update > div > a.daily-feed__update__day
≤2000 Bullet tbody > tr > td > a.text
Hourly SuperBlitz tbody > tr > td > a.text
Hourly HyperBullet tbody > tr > td > a.text
Hourly Blitz tbody > tr > td > a.text
≤1500 Blitz tbody > tr > td > a.text

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
Chess Digital League Final div.daily-feed__update > div > p > a
UAE Chess Federation div.daily-feed__update > div > p > a
Watch the interview on YouTube div.daily-feed__update > div > p > a
Roman Dehtiarov div.daily-feed__update > div > p > a
European Individual Chess Championship 2026 div.daily-feed__update > div > p > a
@GlasnostPerestroika div.daily-feed__update > div > p > a
2026 Spring Marathon div.daily-feed__update > div > p > a
Dimitrios Makridis div.daily-feed__update > div > p > a
next Marathon div.daily-feed__update > div > p > a
Watch the interview on YouTube div.daily-feed__update > div > p > a
YouTube div.daily-feed__update > div > p > a
Twitch div.daily-feed__update > div > p > a

These are opportunities to improve the legibility of your content.

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
Streamers » main.lobby > div.lobby__side > section.lobby__streams > a.more

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Philidor Defense Rapid 1h 57m 165 ≤2000 Bullet 27m 130 Hourly Atomic 27m … div.lobby__tournaments-simuls > div.lobby__tournaments > div.lobby__box__content > table.tournaments
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
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
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
Links have a discernible name
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
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`[accesskey]` values are unique
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 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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#tn-tgcheckboxNavigationaria-label
inputinputSearcharia-label
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: lichess.org
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name lichess.org 192×192 icon 512×512 icon Start URL / Display Mode standalone
Name lichess.org Display Mode standalone Theme Color #161512 Background Color #161512 Icons 7 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback