Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 6 REVIEW 6 FIX

Landmark Structure

Action

22 landmarks

FIX

22 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

14 <nav> landmark(s) found

1 of 14 <nav> elements are unlabeled

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

No contentinfo (footer) landmark

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Form Accessibility

Action

4 of 8 controls have issues

FIX

4 of 8 controls have issues

2 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit">; <input type="submit">

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="email" name="email-2">; <input type="email" name="Email" id="Email">

4 control(s) properly labeled

8 controls

4 labeled

2 placeholder only

2 unlabeled

Control	Type	Label	Method
#necessaryCheckbox	checkbox	Necessary (always active)	for/id
#functionalCheckbox	checkbox	Functional	for/id
#marketingCheckbox	checkbox	Marketing	for/id
#analyticalCheckbox	checkbox	Analytical	for/id
email-2	email	(Enter your email)	placeholder only
#Email	email	(Enter your email)	placeholder only
input	submit	(none)	none
input	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

Action

5 issue(s) across 151 links and 16 buttons

FIX

5 issue(s) across 151 links and 16 buttons

4 link(s) with no accessible text

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

Got: /home/demo; https://www.g2.com/products/zeffy/reviews?utf8=✓&order=highest_rated; https://www.capterra.ca/reviews/220131/zeffy#facets; /

11 link(s) open in new tab without warning

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

Got: https://zeffy.com/login?; https://zeffy.com/login?; https://www.facebook.com/zeffyplatform; https://www.instagram.com/zeffyplatform/?hl=fr; https://www.linkedin.com/company/zeffy/; https://feedback.zeffy.com/; https://www.notion.so/zeffy/Brand-Assets-Public-b26b27c966ea4067a2c96238cd4694d8; https://support.zeffy.com/; https://feedback.zeffy.com/feature-requests; https://community.zeffy.com/ (+1 more)

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button#consent-close-button

136 link(s) with descriptive text

151 links

4 empty

0 generic text

11 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/home/demo	(empty)	empty	Add link text or aria-label
https://zeffy.com/login?	Login	new tab	Add '(opens in new tab)' to text
https://zeffy.com/login?	Login	new tab	Add '(opens in new tab)' to text
https://www.g2.com/products/zeffy/review…	(empty)	empty	Add link text or aria-label
https://www.capterra.ca/reviews/220131/z…	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
https://www.facebook.com/zeffyplatform	facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/zeffyplatform/…	instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/zeffy/	linkedin	new tab	Add '(opens in new tab)' to text
https://feedback.zeffy.com/	Roadmap	new tab	Add '(opens in new tab)' to text
https://www.notion.so/zeffy/Brand-Assets…	Brand assets	new tab	Add '(opens in new tab)' to text
https://support.zeffy.com/	Documentation	new tab	Add '(opens in new tab)' to text
https://feedback.zeffy.com/feature-reque…	Request a feature	new tab	Add '(opens in new tab)' to text
https://community.zeffy.com/	Zeffy Community	new tab	Add '(opens in new tab)' to text
https://support.zeffy.com/legal-data-pri…	Legal & Privacy	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

151 links and buttons have descriptive text

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

/home/demo; https://www.g2.com/products/zeffy/reviews?utf8=✓&order=highest_rated; https://www.capterra.ca/reviews/220131/zeffy#facets; /

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://zeffy.com/login?; https://zeffy.com/login?; https://www.facebook.com/zeffyplatform; https://www.instagram.com/zeffyplatform/?hl=fr; https://www.linkedin.com/company/zeffy/; https://feedback.zeffy.com/; https://www.notion.so/zeffy/Brand-Assets-Public-b26b27c966ea4067a2c96238cd4694d8; https://support.zeffy.com/; https://feedback.zeffy.com/feature-requests; https://community.zeffy.com/ (+1 more)

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

Icon-only buttons need an aria-label so screen readers can announce them.

button#consent-close-button

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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

14 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 14 <nav> element(s)

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.

Heading Hierarchy

31 headings, 1 skip(s)

REVIEW

31 headings, 1 skip(s)

Multiple H1 headings (2 found)

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

Heading level skipped: H2 → H6 (missing H3)

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

H2 Get fundraising tips straight to your inbox
H2 Join 250K+ fundraising leaders receiving exclusive tips
H2 Get weekly fundraising tips from nonprofits experts
H6 Cookie settings skipped
H6 We use cookies
H1 All-in-one fundraising platform with zero fees.
H1 All-in-one fundraising platform with zero fees. duplicate H1
H2 The only 100% free fundraising platform for nonprofits
H2 How it works
H3 Create your fundraising form
H3 Collect payments in one click.
H3 Keep 100% of what you raise
H3 All your fundraising tools, in one platform
H2 Zeffy makes money exclusively from optional tips from your donors
H3 Will I ever have to pay to use Zeffy?
H3 How does Zeffy make money?
H3 What if my donors don’t leave a tip?
H3 Why would donors tip Zeffy?
H2 100,000 nonprofits fundraise with Zeffy
H3 SUCCESS STORIES
H2 Zero-fee fundraising in action — nonprofit stories worth sharing.
H3 Village Reach lost $1500 to Donorbox fees. They’ve already saved nearly as much with Zeffy.
H3 Zeffy Proves a Valuable Tool for the Jefferson County Democrats
H3 No Office. All Volunteers. No Time to Waste. How Waggytail Rescue Saves NYC’s Vulnerable Pets — One Zero-Fee Donation at a Time
H3 Momentum Dance Collaborative raised $22,000 to fund its workshop series thanks to Zeffy.
H3 Iron City Tryke’s Raised Over $20K with Zeffy—Enough for Almost 20 Trykes.
H3 From Platform Fees to Planting Seeds: Berry Good Food’s Zero-Fee Fundraising Story
H3 Autism Insights picked Zeffy from the beginning. They’ve never paid a single fee, saving over $1700.
H3 GB Sports Academy saved over $1,000 in PayPal fees to keep more athletes in their chosen game.
H3 Twin Steeples Creative Arts Center ditched Bloomerang’s expensive monthly subscription. Now it saves hundreds with Zeffy.
H2 Ready to get started for free?

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

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Zeffy ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✗ Multiple Sizes Missing

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

Name present: Zeffy.com

No 192x192 icon

A 192px icon is required for PWA installation.

Display mode: standalone

PWA Install Criteria Not Installable

Name Zeffy.com ✓192×192 icon ✗512×512 icon ✗Start URL . ✓Display Mode standalone ✓

Name Zeffy.com Display Mode standalone Theme Color #000000 Background Color #ffffff Icons 1 icon(s)

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 All-in-one fundraising platform with zer…

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

32px · bottom of viewport

h1 All-in-one fundraising platform with

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Get fundraising tips straight to your in…

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Join 250K+ fundraising leaders receiving…

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get weekly fundraising tips from nonprof…

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The only

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 fundraising platform for nonprofits

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How it works

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Zeffy makes money exclusively from optio…

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 100,000 nonprofits fundraise with Zeffy

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 — nonprofit stories worth sharing.

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to get started for free?

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Create your fundraising form

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Collect payments in one click.

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Keep 100% of what you raise

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 All your fundraising tools, in one platf…

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Will I ever have to pay to use Zeffy?

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 How does Zeffy make money?

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 What if my donors don’t leave a tip?

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Why would donors tip Zeffy?

1.23:1

#000000

#0F0E5B

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 All-in-one fundraisi…	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h1 All-in-one fundraisi…	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h2 Get fundraising tips…	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h2 Join 250K+ fundraisi…	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h2 Get weekly fundraisi…	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h2 The only	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h2 fundraising platform…	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h2 How it works	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h2 Zeffy makes money ex…	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h2 100,000 nonprofits f…	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h2 — nonprofit storie…	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h2 Ready to get started…	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h3 Create your fundrais…	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h3 Collect payments in …	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h3 Keep 100% of what yo…	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h3 All your fundraising…	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h3 Will I ever have to …	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h3 How does Zeffy make …	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h3 What if my donors do…	1.23:1	3.0:1	#000000	#0F0E5B	Fail
h3 Why would donors tip…	1.23:1	3.0:1	#000000	#0F0E5B	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.

Lighthouse Accessibility Audits

Score 88/100 — 4 failing, 29 passed

REVIEW

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. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Will I ever have to pay to use Zeffy? `div.stack-vertical-10px > div.fs-faq_item > div#w-dropdown-toggle-4 > h3.fs-faq_question`
How does Zeffy make money? `div.stack-vertical-10px > div.fs-faq_item > div#w-dropdown-toggle-5 > h3.fs-faq_question`
What if my donors don’t leave a tip? `div.stack-vertical-10px > div.fs-faq_item > div#w-dropdown-toggle-6 > h3.fs-faq_question`
Why would donors tip Zeffy? `div.stack-vertical-10px > div.fs-faq_item > div#w-dropdown-toggle-7 > h3.fs-faq_question`
Zero-fee fundraising in action `div.stack-vertical > h2.text-align-center > span.text-color--04cfaf > strong`
$18,345 `div.case-study_bottom-card > div.stack-2-5 > div.stack-vertical > div.raised-saved_number`
$917 `div.case-study_bottom-card > div.stack-2-5 > div.stack-vertical > div.raised-saved_number`

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.cf-padding-global > div.stack-vertical-1-25 > div.stack-1 > a.w-inline-block `div.cf-padding-global > div.stack-vertical-1-25 > div.stack-1 > a.w-inline-block`
div.cf-padding-global > div.stack-vertical-1-25 > div.stack-1 > a.w-inline-block `div.cf-padding-global > div.stack-vertical-1-25 > div.stack-1 > a.w-inline-block`
div.stack-vertical-5 > div.stack-vertical-2-5 > div.stack_header-footer > a#footer-home `div.stack-vertical-5 > div.stack-vertical-2-5 > div.stack_header-footer > a#footer-home`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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
Go to slide 1 `section.spz-home-hero-2008-2 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `section.spz-home-hero-2008-2 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `section.spz-home-hero-2008-2 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 4 `section.spz-home-hero-2008-2 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 5 `section.spz-home-hero-2008-2 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 6 `section.spz-home-hero-2008-2 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 7 `section.spz-home-hero-2008-2 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 8 `section.spz-home-hero-2008-2 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 9 `section.spz-home-hero-2008-2 > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet`

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

●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

●Input buttons have discernible text.

●Form elements have associated labels

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

●ARIA attributes are used as specified for the element's role

●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

●Elements use only permitted ARIA attributes

●ARIA toggle fields have accessible names

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●No element has a `[tabindex]` value greater than 0

●`[lang]` attributes have a valid value

●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

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with the `role=text` attribute do not have focusable descendents.

○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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<input type="image">` elements have `[alt]` text

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

Alt Text Quality

2 of 200 images have issues

PASS

2 of 200 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image(s) with generic alt text

1 image(s) with alt text over 125 characters

110 decorative image(s) correctly marked

87 image(s) with good alt text

200 images 87 good alt text 110 decorative 1 generic 1 missing

Issue	Count
missing	1 image(s)
generic	1 image(s)
too long	1 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

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