Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 3 REVIEW 4 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

Web Manifest

Action

Not found

FIX

Not found

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.

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 ✗

Navigation UX

Action

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

9 navigation landmark(s) detected

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 9 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Link & Button Quality

7 issue(s) across 564 links and 10 buttons

REVIEW

7 issue(s) across 564 links and 10 buttons

7 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: #; #; #; #; #; #; #

557 link(s) with descriptive text

564 links

7 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label

567 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

#; #; #; #; #; #; #

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

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 ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Landmark Structure

15 landmarks

PASS

15 landmarks

<main> landmark present

9 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

7 headings

PASS

7 headings

Single H1 present

H1 Main Page
H2 100,000 +
H2 10,000 +
H2 1,000 +
H2 100 +
H2 < 100
H2 All languages at Wikisource

A+

Alt Text Quality

All 20 images OK

PASS

All 20 images OK

1 decorative image(s) correctly marked

19 image(s) with good alt text

20 images 19 good alt text 1 decorative

All images have appropriate alt text.

Form Accessibility

1 of 16 controls have issues

PASS

1 of 16 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="search" name="search">

15 control(s) properly labeled

16 controls

15 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#vector-main-menu-dropdown-checkbox	checkbox	Main menu	aria-label
#searchInput	search	Search Wikisource	aria-label
#vector-appearance-dropdown-checkbox	checkbox	Appearance	aria-label
#skin-client-pref-vector-feature-custom-font-size-value-0	radio	Small	for/id
#skin-client-pref-vector-feature-custom-font-size-value-1	radio	Standard	for/id
#skin-client-pref-vector-feature-custom-font-size-value-2	radio	Large	for/id
#skin-client-pref-vector-feature-limited-width-value-1	radio	Standard	for/id
#skin-client-pref-vector-feature-limited-width-value-0	radio	Wide	for/id
#skin-client-pref-skin-theme-value-os	radio	Automatic	for/id
#skin-client-pref-skin-theme-value-day	radio	Light	for/id
#skin-client-pref-skin-theme-value-night	radio	Dark	for/id
#vector-user-links-dropdown-checkbox	checkbox	Personal tools	aria-label
#vector-variants-dropdown-checkbox	checkbox	Change language variant	aria-label
#vector-page-tools-dropdown-checkbox	checkbox	Tools	aria-label
#p-lang-btn-checkbox	checkbox	Go to an article in another language. Available in 82 languages	aria-label
search	search	(Search Wikisource)	placeholder only

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

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

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
h2 100,000 +	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 10,000 +	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 1,000 +	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 100 +	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 < 100	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Wikisource	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Jump to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Main menu	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Main menu	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button move to sidebar	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button hide	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Navigation	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Main Page	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Scriptorium	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span News	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Recent changes	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Random page	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Random book	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Help	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Search	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.

Lighthouse Accessibility Audits

Score 92/100 — 3 failing, 28 passed

PASS

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

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`

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.

Internationalization and localization

Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Reo Tahiti `p > span.nowrap > a > span`

These are opportunities to improve the interpretation of your content by users in different locales.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Wiktionary Wikiquote Wikibooks Wikispecies Wikipedia Wikiversity Wikivoy… `section#mf-section-0 > div > div.center > table.plainlinks`

○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

●Image elements have `[alt]` attributes

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

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

●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

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

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

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

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

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

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

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