Skip to content
https://en.wiktionary.org

Accessibility

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

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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
9 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 9 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Form Accessibility
Action
3 of 18 controls have issues
REVIEW
3 of 18 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input name="search" id="bodySearchInput0.697020182758">; <input type="submit" name="go">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="search">
Info::
15 control(s) properly labeled
18 controls
15 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#vector-main-menu-dropdown-checkboxcheckboxMain menuaria-label
#searchInputsearchSearch Wiktionaryaria-label
#vector-appearance-dropdown-checkboxcheckboxAppearancearia-label
#skin-client-pref-vector-feature-custom-font-size-value-0radioSmallfor/id
#skin-client-pref-vector-feature-custom-font-size-value-1radioStandardfor/id
#skin-client-pref-vector-feature-custom-font-size-value-2radioLargefor/id
#skin-client-pref-vector-feature-limited-width-value-1radioStandardfor/id
#skin-client-pref-vector-feature-limited-width-value-0radioWidefor/id
#skin-client-pref-skin-theme-value-osradioAutomaticfor/id
#skin-client-pref-skin-theme-value-dayradioLightfor/id
#skin-client-pref-skin-theme-value-nightradioDarkfor/id
#vector-user-links-dropdown-checkboxcheckboxPersonal toolsaria-label
#vector-variants-dropdown-checkboxcheckboxChange language variantaria-label
#vector-page-tools-dropdown-checkboxcheckboxToolsaria-label
#p-lang-btn-checkboxcheckboxGo to an article in another language. Available in 181 languagesaria-label
searchsearch(Search Wiktionary)placeholder only
#bodySearchInput0.697020182758input(none)none
gosubmit(none)none

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

<input name="search" id="bodySearchInput0.697020182758">; <input type="submit" name="go">

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="search">

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

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 Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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.

B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 27 passed
REVIEW
82

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
9,950,380 td > p > b > a
4,600 p > span > b > a
All languages tr > td > p > a
List of topics tr > td > p > a
Random word tr > td > p > a
New entries tr > td > p > a
Appendices tr > td > p > a
Thesaurus tr > td > p > a
Rhymes tr > td > p > a
Frequency lists tr > td > p > a
Phrasebooks tr > td > p > a

These are opportunities to improve the legibility of your content.

Tables and lists

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
A page containing everything you wanted to know about Wiktionary. tbody > tr > td > dl
A page containing everything you wanted to know about Wiktionary. td > dl > dd > dl
A collection of pages for the discussion of Wiktionary and the words it contain… tbody > tr > td > dl
A collection of pages for the discussion of Wiktionary and the words it contain… td > dl > dd > dl

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

Names and labels

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
span > span > a > img.mw-file-element span > span > a > img.mw-file-element
p > span > a.mw-file-description > img.mw-file-element p > span > a.mw-file-description > img.mw-file-element
span > span.skin-invert-image > a > img.mw-file-element span > span.skin-invert-image > a > img.mw-file-element
div#FWOTD-rss-description > span > a.mw-file-description > img.mw-file-element div#FWOTD-rss-description > span > a.mw-file-description > img.mw-file-element
span > span > a > img.mw-file-element span > span > a > img.mw-file-element
span > span > a > img.mw-file-element span > span > a > img.mw-file-element

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header.header-container > div.minerva-header > nav.navigation-drawer > input#main-menu-input header.header-container > div.minerva-header > nav.navigation-drawer > input#main-menu-input
form#bodySearch0.697020182758 > div.bodySearchWrap > div.cdx-text-input > input#bodySearchInput0.697020182758 form#bodySearch0.697020182758 > div.bodySearchWrap > div.cdx-text-input > input#bodySearchInput0.697020182758

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#WOTD-rss-description > p > span > a.mw-file-description div#WOTD-rss-description > p > span > a.mw-file-description
td > div#FWOTD-rss-description > span > a.mw-file-description td > div#FWOTD-rss-description > span > a.mw-file-description
div.main-page-list-of-wiktionaries > span > span > a div.main-page-list-of-wiktionaries > span > span > 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.

○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
●Input buttons have discernible text.
●`[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
●Definition list items are wrapped in `<dl>` elements
●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
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`[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
●Uses ARIA roles only on compatible elements
●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 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
○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 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.
○No element has a `[tabindex]` value greater than 0
○`<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.
○Image elements do not have `[alt]` attributes that are redundant text.
○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
15 landmarks
PASS
15 landmarks
Info::
<main> landmark present
Info::
9 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Site" SEARCH MAIN CONTENTINFO footer
A
Heading Hierarchy
3 headings, 1 skip(s)
PASS
3 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Wiktionary:Main Page
  • H3 Wiktionaries in other languages skipped
  • H3 Other Wikimedia projects

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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
h3 Wiktionaries in othe…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Other Wikimedia proj…21.00:13.0:1
#000000
#FFFFFF
Pass
title Wiktionary, the free…21.00:14.5:1
#000000
#FFFFFF
Pass
a Jump to content21.00:14.5:1
#000000
#FFFFFF
Pass
span Main menu21.00:14.5:1
#000000
#FFFFFF
Pass
div Main menu21.00:14.5:1
#000000
#FFFFFF
Pass
button move to sidebar21.00:14.5:1
#000000
#FFFFFF
Pass
button hide21.00:14.5:1
#000000
#FFFFFF
Pass
div Navigation21.00:14.5:1
#000000
#FFFFFF
Pass
span Main page21.00:14.5:1
#000000
#FFFFFF
Pass
span Community portal21.00:14.5:1
#000000
#FFFFFF
Pass
span Requested entries21.00:14.5:1
#000000
#FFFFFF
Pass
span Recent changes21.00:14.5:1
#000000
#FFFFFF
Pass
span Random entry21.00:14.5:1
#000000
#FFFFFF
Pass
span Help21.00:14.5:1
#000000
#FFFFFF
Pass
span Glossary21.00:14.5:1
#000000
#FFFFFF
Pass
span Contact us21.00:14.5:1
#000000
#FFFFFF
Pass
span Special pages21.00:14.5:1
#000000
#FFFFFF
Pass
div Feedback21.00:14.5:1
#000000
#FFFFFF
Pass
a If you have time, le…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.

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

Send Feedback