Skip to content
https://thesaurus.com

Accessibility

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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="inputSearchWord">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputSearchWordsearch(Search a word or phrase)placeholder only
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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

Placeholder text disappears on focus and is not a reliable label.

<input type="search" name="inputSearchWord">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

C
Favicon & Branding
Action
9 icon(s) detected
REVIEW
9 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 80/100 — 5 failing, 23 passed
REVIEW
80

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
div#onetrust-consent-sdk > div#ot-sdk-btn-floating > div.ot-floating-button__front > button.ot-floating-button__open div#onetrust-consent-sdk > div#ot-sdk-btn-floating > div.ot-floating-button__front > button.ot-floating-button__open
div#onetrust-consent-sdk > div#ot-sdk-btn-floating > div.ot-floating-button__back > button.ot-floating-button__close div#onetrust-consent-sdk > div#ot-sdk-btn-floating > div.ot-floating-button__back > button.ot-floating-button__close

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.featured-articles-homepage > div.all-articles-container > a.lk-primary-article > img.hero-image div.featured-articles-homepage > div.all-articles-container > a.lk-primary-article > img.hero-image

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.ac-player-wrapper > div.ac-lre-player > div.ac-lre-display-ad-container > iframe div.ac-player-wrapper > div.ac-lre-player > div.ac-lre-display-ad-container > iframe
div.ac-lre-player > div.ac-lre-fallback-ad-wrapper > div.ac-lre-fallback-ad-container > iframe div.ac-lre-player > div.ac-lre-fallback-ad-wrapper > div.ac-lre-fallback-ad-container > iframe
body.pg-tcom-home > iframe body.pg-tcom-home > iframe
body.pg-tcom-home > iframe body.pg-tcom-home > iframe
body.pg-tcom-home > iframe body.pg-tcom-home > iframe
body.pg-tcom-home > iframe body.pg-tcom-home > iframe

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
footer.site-ftr > div.logos-primary-container > div.primary-section > a footer.site-ftr > div.logos-primary-container > div.primary-section > a
div.logos-primary-container > div.primary-section > div.social-logo-container > a div.logos-primary-container > div.primary-section > div.social-logo-container > a
div.logos-primary-container > div.primary-section > div.social-logo-container > a div.logos-primary-container > div.primary-section > div.social-logo-container > a
div.logos-primary-container > div.primary-section > div.social-logo-container > a div.logos-primary-container > div.primary-section > div.social-logo-container > a
div.logos-primary-container > div.primary-section > div.social-logo-container > a div.logos-primary-container > div.primary-section > div.social-logo-container > a
div.logos-primary-container > div.primary-section > div.social-logo-container > a div.logos-primary-container > div.primary-section > div.social-logo-container > a
div.logos-primary-container > div.primary-section > div.social-logo-container > a div.logos-primary-container > div.primary-section > div.social-logo-container > a
div.logos-primary-container > div.primary-section > div.social-logo-container > a div.logos-primary-container > div.primary-section > div.social-logo-container > 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.

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
Get the Word of the Day div.box-content-primary > section.sec-wotd-card > div.box-wotd-card > button.btn-common-cta

These are opportunities to improve the legibility of your content.

○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]` 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.
●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
●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.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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
○`[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
○`<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
○Links are distinguishable without relying on color.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○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.
○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
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 "site navigation" MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
19 headings
PASS
19 headings
Info::
Single H1 present
  • H1 Thesaurus.com
  • H2 The Thesaurus for the Real World
  • H3 Popular searches:
  • H3 Word of the Day
  • H3 braird
  • H2 Featured Articles
  • H3 Grammar
  • H4 5 Grammar Rules You Don't Actually Need to Follow
  • H3 Word Origins
  • H4 All 50 State Names and Their Origins
  • H3 Commonly Confused
  • H4 CV vs. Resume: What Are the Differences?
  • H3 Food & Drink
  • H4 This List of Vegetables Is No Small Potatoes
  • H2 Trending Words
  • H3 EBT 🛒💳
  • H3 NaNoWriMo ✍️⏳
  • H3 Leeroy Jenkins 🎮🤦
  • H3 blockchain 🧱🔗
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404: Not found | Thesaurus.com ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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 Thesaurus for th…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Featured Articles21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trending Words21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Popular searches:21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Grammar21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Word Origins21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Commonly Confused21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Food & Drink21.00:13.0:1
#000000
#FFFFFF
Pass
h3 EBT 🛒…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 NaNoWriMo …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Leeroy Jenkins …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 blockchain …21.00:13.0:1
#000000
#FFFFFF
Pass
title Synonyms and Antonym…21.00:14.5:1
#000000
#FFFFFF
Pass
a Featured21.00:14.5:1
#000000
#FFFFFF
Pass
a Games21.00:14.5:1
#000000
#FFFFFF
Pass
a Cultural21.00:14.5:1
#000000
#FFFFFF
Pass
a Writing tips21.00:14.5:1
#000000
#FFFFFF
Pass
a Thesaurus.com21.00:14.5:1
#000000
#FFFFFF
Pass
a Dictionary.com21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.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.

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

Send Feedback