Skip to content
https://dontwordle.app

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
86
GRADE
B
FIX
3
REVIEW
4
PASS
17
INFO
0
Checks
24
17 PASS 4 REVIEW 3 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
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::
3 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <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
Mobile-Readable Font Sizes
94% of visible text renders at >= 12 CSS px (7 below threshold)
REVIEW
94% of visible text renders at >= 12 CSS px (7 below threshold)
Info::
7 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.5px ("EN"); <span> 11.5px ("ES"); <span> 11.5px ("FR"); <span> 11.5px ("DE"); <span> 11.5px ("PT").
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 | Dont Wordle ✓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
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+
Landmark Structure
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary navigation" MAIN CONTENTINFO footer
A+
Heading Hierarchy
19 headings
PASS
19 headings
Info::
Single H1 present
  • H1 Dont Wordle
  • H2 Explore the Reverse Wordle category
  • H2 How the reverse puzzle works
  • H3 Green locks
  • H3 Amber relocates
  • H3 Gray narrows
  • H2 Why Dont Wordle is harder than it looks
  • H2 How to read the legal-word counter
  • H2 Practical Dont Wordle strategy
  • H3 Keep the path wide
  • H3 Use undos early
  • H3 Avoid perfect clues
  • H3 Watch the counter
  • H2 Dont Wordle compared with other reverse word games
  • H2 Common mistakes that end a run
  • H2 Need help on an Antiwordle board?
  • H2 Play Antiwordle Unlimited
  • H2 Dont Wordle FAQ
  • H2 Play the daily reverse puzzle
A+
Heading Text Quality
All 19 heading(s) have substantive, well-formed text
PASS
All 19 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 1 images OK
PASS
All 1 images OK
Info::
1 image(s) with good alt text
1 images 1 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
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
h1 Dont Wordle21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Explore the Reverse …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 How the reverse puzz…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why Dont Wordle is h…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 How to read the lega…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Practical Dont Wordl…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Dont Wordle compared…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Common mistakes that…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Need help on an Anti…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Play Antiwordle Unli…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Dont Wordle FAQ21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Play the daily rever…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Green locks21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Amber relocates21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Gray narrows21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Keep the path wide21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Use undos early21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Avoid perfect clues21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Watch the counter21.00:13.0:1
#000000
#FFFFFF
Pass
title Dont Wordle Game - P…21.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.

A
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 22 passed
PASS
92

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile
empty section#play > div.board > div.board-row > div.tile

These are opportunities to improve the usage of ARIA in your application which 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
Play now main#main-content > article#seo-main > section > a.primary-button

These are opportunities to improve the legibility of your content.

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
DW Dont Wordle body > div.site-page > header.site-header > a.brand-link
EN ▾ header.site-header > div.header-actions > details.language-switcher > summary.language-trigger
○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.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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.
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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 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
○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
○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.
○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.
○`<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.
○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