Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 5 REVIEW 3 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Heading Hierarchy

3 headings

REVIEW

3 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H3 Spanish Dictionaries
H3 French and Italian Dictionaries
H3 Language Forums

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

Form Accessibility

2 of 3 controls have issues

REVIEW

2 of 3 controls have issues

2 control(s) without accessible label

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

Got: <input type="text" name="w" id="si">; <input type="submit">

1 control(s) properly labeled

3 controls

1 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#fSelect	select		none
input	submit	(none)	none
#si	text	(none)	none

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

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 - Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

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 #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Lighthouse Accessibility Audits

Action

Score 79/100 — 5 failing, 20 passed

REVIEW

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.

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
.com `body > div#container > div#content > span.dotcom`
Español `div#container > div#content > div.links > a`
Français `div#container > div#content > div.links > a`
Italiano `div#container > div#content > div.links > a`
Português `div#container > div#content > div.links > a`
Català `div#container > div#content > div.links > a`
Deutsch `div#container > div#content > div.links > a`
Svenska `div#container > div#content > div.links > a`
Nederlands `div#container > div#content > div.links > a`
Русский `div#container > div#content > div.links > a`
Polski `div#container > div#content > div.links > a`
Română `div#container > div#content > div.links > a`
Čeština `div#container > div#content > div.links > a`
Ελληνικά `div#container > div#content > div.links > a`
Türkçe `div#container > div#content > div.links > a`
英汉词典 `div#container > div#content > div.links > a`
英和辞書 `div#container > div#content > div.links > a`
영-한 사전 `div#container > div#content > div.links > a`
قاموس إنجليزي - عربي `div#container > div#content > div.links > a`
Virtual dictionaries for non-English language pairs `div#container > div#content > div.links > a`

These are opportunities to improve the legibility of your content.

Names and labels

Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#container > div#content > form#text_form > input.submit-button `div#container > div#content > form#text_form > input.submit-button`

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English-Spanish Spanish-English Spanish-French Spanish-Portuguese Spanish-Itali… `div#content > form#text_form > label.custom-select > select#fSelect`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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.

○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

●Form elements have associated labels

●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 have a discernible name

●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.

●Deprecated ARIA roles were not used

●The page contains a heading, skip link, or landmark region

○`[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

○Buttons have an accessible name

○`<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

○Heading elements appear in a sequentially-descending order

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○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.

○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+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

Link & Button Quality

1 issue(s) across 106 links and 1 buttons

PASS

1 issue(s) across 106 links and 1 buttons

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: input[type="submit"].submit-button (#134 on page)

106 link(s) with descriptive text

106 links

0 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
<input>	(empty)	empty	Add button text or aria-label

106 links and buttons have descriptive text

Icon-only buttons need an aria-label so screen readers can announce them.

input[type="submit"].submit-button (#134 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

7 icon(s) detected

PASS

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: WordReference

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name WordReference ✓192×192 icon ✓512×512 icon ✓Start URL /definition/?src=homescreen ✓Display Mode standalone ✓

Name WordReference Display Mode standalone Theme Color #ffffff Background Color #fff Icons 3 icon(s)

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)

Element	Ratio	Required	FG	BG	Result
h3 Spanish Dictionaries	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 French and Italian D…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Language Forums	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title English to French, I…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Language Forums	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Direct Links to Engl…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Spanish-English dict…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a French: Dictionnaire…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Italian: Dizionario …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Portuguese: Dicioná…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a German: Wörterbuch …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Dutch: Engels-Nederl…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Swedish: Engelsk-Sve…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Icelandic: Ensk-ísl…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Russian: Англо-…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Polish: Słownik ang…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Romanian: Dicţionar…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Czech: Anglicko-čes…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Greek: Αγγλοε�…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Turkish: İngilizce-…	21.00:1	4.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.