Skip to content
https://yourdictionary.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
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
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.
C
Landmark Structure
Action
9 landmarks
REVIEW
9 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
Info::
All <nav> elements are properly labeled
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" 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

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found · YourDictionary ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
A+
Heading Hierarchy
30 headings
PASS
30 headings
Info::
Single H1 present
  • H1 YourDictionary
  • H2 We Have a Way With Words
  • H2 Word of the Day
  • H3 Empathy
  • H3 YourDictionary on Instagram
  • H2 Daily Grammar
  • H3 What Is A Reciprocal Pronoun?
  • H3 Have You Subscribed to Our Newsletters?
  • H2 The World's Most Powerful Dictionary
  • H3 Dictionary
  • H3 Thesaurus
  • H3 Sentences
  • H2 Trending Topics
  • H2 Fiancé vs. Fiancée: Does the Extra 'E' Make a Difference?
  • H2 Beat Today's NYT Crossplay With Our Hint Tool
  • H2 What Does SMTH Mean? The Abbreviation Explained
  • H2 Find the Perfect 5-Letter Word for Wordle
  • H2 6 Types of Plagiarism and How to Avoid Them
  • H2 Look Up Any Word With Our Scrabble Dictionary
  • H2 What Your Favorite Pasta's Name Means
  • H2 How Well Do You Know the Basic Grammar Rules of English?
  • H2 WordFinder
  • H3 More than 20 word games
  • H3 A team of language experts
  • H3 Over 290,000 words
  • H3 An enthusiastic community
  • H3 Customized to your needs
  • H3 Convenient mobile app
  • H2 Definitions From Trusted Sources
  • H2 Have You Subscribed to Our Newsletters?
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
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
newslettercheckboxnone
inputtextSearch termaria-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
h1 YourDictionary18.30:13.0:1
#000000
#ECF0F1
Pass
h2 We Have a Way With W…18.30:13.0:1
#000000
#ECF0F1
Pass
h2 Word of the Day18.30:13.0:1
#000000
#ECF0F1
Pass
h2 Daily Grammar18.30:13.0:1
#000000
#ECF0F1
Pass
h2 The World's Most Pow…18.30:13.0:1
#000000
#ECF0F1
Pass
h2 Trending Topics18.30:13.0:1
#000000
#ECF0F1
Pass
h2 Fiancé vs. Fiancée…18.30:13.0:1
#000000
#ECF0F1
Pass
h2 Beat Today's NYT Cro…18.30:13.0:1
#000000
#ECF0F1
Pass
h2 What Does SMTH Mean?…18.30:13.0:1
#000000
#ECF0F1
Pass
h2 Find the Perfect 5-L…18.30:13.0:1
#000000
#ECF0F1
Pass
h2 6 Types of Plagiaris…18.30:13.0:1
#000000
#ECF0F1
Pass
h2 Look Up Any Word Wit…18.30:13.0:1
#000000
#ECF0F1
Pass
h2 What Your Favorite P…18.30:13.0:1
#000000
#ECF0F1
Pass
h2 How Well Do You Know…18.30:13.0:1
#000000
#ECF0F1
Pass
h2 WordFinder18.30:13.0:1
#000000
#ECF0F1
Pass
h2 Definitions From Tru…18.30:13.0:1
#000000
#ECF0F1
Pass
h2 Have You Subscribed …18.30:13.0:1
#000000
#ECF0F1
Pass
h3 YourDictionary on In…18.30:13.0:1
#000000
#ECF0F1
Pass
h3 Have You Subscribed …18.30:13.0:1
#000000
#ECF0F1
Pass
h3 Dictionary18.30:13.0:1
#000000
#ECF0F1
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 97/100 — 2 failing, 27 passed
PASS
97

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

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.social_section > ul.footer_subdomain_links > li.flex > a.social-icon div.social_section > ul.footer_subdomain_links > li.flex > a.social-icon
div.social_section > ul.footer_subdomain_links > li.flex > a.social-icon div.social_section > ul.footer_subdomain_links > li.flex > a.social-icon
div.social_section > ul.footer_subdomain_links > li.flex > a.social-icon div.social_section > ul.footer_subdomain_links > li.flex > a.social-icon
div.social_section > ul.footer_subdomain_links > li.flex > a.social-icon div.social_section > ul.footer_subdomain_links > li.flex > a.social-icon

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.

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
Dictionary div.search-box-wrapper > div.search-box-container > div.filter-dropdown-container > button.filter-dropdown-button
○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
●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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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 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
●Touch targets have sufficient size and spacing.
●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.
○`[accesskey]` values are unique
○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.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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.
○Uses ARIA roles only on compatible elements
○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