Accessibility

D

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.

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #000000

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 ModePartial Dark Mode

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

Detection limited to meta tags and inline styles.

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

1 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 1 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

B

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

C

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 Home

1.00:1

#000000

on

#000000

needs 3.0:1 (large text)

32px · above the fold

title Home.blog – Appalachia + AGI + Automat…

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Home.blog

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

p Appalachia + AGI + Automattic

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

button Menu

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Home.blog

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a About A3

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Michael Bierut

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Blog

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a AGI

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Paintsville High

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Automattic

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · above the fold

p Artwork by

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · mid-page

a Michael Bierut

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · mid-page

p Site by

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · mid-page

a Kjell Reigstad

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · mid-page

a Create Your . Home . Blog

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · mid-page

a Support

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · mid-page

a Blog at WordPress.com.

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Home	1.00:1	3.0:1	#000000	#000000	Fail
title Home.blog – Appala…	1.00:1	4.5:1	#000000	#000000	Fail
a Skip to content	1.00:1	4.5:1	#000000	#000000	Fail
a Home.blog	1.00:1	4.5:1	#000000	#000000	Fail
p Appalachia + AGI + A…	1.00:1	4.5:1	#000000	#000000	Fail
button Menu	1.00:1	4.5:1	#000000	#000000	Fail
a Home.blog	1.00:1	4.5:1	#000000	#000000	Fail
a About A3	1.00:1	4.5:1	#000000	#000000	Fail
a Michael Bierut	1.00:1	4.5:1	#000000	#000000	Fail
a Blog	1.00:1	4.5:1	#000000	#000000	Fail
a AGI	1.00:1	4.5:1	#000000	#000000	Fail
a Paintsville High	1.00:1	4.5:1	#000000	#000000	Fail
a Automattic	1.00:1	4.5:1	#000000	#000000	Fail
p Artwork by	1.00:1	4.5:1	#000000	#000000	Fail
a Michael Bierut	1.00:1	4.5:1	#000000	#000000	Fail
p Site by	1.00:1	4.5:1	#000000	#000000	Fail
a Kjell Reigstad	1.00:1	4.5:1	#000000	#000000	Fail
a Create Your . Home .…	1.00:1	4.5:1	#000000	#000000	Fail
a Support	1.00:1	4.5:1	#000000	#000000	Fail
a Blog at WordPress.co…	1.00:1	4.5:1	#000000	#000000	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

8 landmarks

PASS

8 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 Home

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

2 decorative image(s) correctly marked

1 image(s) with good alt text

3 images 1 good alt text 2 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.

A

Link & Button Quality

21 links, 1 buttons — all OK

PASS

21 links, 1 buttons — all OK

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://home.blog"]

1 link(s) open in new tab without warning

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

Got: https://wordpress.com/abuse/?report_url=https://home.blog/

19 link(s) with descriptive text

21 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://home.blog	Home.blog	img no alt	Add alt attribute to the image
https://wordpress.com/abuse/?report_url=…	Report this content	new tab	Add '(opens in new tab)' to text

20 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://home.blog"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://wordpress.com/abuse/?report_url=https://home.blog/

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

A

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 – Home.blog ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /wp-content/mu-plugins/global-print/global-print.css?m=1465851035i&cssminify=yes

Print Stylesheet ✓ Print Optimized

Print stylesheet /wp-content/mu-plugins/global-print/global-print.css?m=1465851035i&cssminify=yes ✓Inline @media print Not detected ✗

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 22 passed

PASS

100

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.

○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

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

●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-hidden="true"]` elements do not contain focusable descendents

○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

○Heading elements appear in a sequentially-descending order

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

○Links are distinguishable without relying on color.

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