Skip to content
https://etymonline.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
3
REVIEW
6
PASS
4
INFO
0
Checks
13
4 PASS 6 REVIEW 3 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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.
C
Landmark Structure
Action
4 landmarks
REVIEW
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 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
Favicon & Branding
Action
8 icon(s) detected
REVIEW
8 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
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
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 #8e001f ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
h2 Support
2.17:1
#000000
on
#8E001F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Apps
2.17:1
#000000
on
#8E001F
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Online Etymology Dic…20.46:13.0:1
#000000
#FFFCF2
Pass
h2 A Word or Two20.46:13.0:1
#000000
#FFFCF2
Pass
h2 About5.22:13.0:1
#000000
#BB6573
Pass
h2 Support2.17:13.0:1
#000000
#8E001F
Fail
h2 Apps2.17:13.0:1
#000000
#8E001F
Fail
title Online Etymology Dic…20.46:14.5:1
#000000
#FFFCF2
Pass
button Log in20.46:14.5:1
#000000
#FFFCF2
Pass
a Columns20.46:14.5:1
#000000
#FFFCF2
Pass
a Forum20.46:14.5:1
#000000
#FFFCF2
Pass
a Apps20.46:14.5:1
#000000
#FFFCF2
Pass
a Premium20.46:14.5:1
#000000
#FFFCF2
Pass
button Log in20.46:14.5:1
#000000
#FFFCF2
Pass
div About20.46:14.5:1
#000000
#FFFCF2
Pass
p This is a map of the…20.46:14.5:1
#000000
#FFFCF2
Pass
a Etymologies20.46:14.5:1
#000000
#FFFCF2
Pass
p are not definitions;…20.46:14.5:1
#000000
#FFFCF2
Pass
p The Online Etymology…20.46:14.5:1
#000000
#FFFCF2
Pass
p Etymonline aims to w…20.46:14.5:1
#000000
#FFFCF2
Pass
a serendipity20.46:14.5:1
#000000
#FFFCF2
Pass
p . Print sources used…20.46:14.5:1
#000000
#FFFCF2
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.

B
Lighthouse Accessibility Audits
Score 84/100 — 6 failing, 24 passed
REVIEW
84

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.h-full > div.relative > div.inline-flex > button.z-0 div.h-full > div.relative > div.inline-flex > button.z-0

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 your speakers ready, because this will be much easier and more enjoyable if… a.flex > div.relative > section.text-davis-gray/80 > span
Mar 5 a.flex > div.p-3 > div.flex > time.text-xs
How to make anything sound scary for fun and profit a.flex > div.relative > section.text-davis-gray/80 > span
Feb 21 a.flex > div.p-3 > div.flex > time.text-xs
A few of the faces glimpsed from the time-travel train while researching "handl… a.flex > div.relative > section.text-davis-gray/80 > span
Feb 10 a.flex > div.p-3 > div.flex > time.text-xs
Quick and reliable accounts of the origin and history of English words. Scholar… div.-mx-4 > div.w-full > div.mb-12 > p.mb-9
Who Did This div.mb-12 > ul > li > a.mb-4
Sources div.mb-12 > ul > li > a.mb-4
Introduction div.mb-12 > ul > li > a.mb-4
Links div.mb-12 > ul > li > a.mb-4
Premium div.mb-12 > ul > li > a.mb-4
Patreon div.mb-12 > ul > li > a.mb-4
Donate with PayPal div.mb-12 > ul > li > a.mb-4
Merch div.mb-12 > ul > li > a.mb-4
Dark div.inline-flex > div#react-aria-:RlnnrrimdfbH1: > button#react-aria-:RlnnrrimdfbH1:-tab-dark > div.relative
Auto div.inline-flex > div#react-aria-:RlnnrrimdfbH1: > button#react-aria-:RlnnrrimdfbH1:-tab-system > div.relative
Terms of Services div.flex > div.flex > div.flex > a.link-hover
Privacy Policy div.flex > div.flex > div.flex > a.link-hover
English (English) div.flex > div.flex > div > button#react-aria-:Rtnnrrimdfb:
© 2001 - 2026 Douglas Harper div.flex > div.flex > div.text-sm > a.text-battleship-gray

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Get Chrome Extension Get iOS App Get Android App div.-mx-4 > div.w-full > div.mb-12 > ul

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
© 2001 - 2026 Douglas Harper div.flex > div.flex > div.text-sm > a.text-battleship-gray

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
Auto div.bg-battleship-gray > div.inline-flex > div#react-aria-:RlnnrrimdfbH1: > button#react-aria-:RlnnrrimdfbH1:-tab-system
○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
●Image elements have `[alt]` attributes
●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
●Links are distinguishable without relying on color.
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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 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
○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.
A+
Heading Hierarchy
5 headings
PASS
5 headings
Info::
Single H1 present
  • H1 Online Etymology Dictionary
  • H2 A Word or Two
  • H2 About
  • H2 Support
  • H2 Apps
A
Alt Text Quality
2 of 4 images have issues
PASS
2 of 4 images have issues
Warning::
2 image(s) with generic alt text
Info::
2 image(s) with good alt text
4 images 2 good alt text 2 generic
IssueCount
generic2 image(s)
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#react-aria-:Rqcnrrimdfb:textSearcharia-label
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Etymonline - Online Etymology Dictionary | Origin, history and meaning of English words
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Etymonline - Online Etymology Dictionary | Origin, history and meaning of English words ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name Etymonline - Online Etymology Dictionary | Origin, history and meaning of English words Display Mode standalone Theme Color #83001d Background Color #F1EBD7 Icons 6 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