https://stationery.wiki/Stationery_Wiki:Mechanical_Pencil_Day_Contest

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 5 REVIEW 5 FIX

Alt Text Quality

Action

6 of 9 images have issues

FIX

6 of 9 images have issues

6 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

6 image-in-link without alt text

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

3 image(s) with good alt text

9 images 3 good alt text 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

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ PNG Icons Missing

✗ 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

11 navigation landmark(s) detected

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 11 <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

6 issue(s) across 95 links and 9 buttons

REVIEW

6 issue(s) across 95 links and 9 buttons

6 link(s) with no accessible text

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

Got: /File:Flag_of_Romania.svg; /File:Flag_of_Italy.svg; /File:Flag_of_the_United_States_(Pantone).svg; /File:Flag_of_New_Zealand.svg; /File:Flag_of_the_United_States_(Pantone).svg; /File:Flag_of_the_United_States_(Pantone).svg

89 link(s) with descriptive text

95 links

6 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/File:Flag_of_Romania.svg	(empty)	empty	Add link text or aria-label
/File:Flag_of_Italy.svg	(empty)	empty	Add link text or aria-label
/File:Flag_of_the_United_States_(Pantone…	(empty)	empty	Add link text or aria-label
/File:Flag_of_New_Zealand.svg	(empty)	empty	Add link text or aria-label
/File:Flag_of_the_United_States_(Pantone…	(empty)	empty	Add link text or aria-label
/File:Flag_of_the_United_States_(Pantone…	(empty)	empty	Add link text or aria-label

98 links and buttons have descriptive text

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

/File:Flag_of_Romania.svg; /File:Flag_of_Italy.svg; /File:Flag_of_the_United_States_(Pantone).svg; /File:Flag_of_New_Zealand.svg; /File:Flag_of_the_United_States_(Pantone).svg; /File:Flag_of_the_United_States_(Pantone).svg

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

Tap Target Adequacy

2 tap target(s) too small or too close together

REVIEW

2 tap target(s) too small or too close together

2 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Beavercheck-404-test-e96h58 - Stationery Wiki ✓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.

Lighthouse Accessibility Audits

Score 84/100 — 4 failing, 29 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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
(Redirected from Stationery Wiki:Mechanical Pencil Day Contest) The Mechanical… `div.mw-page-container-inner > div.mw-content-container > main#content > div#bodyContent`
main#content > div#bodyContent > div.vector-body-before-content > div.mw-indicators `main#content > div#bodyContent > div.vector-body-before-content > div.mw-indicators`

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.

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
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`
td > span > a.mw-file-description > img.mw-file-element `td > span > a.mw-file-description > img.mw-file-element`

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
tr > td > span > a.mw-file-description `tr > td > span > a.mw-file-description`
tr > td > span > a.mw-file-description `tr > td > span > a.mw-file-description`
tr > td > span > a.mw-file-description `tr > td > span > a.mw-file-description`
tr > td > span > a.mw-file-description `tr > td > span > a.mw-file-description`
tr > td > span > a.mw-file-description `tr > td > span > a.mw-file-description`
tr > td > span > a.mw-file-description `tr > td > 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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Dish `div.mw-content-ltr > ol > li > a`
Rares `div.mw-content-ltr > ol > li > a.mw-redirect`

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

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`[accesskey]` values are unique

●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

●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

●Skip links are focusable.

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

●`<td>` elements in a large `<table>` have one or more table headers.

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

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

Landmark Structure

16 landmarks

PASS

16 landmarks

<main> landmark present

11 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Skip link target(s) don't exist on page: #bodyContent

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Search landmark present

Page Structure — as a screen reader sees it

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Hierarchy

9 headings

PASS

9 headings

Single H1 present

H2 Contents
H1 Stationery Wiki:Mechanical Pencil Day Contest 2018
H2 The Judges[edit]
H2 How to participate[edit]
H2 Who can participate[edit]
H2 Participants[edit]
H2 What you can win[edit]
H2 There's More[edit]
H2 Winners[edit]

A+

Heading Text Quality

All 9 heading(s) have substantive, well-formed text

PASS

All 9 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Form Accessibility

All 12 controls labeled

PASS

All 12 controls labeled

12 control(s) properly labeled

12 controls

12 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#vector-main-menu-dropdown-checkbox	checkbox	Main menu	aria-label
#searchInput	search	Search Stationery Wiki	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
#vector-user-links-dropdown-checkbox	checkbox	Personal tools	aria-label
#vector-page-titlebar-toc-checkbox	checkbox	Toggle the table of contents	aria-label
#vector-variants-dropdown-checkbox	checkbox	Change language variant	aria-label
#vector-page-tools-dropdown-checkbox	checkbox	Tools	aria-label

A+

Form Input Types

12 form control(s) checked, no type mismatches

PASS

12 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

12 form control(s) checked, no input-semantic issues

PASS

12 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en-GB"

PASS

Lang attribute set to "en-GB"

<html lang="en-GB"> is set and valid

Got: en-GB

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Mobile-Readable Font Sizes

All 109 visible text node(s) render at >= 12 CSS pixels

PASS

All 109 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

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 Contents	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Stationery Wiki:Mech…	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 Recent changes	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Random page	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Help using our Wiki	21.00:1	4.5:1	#000000	#FFFFFF	Pass
strong Stationery Wiki	21.00:1	3.0:1	#000000	#FFFFFF	Pass
span Search	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Search	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Appearance	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Appearance	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 Text	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.