Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

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

71 links, 8 buttons — all OK

REVIEW

71 links, 8 buttons — all OK

2 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://akismet.com"]; a[href="https://akismet.com"]

2 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://akismet.com/; https://jetpack.com/upgrade/search/?utm_source=poweredby

67 link(s) with descriptive text

71 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://akismet.com	Akismet	img no alt	Add alt attribute to the image
https://akismet.com	Akismet	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
https://jetpack.com/upgrade/search/?utm_…	Search powered by Jetpack	new tab	Add '(opens in new tab)' to text

75 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://akismet.com"]; a[href="https://akismet.com"]

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://akismet.com/; https://jetpack.com/upgrade/search/?utm_source=poweredby

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

A+

Landmark Structure

10 landmarks

PASS

10 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

Heading Hierarchy

22 headings

PASS

22 headings

Multiple H1 headings (4 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 Spam shall not pass.
H1 The whole can of spam. duplicate H1
H1 Like a machine.With intelligence. duplicate H1
H2 Never waste time on spam again.
H3 20 hours per month
H2 Never lose money on spam attacks again.
H3 3.6% of annual revenue
H2 Bring in more leads, sales, and revenue.
H3 +3.2%
H2 Sleep well,security team.
H3 99.99%
H4 Your whole team.
H2 An API so flexible it’s basically double-jointed.
H2 Try Akismet today.
H2 Product
H2 Resources
H2 Developers
H2 Legal
H2 Language
H1 Search results duplicate H1
H2 No results found
H2 Filter options

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

All 31 images OK

PASS

All 31 images OK

26 decorative image(s) correctly marked

5 image(s) with good alt text

31 images 5 good alt text 26 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
email	email	Enter your email address	aria-label
#jetpack-instant-search__box-input-1	search	Magnifying Glass	none

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

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 Spam shall	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h1 not pass.	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h1 The whole	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h1 Like a	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h1 With	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h1 Search results	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 Never waste time on …	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 Never lose money on …	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 Bring in more leads,…	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 Sleep well,	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 security team.	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 it’s basically dou…	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 Try Akismet today.	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 Product	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 Resources	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 Developers	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 Legal	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 Language	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 No results found	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 Filter options	19.60:1	3.0:1	#000000	#F7F7F7	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+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 23 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.

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
Press `div.copy-right > div.sub-container > div.cell > a.work-with-us`

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

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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

○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

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