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 4 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

✓ favicon.ico Present

✓ PNG Icons Present

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

9 landmarks

REVIEW

9 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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.

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Alt Text Quality

Action

4 of 12 images have issues

REVIEW

4 of 12 images have issues

4 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 decorative image(s) correctly marked

6 image(s) with good alt text

12 images 6 good alt text 2 decorative 4 missing

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

Link & Button Quality

Action

6 issue(s) across 51 links and 1 buttons

REVIEW

6 issue(s) across 51 links and 1 buttons

6 link(s) with generic text

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

Got: https://www.studiopress.com/genesis-pro/ ("Read More"); https://my.studiopress.com/themes/genesis/ ("Learn More"); https://my.studiopress.com/themes/ ("Learn More"); https://www.studiopress.com/genesis-blocks/ ("Learn More"); https://www.studiopress.com/genesis-custom-blocks/ ("Learn More"); https://www.studiopress.com/genesis-pro/ ("Read More")

10 link(s) open in new tab without warning

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

Got: https://wpengine.com/?__hstc=82220873.983eb9d7c9fcfde5d57babfde8a5c472.177688…; https://getflywheel.com/; https://localwp.com/?__hstc=82220873.983eb9d7c9fcfde5d57babfde8a5c472.1776889…; https://www.advancedcustomfields.com/?__hstc=82220873.983eb9d7c9fcfde5d57babf…; https://nitropack.io/; https://deliciousbrains.com/?__hstc=82220873.983eb9d7c9fcfde5d57babfde8a5c472…; https://wpengine.com/wordpress-hosting/?__hstc=82220873.983eb9d7c9fcfde5d57ba…; https://wpengine.com/wordpress-hosting/?__hstc=82220873.983eb9d7c9fcfde5d57ba…; https://wpengine.com/legal/terms-of-service/?__hstc=82220873.983eb9d7c9fcfde5…; https://wpengine.com/legal/privacy/?__hstc=82220873.983eb9d7c9fcfde5d57babfde…

35 link(s) with descriptive text

51 links

0 empty

6 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wpengine.com/?__hstc=82220873.98…	WPEngine	new tab	Add '(opens in new tab)' to text
https://getflywheel.com/	Flywheel	new tab	Add '(opens in new tab)' to text
https://localwp.com/?__hstc=82220873.983…	Local	new tab	Add '(opens in new tab)' to text
https://www.advancedcustomfields.com/?__…	ACF	new tab	Add '(opens in new tab)' to text
https://nitropack.io/	Nitropack	new tab	Add '(opens in new tab)' to text
https://deliciousbrains.com/?__hstc=8222…	Delicious brains	new tab	Add '(opens in new tab)' to text
https://wpengine.com/wordpress-hosting/?…	WordPress Hosting	new tab	Add '(opens in new tab)' to text
https://www.studiopress.com/genesis-pro/	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Genesis Pro
https://my.studiopress.com/themes/genesi…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Genesis
https://my.studiopress.com/themes/	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Themes
https://www.studiopress.com/genesis-bloc…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Genesis Blocks
https://www.studiopress.com/genesis-cust…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Genesis Custom Blocks
https://www.studiopress.com/genesis-pro/	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Genesis Pro
https://wpengine.com/wordpress-hosting/?…	WordPress Hosting	new tab	Add '(opens in new tab)' to text
https://wpengine.com/legal/terms-of-serv…	Terms of Service	new tab	Add '(opens in new tab)' to text
https://wpengine.com/legal/privacy/?__hs…	Privacy Policy	new tab	Add '(opens in new tab)' to text

36 links and buttons have descriptive text

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

https://www.studiopress.com/genesis-pro/ ("Read More"); https://my.studiopress.com/themes/genesis/ ("Learn More"); https://my.studiopress.com/themes/ ("Learn More"); https://www.studiopress.com/genesis-blocks/ ("Learn More"); https://www.studiopress.com/genesis-custom-blocks/ ("Learn More"); https://www.studiopress.com/genesis-pro/ ("Read 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

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

https://wpengine.com/?__hstc=82220873.983eb9d7c9fcfde5d57babfde8a5c472.177688…; https://getflywheel.com/; https://localwp.com/?__hstc=82220873.983eb9d7c9fcfde5d57babfde8a5c472.1776889…; https://www.advancedcustomfields.com/?__hstc=82220873.983eb9d7c9fcfde5d57babf…; https://nitropack.io/; https://deliciousbrains.com/?__hstc=82220873.983eb9d7c9fcfde5d57babfde8a5c472…; https://wpengine.com/wordpress-hosting/?__hstc=82220873.983eb9d7c9fcfde5d57ba…; https://wpengine.com/wordpress-hosting/?__hstc=82220873.983eb9d7c9fcfde5d57ba…; https://wpengine.com/legal/terms-of-service/?__hstc=82220873.983eb9d7c9fcfde5…; https://wpengine.com/legal/privacy/?__hstc=82220873.983eb9d7c9fcfde5d57babfde…

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

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

Heading Hierarchy

16 headings, 1 skip(s)

PASS

16 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Build Better WordPress Websites,Faster with Genesis
H2 Genesis Pro
H2 Or choose the tool you need.
H3 Genesis Framework
H3 Genesis Themes
H3 Genesis Blocks
H3 Genesis Custom Blocks
H2 Why Genesis?
H2 What People Are Saying
H2 Genesis Pro
H2 Footer
H5 Products skipped
H5 Company
H5 Community
H5 Resources
H5 Connect

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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 Faster with Genesis	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Genesis Pro	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Or choose the tool y…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Genesis Pro	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Footer	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Genesis Framework	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Genesis Themes	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Genesis Blocks	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Genesis Custom Block…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title WordPress Themes by …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Premium WordPress Th…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Menu	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Genesis Pro	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Blocks	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Custom Blocks	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Framework	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Themes	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span WordPress Hosting	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Agencies	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.

Lighthouse Accessibility Audits

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

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
div.flexible-widgets > section#nav_menu-14 > div.widget-wrap > h5.widgettitle `div.flexible-widgets > section#nav_menu-14 > div.widget-wrap > h5.widgettitle`

These are opportunities to improve keyboard navigation in your application.

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
div.menu-products-menu-container > ul#menu-products-menu > li#menu-item-658023 > a `div.menu-products-menu-container > ul#menu-products-menu > li#menu-item-658023 > a`
div.menu-products-menu-container > ul#menu-products-menu > li#menu-item-658021 > a `div.menu-products-menu-container > ul#menu-products-menu > li#menu-item-658021 > a`
div.menu-products-menu-container > ul#menu-products-menu > li#menu-item-658022 > a `div.menu-products-menu-container > ul#menu-products-menu > li#menu-item-658022 > a`
div.menu-products-menu-container > ul#menu-products-menu > li#menu-item-658024 > a `div.menu-products-menu-container > ul#menu-products-menu > li#menu-item-658024 > a`
div.menu-products-menu-container > ul#menu-products-menu > li#menu-item-26473 > a `div.menu-products-menu-container > ul#menu-products-menu > li#menu-item-26473 > a`
div.menu-products-menu-container > ul#menu-products-menu > li#menu-item-658282 > a `div.menu-products-menu-container > ul#menu-products-menu > li#menu-item-658282 > a`
div.menu-products-menu-container > ul#menu-products-menu > li#menu-item-658194 > a `div.menu-products-menu-container > ul#menu-products-menu > li#menu-item-658194 > a`
div.menu-company-menu-container > ul#menu-company-menu > li#menu-item-26478 > a `div.menu-company-menu-container > ul#menu-company-menu > li#menu-item-26478 > a`
div.menu-company-menu-container > ul#menu-company-menu > li#menu-item-26479 > a `div.menu-company-menu-container > ul#menu-company-menu > li#menu-item-26479 > a`
div.menu-company-menu-container > ul#menu-company-menu > li#menu-item-26480 > a `div.menu-company-menu-container > ul#menu-company-menu > li#menu-item-26480 > a`
div.menu-company-menu-container > ul#menu-company-menu > li#menu-item-26481 > a `div.menu-company-menu-container > ul#menu-company-menu > li#menu-item-26481 > a`
div.menu-company-menu-container > ul#menu-company-menu > li#menu-item-26482 > a `div.menu-company-menu-container > ul#menu-company-menu > li#menu-item-26482 > a`
div.menu-community-menu-container > ul#menu-community-menu > li#menu-item-26483 > a `div.menu-community-menu-container > ul#menu-community-menu > li#menu-item-26483 > a`
div.menu-community-menu-container > ul#menu-community-menu > li#menu-item-26484 > a `div.menu-community-menu-container > ul#menu-community-menu > li#menu-item-26484 > a`
div.menu-community-menu-container > ul#menu-community-menu > li#menu-item-26485 > a `div.menu-community-menu-container > ul#menu-community-menu > li#menu-item-26485 > a`
div.menu-community-menu-container > ul#menu-community-menu > li#menu-item-26486 > a `div.menu-community-menu-container > ul#menu-community-menu > li#menu-item-26486 > a`
div.menu-community-menu-container > ul#menu-community-menu > li#menu-item-26487 > a `div.menu-community-menu-container > ul#menu-community-menu > li#menu-item-26487 > a`
div.menu-resources-menu-container > ul#menu-resources-menu > li#menu-item-26488 > a `div.menu-resources-menu-container > ul#menu-resources-menu > li#menu-item-26488 > a`
div.menu-resources-menu-container > ul#menu-resources-menu > li#menu-item-26489 > a `div.menu-resources-menu-container > ul#menu-resources-menu > li#menu-item-26489 > a`
div.menu-resources-menu-container > ul#menu-resources-menu > li#menu-item-26491 > a `div.menu-resources-menu-container > ul#menu-resources-menu > li#menu-item-26491 > a`
div.menu-resources-menu-container > ul#menu-resources-menu > li#menu-item-26490 > a `div.menu-resources-menu-container > ul#menu-resources-menu > li#menu-item-26490 > a`
div.menu-resources-menu-container > ul#menu-resources-menu > li#menu-item-26492 > a `div.menu-resources-menu-container > ul#menu-resources-menu > li#menu-item-26492 > a`
div.menu-connect-menu-container > ul#menu-connect-menu > li#menu-item-27197 > a `div.menu-connect-menu-container > ul#menu-connect-menu > li#menu-item-27197 > a`
div.menu-connect-menu-container > ul#menu-connect-menu > li#menu-item-26494 > a `div.menu-connect-menu-container > ul#menu-connect-menu > li#menu-item-26494 > a`
div.menu-connect-menu-container > ul#menu-connect-menu > li#menu-item-26495 > a `div.menu-connect-menu-container > ul#menu-connect-menu > li#menu-item-26495 > a`
div.menu-connect-menu-container > ul#menu-connect-menu > li#menu-item-26496 > a `div.menu-connect-menu-container > ul#menu-connect-menu > li#menu-item-26496 > a`

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-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

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

●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

●Document has a main landmark.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

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

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

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

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