Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 5 REVIEW 4 FIX

Alt Text Quality

Action

7 of 33 images have issues

FIX

7 of 33 images have issues

7 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

4 image-in-link without alt text

An image inside a link with no alt creates an empty link.

9 decorative image(s) correctly marked

17 image(s) with good alt text

33 images 17 good alt text 9 decorative 7 missing

Issue	Count
missing	7 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

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 ✗

Link & Button Quality

11 issue(s) across 294 links and 10 buttons

REVIEW

11 issue(s) across 294 links and 10 buttons

11 link(s) with no accessible text

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

Got: /wiki/Plik:P2N2019ClaraLuciani_06.jpg; /wiki/Plik:HMS_Roberts_NARA-45513189.jpg; /wiki/Plik:William_Tolbert_(cropped).jpg; /wiki/Plik:Ratusz_w_%C5%81%C4%99czycy.jpg; #; #; #; #; #; # (+1 more)

283 link(s) with descriptive text

294 links

11 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/wiki/Plik:P2N2019ClaraLuciani_06.jpg	(empty)	empty	Add link text or aria-label
/wiki/Plik:HMS_Roberts_NARA-45513189.jpg	(empty)	empty	Add link text or aria-label
/wiki/Plik:William_Tolbert_(cropped).jpg	(empty)	empty	Add link text or aria-label
/wiki/Plik:Ratusz_w_%C5%81%C4%99czycy.jp…	(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
#	(empty)	empty	Add link text or aria-label

293 links and buttons have descriptive text

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

/wiki/Plik:P2N2019ClaraLuciani_06.jpg; /wiki/Plik:HMS_Roberts_NARA-45513189.jpg; /wiki/Plik:William_Tolbert_(cropped).jpg; /wiki/Plik:Ratusz_w_%C5%81%C4%99czycy.jpg; #; #; #; #; #; # (+1 more)

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 ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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.

Lighthouse Accessibility Audits

Score 86/100 — 3 failing, 25 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.

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
div#main-page-didyouknow > figure.mw-halign-right > a.mw-file-description > img.mw-file-element `div#main-page-didyouknow > figure.mw-halign-right > a.mw-file-description > img.mw-file-element`
div#main-page-featured-article > figure.mw-halign-right > a.mw-file-description > img.mw-file-element `div#main-page-featured-article > figure.mw-halign-right > a.mw-file-description > img.mw-file-element`
div#main-page-good-article > figure.mw-halign-right > a.mw-file-description > img.mw-file-element `div#main-page-good-article > figure.mw-halign-right > a.mw-file-description > img.mw-file-element`
div > span > a.mw-file-description > img.mw-file-element `div > span > a.mw-file-description > 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`

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#main-page-column1 > div#main-page-didyouknow > figure.mw-halign-right > a.mw-file-description `div#main-page-column1 > div#main-page-didyouknow > figure.mw-halign-right > a.mw-file-description`
div#main-page-column2 > div#main-page-featured-article > figure.mw-halign-right > a.mw-file-description `div#main-page-column2 > div#main-page-featured-article > figure.mw-halign-right > a.mw-file-description`
div#main-page-column2 > div#main-page-good-article > figure.mw-halign-right > a.mw-file-description `div#main-page-column2 > div#main-page-good-article > figure.mw-halign-right > a.mw-file-description`
div#main-page-featured-image > div > span > a.mw-file-description `div#main-page-featured-image > div > span > a.mw-file-description`

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

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

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

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

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

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

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

Landmark Structure

17 landmarks

PASS

17 landmarks

<main> landmark present

9 <nav> landmark(s) found

All <nav> elements are properly labeled

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.

Search landmark present

Page Structure — as a screen reader sees it

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

A+

Heading Hierarchy

2 headings

PASS

2 headings

Single H1 present

H1 Wikipedia:Strona główna
H2 Wstęp

Form Accessibility

1 of 17 controls have issues

PASS

1 of 17 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">

16 control(s) properly labeled

17 controls

16 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#vector-main-menu-dropdown-checkbox	checkbox	Menu główne	aria-label
#searchInput	search	Przeszukaj Wikipedię	aria-label
#vector-appearance-dropdown-checkbox	checkbox	Wygląd	aria-label
#skin-client-pref-vector-feature-custom-font-size-value-0	radio	Mały	for/id
#skin-client-pref-vector-feature-custom-font-size-value-1	radio	Normalny	for/id
#skin-client-pref-vector-feature-custom-font-size-value-2	radio	Duży	for/id
#skin-client-pref-vector-feature-limited-width-value-1	radio	Normalna	for/id
#skin-client-pref-vector-feature-limited-width-value-0	radio	Duża	for/id
#skin-client-pref-skin-theme-value-os	radio	Automatyczny	for/id
#skin-client-pref-skin-theme-value-day	radio	Jasny	for/id
#skin-client-pref-skin-theme-value-night	radio	Ciemny	for/id
#vector-user-links-dropdown-checkbox	checkbox	Narzędzia osobiste	aria-label
#p-lang-btn-checkbox	checkbox	Przejdź do artykułu w innym języku. Treść dostępna w 60 językach	aria-label
#vector-variants-dropdown-checkbox	checkbox	Zmień wariant języka	aria-label
#vector-page-tools-dropdown-checkbox	checkbox	Narzędzia	aria-label
input	checkbox		none
search	search	(Przeszukaj Wikipedię)	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 Wstęp	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Wikipedia, wolna enc…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Przejdź do zawarto�…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Menu główne	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Menu główne	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button przypnij	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button ukryj	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Nawigacja	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Strona główna	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Losuj artykuł	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Kategorie artykułó…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Najlepsze artykuły	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Częste pytania (FAQ…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Dla czytelników	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span O Wikipedii	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Kontakt	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Dla wikipedystów	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Pierwsze kroki	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Portal wikipedystów	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Ogłoszenia	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.