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

6 of 17 images have issues

FIX

6 of 17 images have issues

6 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image-in-link without alt text

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

1 decorative image(s) correctly marked

10 image(s) with good alt text

17 images 10 good alt text 1 decorative 6 missing

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

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

8 issue(s) across 197 links and 9 buttons

REVIEW

8 issue(s) across 197 links and 9 buttons

8 link(s) with no accessible text

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

Got: //www.mediawiki.org/wiki/File:Wikimedia_Hackathon_2025_Group_photo_from_drone…; #; #; #; #; #; #; #

189 link(s) with descriptive text

197 links

8 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
//www.mediawiki.org/wiki/File:Wikimedia_…	(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

198 links and buttons have descriptive text

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

//www.mediawiki.org/wiki/File:Wikimedia_Hackathon_2025_Group_photo_from_drone…; #; #; #; #; #; #; #

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 87/100 — 4 failing, 26 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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Photo of participants of the Wikimedia Hackathon 2025 `div.mw-content-ltr > section#mf-section-0 > div#lang_dir > div`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Set up and run MediaWiki `div#audiences > div.mainpage_box > div.mw-heading > h3#Set_up_and_run_MediaWiki`

These are opportunities to improve keyboard navigation in your application.

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Wikimedia Hackathon 2025 `div > figure.mw-halign-right > figcaption > a`

These are opportunities to improve the legibility of your content.

○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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

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

●`[lang]` attributes have a valid value

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

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 MediaWiki is a collaboration and documentation platform brought to you by a vibrant community.
H2 MediaWiki is a collaboration and documentation platform brought to you by a vibrant community.
H3 Set up and run MediaWiki
H3 Edit and use MediaWiki
H3 Develop and extend code
H3 Get help and contribute
H3 News

Form Accessibility

1 of 15 controls have issues

PASS

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

14 control(s) properly labeled

15 controls

14 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#vector-main-menu-dropdown-checkbox	checkbox	Main menu	aria-label
#searchInput	search	Search mediawiki.org	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
search	search	(Search mediawiki.org)	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
h1 MediaWiki is a colla…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 MediaWiki is a colla…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title MediaWiki	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 Get MediaWiki	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Get extensions	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Tech blog	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Contribute	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Support	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span User help	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span FAQ	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Technical manual	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Support desk	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Communication	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.