Skip to content
https://aspca.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
F
Alt Text Quality
Action
18 of 35 images have issues
FIX
18 of 35 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
13 image(s) with generic alt text
Info::
2 decorative image(s) correctly marked
Info::
15 image(s) with good alt text
35 images 15 good alt text 2 decorative 13 generic 5 missing
IssueCount
missing5 image(s)
generic13 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Form Accessibility
2 of 8 controls have issues
REVIEW
2 of 8 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="op" id="edit-submit--2">; <input type="submit" name="op" id="edit-submit">
Info::
6 control(s) properly labeled
8 controls
6 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#edit-search-block-form--2textSearchfor/id
#edit-submitted-sbp-first-nametextFirst Name *for/id
#edit-submitted-sbp-last-nametextLast Name *for/id
#edit-submitted-mailemailEmail Address *for/id
#edit-submitted-mobile-phonetextMobile Numberfor/id
#edit-email-addresstextLeave this field blankfor/id
#edit-submit--2submit(none)none
#edit-submitsubmit(none)none

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

<input type="submit" name="op" id="edit-submit--2">; <input type="submit" name="op" id="edit-submit">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Oops! Page Not Found. | ASPCA ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
25 icon(s) detected
REVIEW
25 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
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, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA 4 pass AA only
a Investigations and Rescue
3.40:1
#000000
on
#63615E
needs 4.5:1 (normal text)
16px · above the fold
a Animal Care and Recovery
4.43:1
#000000
on
#747371
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Primary Nav Menu21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Search form21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The Latest21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Connect with Us21.00:13.0:1
#000000
#FFFFFF
Pass
h2 You Can21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Make a Difference21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Featured Highlights21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Donate21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Advocate21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Give Monthly21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Help the ASPCA Put a…21.00:13.0:1
#000000
#FFFFFF
Pass
title ASPCA | American Soc…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
span ASPCA21.00:14.5:1
#000000
#FFFFFF
Pass
span Our6.63:14.5:1
#000000
#F76006
Pass
span Work6.63:14.5:1
#000000
#F76006
Pass
a Helping Shelters, Pe…6.63:14.5:1
#000000
#F76006
Pass
a Investigations and R…3.40:14.5:1
#000000
#63615E
Fail
a Animal Care and Reco…4.43:14.5:1
#000000
#747371
Fail
a Improving Laws for A…4.70:14.5:1
#000000
#787777
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.

C
Lighthouse Accessibility Audits
Action
Score 74/100 — 5 failing, 17 passed
REVIEW
74

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
April 10, 2026 div.view-content > div.views-row > div.timestamp > span.date-display-single
The ASPCA Turns 160: Celebrating Our History div.views-row > div.views-field > span.field-content > a
April 14, 2026 div.view-content > div.views-row > div.timestamp > span.date-display-single
Join Us for Our Sweet 160th Adoption Bash! div.views-row > div.views-field > span.field-content > a
https://secure.aspca.org/donate/joinaspca?ms=wb_lpf_homepage-featuredhighlight-… div.cycle-carousel-wrap > div.featured-story > div.link > a
https://www.aspca.org/news/elio-cant-say-no-cheesy-treat-or-new-best-friend div.cycle-carousel-wrap > div.featured-story > div.link > a
©2026 The American Society for the Prevention of Cruelty to Animals. All rights… div.l-footer-inner > div.region > div#block-block-15 > p
Our Partnerships div.l-footer-inner > div.region > div#block-block-86 > h4
Underwritten by Independence American Insurance Company div#block-block-86 > ul.partnerships > li > p

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#block-block-15 > p > a > img div#block-block-15 > p > a > img

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.region > div#block-block-15 > p > a div.region > div#block-block-15 > p > a

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
Will You Be the Hero They're Hoping For? Just 63¢ a day can help rescue and pro… div.view > div.view-content > div.item-list > ul.rslides1

These are opportunities to improve the experience of reading tabular or list data using 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

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●Buttons have an accessible name
●Input buttons have discernible text.
●Form elements have associated labels
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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.
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`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 input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted 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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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 type="image">` elements have `[alt]` text
○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.
A
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH 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+
Heading Hierarchy
12 headings
PASS
12 headings
Info::
Single H1 present
  • H1 ASPCA
  • H2 Primary Nav Menu
  • H2 Search form
  • H2 The Latest
  • H2 Connect with Us
  • H2 You Can Make a Difference
  • H3 Donate
  • H3 Advocate
  • H3 Give Monthly
  • H2 Featured Highlights
  • H3 Help the ASPCA Put a Stop to Animal Cruelty
  • H4 Our Partnerships
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: https://www.aspca.org/sites/default/files/css/css_WRd1oD8kdCE1CpDSrTDsLYVBeeyBmKeiOMdQgCl8vGs.css
Print Stylesheet ✓ Print Optimized
Print stylesheet https://www.aspca.org/sites/default/files/css/css_WRd1oD8kdCE1CpDSrTDsLYVBeeyBmKeiOMdQgCl8vGs.css ✓Inline @media print Not detected ✗
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback