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

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.

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

1 issue(s) across 55 links and 1 buttons

REVIEW

1 issue(s) across 55 links and 1 buttons

1 link(s) with no accessible text

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

Got: https://www.youtube.com/embed/rweCxt37LYo?si=vNYGGYHQtpyIavwp&rel=0&autoplay=…

7 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.facebook.com/GeneratePress/; https://x.com/generatepress; https://wordpress.org/themes/generatepress/; //github.com/tomusborne/GeneratePress; https://youtube.com/c/GeneratePress; https://docs.generatepress.com/; https://translate.generatepress.com/

47 link(s) with descriptive text

55 links

1 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.youtube.com/embed/rweCxt37LY…	(empty)	empty	Add link text or aria-label
https://www.facebook.com/GeneratePress/	Facebook	new tab	Add '(opens in new tab)' to text
https://x.com/generatepress	Twitter	new tab	Add '(opens in new tab)' to text
https://wordpress.org/themes/generatepre…	WordPress	new tab	Add '(opens in new tab)' to text
//github.com/tomusborne/GeneratePress	GitHub	new tab	Add '(opens in new tab)' to text
https://youtube.com/c/GeneratePress	YouTube	new tab	Add '(opens in new tab)' to text
https://docs.generatepress.com/	Documentation	new tab	Add '(opens in new tab)' to text
https://translate.generatepress.com/	Translate	new tab	Add '(opens in new tab)' to text

48 links and buttons have descriptive text

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

https://www.youtube.com/embed/rweCxt37LYo?si=vNYGGYHQtpyIavwp&rel=0&autoplay=…

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

Add '(opens in new tab)' to link text or aria-label.

https://www.facebook.com/GeneratePress/; https://x.com/generatepress; https://wordpress.org/themes/generatepress/; //github.com/tomusborne/GeneratePress; https://youtube.com/c/GeneratePress; https://docs.generatepress.com/; https://translate.generatepress.com/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

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)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Build your perfect WordPress website.

1.28:1

#000000

#1C1F2C

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Start your website today.

1.28:1

#000000

#1C1F2C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Built to outperform the competition.

1.28:1

#000000

#1C1F2C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kickstart your next website.

1.28:1

#000000

#1C1F2C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Our users love us.

1.28:1

#000000

#1C1F2C

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Start building better websites today.

1.28:1

#000000

#1C1F2C

needs 3.0:1 (large text)

19px · bottom of viewport

title GeneratePress - The perfect foundation f…

1.14:1

#000000

#101322

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.24:1

#000000

#191C2A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Pricing

1.15:1

#000000

#111422

needs 4.5:1 (normal text)

16px · top of page (header area)

a Products

1.24:1

#000000

#191C2A

needs 4.5:1 (normal text)

16px · top of page (header area)

strong GeneratePress

1.25:1

#000000

#1A1D2A

needs 3.0:1 (large text)

16px · above the fold

mark One

1.16:1

#000000

#121523

needs 4.5:1 (normal text)

16px · above the fold

p All of our powerful WordPress tools in o…

1.25:1

#000000

#1A1D2A

needs 4.5:1 (normal text)

16px · above the fold

strong Theme

1.15:1

#000000

#111422

needs 3.0:1 (large text)

16px · above the fold

p A lightweight foundation to base your we…

1.24:1

#000000

#191C2A

needs 4.5:1 (normal text)

16px · above the fold

strong Blocks

1.21:1

#000000

#171A28

needs 3.0:1 (large text)

16px · above the fold

p A powerful page builder to build your we…

1.17:1

#000000

#141625

needs 4.5:1 (normal text)

16px · above the fold

strong Cloud

1.25:1

#000000

#1A1D2A

needs 3.0:1 (large text)

16px · above the fold

p Host your very own Pattern Library cloud…

1.15:1

#000000

#111422

needs 4.5:1 (normal text)

16px · above the fold

a One

1.24:1

#000000

#191C2A

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Build your perfect W…	1.28:1	3.0:1	#000000	#1C1F2C	Fail
h2 Start your website t…	1.28:1	3.0:1	#000000	#1C1F2C	Fail
h2 Built to outperform …	1.28:1	3.0:1	#000000	#1C1F2C	Fail
h2 Kickstart your next …	1.28:1	3.0:1	#000000	#1C1F2C	Fail
h2 Our users love us.	1.28:1	3.0:1	#000000	#1C1F2C	Fail
h3 Start building bette…	1.28:1	3.0:1	#000000	#1C1F2C	Fail
title GeneratePress - The …	1.14:1	4.5:1	#000000	#101322	Fail
a Skip to content	1.24:1	4.5:1	#000000	#191C2A	Fail
a Pricing	1.15:1	4.5:1	#000000	#111422	Fail
a Products	1.24:1	4.5:1	#000000	#191C2A	Fail
strong GeneratePress	1.25:1	3.0:1	#000000	#1A1D2A	Fail
mark One	1.16:1	4.5:1	#000000	#121523	Fail
p All of our powerful …	1.25:1	4.5:1	#000000	#1A1D2A	Fail
strong Theme	1.15:1	3.0:1	#000000	#111422	Fail
p A lightweight founda…	1.24:1	4.5:1	#000000	#191C2A	Fail
strong Blocks	1.21:1	3.0:1	#000000	#171A28	Fail
p A powerful page buil…	1.17:1	4.5:1	#000000	#141625	Fail
strong Cloud	1.25:1	3.0:1	#000000	#1A1D2A	Fail
p Host your very own P…	1.15:1	4.5:1	#000000	#111422	Fail
a One	1.24:1	4.5:1	#000000	#191C2A	Fail

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

3 landmarks

PASS

3 landmarks

<main> landmark present

1 <nav> landmark(s) found

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

12 headings

PASS

12 headings

Single H1 present

H1 Build your perfect WordPress website.
H2 Start your website today.
H2 Built to outperform the competition.
H3 Performance
H3 Accessible
H3 World-Class Support
H3 Stable
H3 Coding Standards
H3 Risk-Free Purchase
H2 Kickstart your next website.
H2 Our users love us.
H3 Start building better websites today.

A+

Alt Text Quality

All 16 images OK

PASS

All 16 images OK

8 decorative image(s) correctly marked

8 image(s) with good alt text

16 images 8 good alt text 8 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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 Page not found - GeneratePress ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 26 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

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.gps-main-section__inner > div > div.gb-element-79491b5e > a.gb-text-8766aab3 `div.gps-main-section__inner > div > div.gb-element-79491b5e > a.gb-text-8766aab3`

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

●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

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

●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

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

○Identical links have the same purpose.

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