Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

8 PASS 2 REVIEW 3 FIX

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass 3 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Meet WordPress	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 See what's new	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 One platform, a univ…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Meet the WordPress c…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Latest WordPress new…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
title Blog Tool, Publishin…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span News	5.02:1	4.5:1	#000000	#856EC3	Pass
span Showcase	5.02:1	4.5:1	#000000	#856EC3	Pass
span Hosting	5.02:1	4.5:1	#000000	#856EC3	Pass
span Extend	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Themes	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Plugins	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Patterns	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Blocks	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Openverse	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span ↗	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span ︎	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Learn	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Learn WordPress	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.

A+

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

10 headings

PASS

10 headings

Single H1 present

H1 Meet WordPress
H2 Design
H2 Build
H2 Extend
H2 See what's new
H2 One platform, a universe of possibilities
H2 Meet the WordPress community
H2 Build for yourself, not by yourself
H2 Latest WordPress news
H2 Get started

A+

Alt Text Quality

All 18 images OK

PASS

All 18 images OK

10 decorative image(s) correctly marked

8 image(s) with good alt text

18 images 8 good alt text 10 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#wp-block-search__input-3	search	Search in WordPress.org	for/id

Link & Button Quality

2 issue(s) across 80 links and 9 buttons

PASS

2 issue(s) across 80 links and 9 buttons

1 link(s) with no accessible text

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

Got: https://asia.wordcamp.org/2026/

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://asia.wordcamp.org/2026/ ("Learn more")

78 link(s) with descriptive text

80 links

1 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://asia.wordcamp.org/2026/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: 2026
https://asia.wordcamp.org/2026/	(empty)	empty	Add link text or aria-label

87 links and buttons have descriptive text

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

https://asia.wordcamp.org/2026/

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

Generic link text like 'click here' doesn't describe the destination.

https://asia.wordcamp.org/2026/ ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title WordPress.org ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: https://wordpress.org/wp-content/themes/wporg-parent-2021/build/print.css?ver=1748268724

Print Stylesheet ✓ Print Optimized

Print stylesheet https://wordpress.org/wp-content/themes/wporg-parent-2021/build/print.css?ver=1748268724 ✓Inline @media print Not detected ✗

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 24 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.

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
EVENTS `ul.is-3-column > li > div.wp-block-wporg-latest-news__details > a.wp-block-wporg-latest-news__category`

These are opportunities to improve the legibility of your content.

Names and labels

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.wp-block-group > div.wp-block-group > figure.wp-block-image > a `div.wp-block-group > div.wp-block-group > figure.wp-block-image > 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

●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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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

○Form elements have associated labels

○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

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

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

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