Skip to content
https://actionnetwork.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Heading Hierarchy
Action
14 headings, 4 skip(s)
FIX
14 headings, 4 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Powering you to inspire action
  • H2 Powerful, flexible tools to engage your community when it matters most.
  • H6 POWERING CHANGE skipped
  • H3 In the first 24 hours after President Biden endorsed Vice President Harris, organizations raised over $70 million using Action Network.
  • H2 Tools built by and for…
  • H2 Tools made to…
  • H4 Raise Money skipped
  • H4 Mobilize Supporters
  • H4 Organize Supporters
  • H4 Emi Guereca
  • H6 Women’s March Foundation skipped
  • H2 Get started
  • H5 Get Started skipped
  • H2 Mobile Menu Overlay

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

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

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

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
7 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 7 <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.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Action Network ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 16 fail WCAG AA
REVIEW

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

4 pass 16 fail WCAG AA 4 pass AA only
h1 Powering you to inspire action
1.50:1
#000000
on
#1F2C43
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Powerful, flexible tools to engage your …
1.50:1
#000000
on
#1F2C43
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tools built by and for…
1.50:1
#000000
on
#1F2C43
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tools made to…
1.50:1
#000000
on
#1F2C43
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get started
1.50:1
#000000
on
#1F2C43
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mobile Menu Overlay
1.50:1
#000000
on
#1F2C43
needs 3.0:1 (large text)
24px · bottom of viewport
h3 In the first 24 hours after President Bi…
1.50:1
#000000
on
#1F2C43
needs 3.0:1 (large text)
19px · bottom of viewport
a Login
1.26:1
#000000
on
#211D22
needs 4.5:1 (normal text)
16px · above the fold
a Tools
1.26:1
#000000
on
#211D22
needs 4.5:1 (normal text)
16px · above the fold
span Show submenu for “Tools”
1.26:1
#000000
on
#211D22
needs 4.5:1 (normal text)
16px · above the fold
span Tools To...
1.26:1
#000000
on
#211D22
needs 4.5:1 (normal text)
16px · above the fold
a Fundraise for your movement
1.26:1
#000000
on
#211D22
needs 4.5:1 (normal text)
16px · above the fold
a Mobilize and engage supporters
1.26:1
#000000
on
#211D22
needs 4.5:1 (normal text)
16px · above the fold
a Organize supporters
1.26:1
#000000
on
#211D22
needs 4.5:1 (normal text)
16px · above the fold
span Tools For...
1.26:1
#000000
on
#211D22
needs 4.5:1 (normal text)
16px · above the fold
a Non-Profit Organizations
1.26:1
#000000
on
#211D22
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Powering you to insp…1.50:13.0:1
#000000
#1F2C43
Fail
h2 Powerful, flexible t…1.50:13.0:1
#000000
#1F2C43
Fail
h2 Tools built by and f…1.50:13.0:1
#000000
#1F2C43
Fail
h2 Tools made to…1.50:13.0:1
#000000
#1F2C43
Fail
h2 Get started1.50:13.0:1
#000000
#1F2C43
Fail
h2 Mobile Menu Overlay1.50:13.0:1
#000000
#1F2C43
Fail
h3 In the first 24 hour…1.50:13.0:1
#000000
#1F2C43
Fail
title Home - Action Networ…5.56:14.5:1
#000000
#1781FA
Pass
a Skip to content5.56:14.5:1
#000000
#1781FA
Pass
div Action Network is in…5.56:14.5:1
#000000
#1781FA
Pass
a Join Waitlist5.56:14.5:1
#000000
#1781FA
Pass
a Login1.26:14.5:1
#000000
#211D22
Fail
a Tools1.26:14.5:1
#000000
#211D22
Fail
span Show submenu for “…1.26:14.5:1
#000000
#211D22
Fail
span Tools To...1.26:14.5:1
#000000
#211D22
Fail
a Fundraise for your m…1.26:14.5:1
#000000
#211D22
Fail
a Mobilize and engage …1.26:14.5:1
#000000
#211D22
Fail
a Organize supporters1.26:14.5:1
#000000
#211D22
Fail
span Tools For...1.26:14.5:1
#000000
#211D22
Fail
a Non-Profit Organizat…1.26:14.5:1
#000000
#211D22
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 21 passed
REVIEW
85

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
Action Network is introducing Boost to supercharge your program! Join Waitlist body.page-template-default > div#page > div#header > div.boost-is-coming-soon
Join Waitlist div#page > div#header > div.boost-is-coming-soon > a#join-waitlist
Run the very best version of your fundraising program. Our email and mobile fun… div.container > div.tools-actions__tile-list > div.tile > p
Learn More div.container > div.tools-actions__tile-list > div.tile > a
Make the most of big moments to connect with your community and turn casual sup… div.container > div.tools-actions__tile-list > div.tile > p
Learn More div.container > div.tools-actions__tile-list > div.tile > a
Quickly create events, recruit volunteers, and make RSVPing easy with a map tha… div.container > div.tools-actions__tile-list > div.tile > p
Learn More div.container > div.tools-actions__tile-list > div.tile > a

These are opportunities to improve the legibility of your content.

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
POWERING CHANGE div.container > div.case-study-columns > div.case-study-columns__content > h6.eyebrow
Raise Money div.container > div.tools-actions__tile-list > div.tile > h4
WOMEN’S MARCH FOUNDATION div.container > div.quote__wrapper > div.quote__content > h6.quote-byline
div.footer-columns__two > div.footer-get-started > div.footer-get-started__text_buttons > h5 div.footer-columns__two > div.footer-get-started > div.footer-get-started__text_buttons > h5

These are opportunities to improve keyboard navigation in your application.

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.container > div.row > div.site-header__item > a.site-header__item_inner div.container > div.row > div.site-header__item > a.site-header__item_inner
div.footer-columns__two > div.footer-get-started > div.footer-mobile-logo > a.site-footer__logo div.footer-columns__two > div.footer-get-started > div.footer-mobile-logo > a.site-footer__logo

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.primary > ul#primary-navigation-footer > li.menu-item > ul.sub-menu__col-2 nav.primary > ul#primary-navigation-footer > li.menu-item > ul.sub-menu__col-2
nav.primary > ul#primary-navigation-footer > li.menu-item > ul.sub-menu__col-3 nav.primary > ul#primary-navigation-footer > li.menu-item > ul.sub-menu__col-3
nav.primary > ul#primary-navigation-footer > li.menu-item > ul.sub-menu nav.primary > ul#primary-navigation-footer > li.menu-item > ul.sub-menu
nav.primary > ul#primary-navigation-footer > li.menu-item > ul.sub-menu__col-1 nav.primary > ul#primary-navigation-footer > li.menu-item > ul.sub-menu__col-1
nav.primary > ul#primary-navigation-footer > li.menu-item > ul.sub-menu__col-4 nav.primary > ul#primary-navigation-footer > li.menu-item > ul.sub-menu__col-4
nav.primary > ul#primary-navigation-footer > li.menu-item > ul.sub-menu nav.primary > ul#primary-navigation-footer > li.menu-item > ul.sub-menu

These are opportunities to improve the experience of reading tabular or list data using 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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○Buttons have an accessible name
○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
○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
○`<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.
○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.
A
Landmark Structure
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Warning::
1 of 7 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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

A+
Alt Text Quality
All 14 images OK
PASS
All 14 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
13 image(s) with good alt text
14 images 13 good alt text
IssueCount
too long1 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback