Skip to content
https://plannedparenthood.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
4
REVIEW
8
PASS
1
INFO
0
Checks
13
1 PASS 8 REVIEW 4 FIX
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
No navigation patterns
FIX
No navigation patterns
Info::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 6 <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
Landmark Structure
15 landmarks
REVIEW
15 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
1 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
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

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

C
Heading Hierarchy
Action
20 headings, 2 skip(s)
REVIEW
20 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 Get Care
  • H4 Resources
  • H4 Explore
  • H4 Topics
  • H4 Resources and Tools
  • H4 Get Involved
  • H1 Your health is our priority — no matter what.
  • H3 Need an abortion? skipped
  • H3 Have you seen us on TV?
  • H3 Questions about your sexual health?
  • H2 Get care on the go — no appointment needed.
  • H2 Careers and Volunteering
  • H1 Sign Up for Email Alerts duplicate H1
  • H3 Thank you! skipped
  • H2 Trusted care, every step of the way
  • H3 This website uses cookies
  • H3 Cookie Settings
  • H4 Marketing
  • H4 Performance
  • H4 Analytics

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

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

C
Form Accessibility
Action
3 of 5 controls have issues
REVIEW
3 of 5 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="option1">; <input type="checkbox" id="option2">; <input type="checkbox" id="option3">
Info::
2 control(s) properly labeled
5 controls
2 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#PostalCodetextZip Code*for/id
#EmailAddressemailEmail Address*for/id
#option1checkbox(none)none
#option2checkbox(none)none
#option3checkbox(none)none

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

<input type="checkbox" id="option1">; <input type="checkbox" id="option2">; <input type="checkbox" id="option3">

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 Follow us on ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA 1 pass AA only
a Español
1.53:1
#000000
on
#00286E
needs 4.5:1 (normal text)
16px · top of page (header area)
span Get Care
1.53:1
#000000
on
#00286E
needs 4.5:1 (normal text)
16px · top of page (header area)
h4 Get Care
1.53:1
#000000
on
#00286E
needs 3.0:1 (large text)
16px · above the fold
span Schedule an Appointment
1.53:1
#000000
on
#00286E
needs 4.5:1 (normal text)
16px · above the fold
span Telehealth
1.53:1
#000000
on
#00286E
needs 4.5:1 (normal text)
16px · above the fold
span Abortion
1.53:1
#000000
on
#00286E
needs 4.5:1 (normal text)
16px · above the fold
h4 Resources
1.53:1
#000000
on
#00286E
needs 3.0:1 (large text)
16px · above the fold
span Our Services
1.53:1
#000000
on
#00286E
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Sign Up for Email Al…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get care on the go …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Careers and Voluntee…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trusted care, every …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Need an abortion?21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Have you seen us on …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Questions about your…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Thank you!21.00:13.0:1
#000000
#FFFFFF
Pass
h3 This website uses co…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cookie Settings21.00:13.0:1
#000000
#FFFFFF
Pass
title Planned Parenthood |…21.00:14.5:1
#000000
#FFFFFF
Pass
a Go to Content5.11:14.5:1
#000000
#667EA8
Pass
a Español1.53:14.5:1
#000000
#00286E
Fail
span Get Care1.53:14.5:1
#000000
#00286E
Fail
h4 Get Care1.53:13.0:1
#000000
#00286E
Fail
span Schedule an Appointm…1.53:14.5:1
#000000
#00286E
Fail
span Telehealth1.53:14.5:1
#000000
#00286E
Fail
span Abortion1.53:14.5:1
#000000
#00286E
Fail
h4 Resources1.53:13.0:1
#000000
#00286E
Fail
span Our Services1.53:14.5:1
#000000
#00286E
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 80/100 — 7 failing, 25 passed
REVIEW
80

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ABOUT US TOGGLE NAVIGATION GET INVOLVED TOGGLE NAVIGATION RESOURCES TOGGLE NAVI… footer.site-footer > div.site-footer-wrapper > nav.site-footer-nav > ul.menu

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ABOUT US nav.site-footer-nav > ul.menu > li#rcoecr-acc-menu-link > a.site-footer-nav-heading
TOGGLE NAVIGATION nav.site-footer-nav > ul.menu > li#rcoecr-acc-menu-link > a.site-footer-nav-toggler
GET INVOLVED nav.site-footer-nav > ul.menu > li#ymwwgt-acc-menu-link > a.site-footer-nav-heading
TOGGLE NAVIGATION nav.site-footer-nav > ul.menu > li#ymwwgt-acc-menu-link > a.site-footer-nav-toggler
RESOURCES nav.site-footer-nav > ul.menu > li#tup7hw-acc-menu-link > span.site-footer-nav-heading
TOGGLE NAVIGATION nav.site-footer-nav > ul.menu > li#tup7hw-acc-menu-link > a.site-footer-nav-toggler
ABOUT THIS SITE nav.site-footer-nav > ul.menu > li#kuwql4-acc-menu-link > a.site-footer-nav-heading
TOGGLE NAVIGATION nav.site-footer-nav > ul.menu > li#kuwql4-acc-menu-link > a.site-footer-nav-toggler

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
DONATE header#site-header > div.site-header-outer-wrapper > div.site-header-wrapper > a.mobile-nav-donate
BOOK AN APPOINTMENT header#04512158-6fc5-4ba4-9ad9-c39977fa4a42 > div.text-actions > pp-button.pp-new-button > a.pp-new-button__primary
TELEHEALTH header#04512158-6fc5-4ba4-9ad9-c39977fa4a42 > div.text-actions > pp-button.pp-new-button > a.pp-new-button__primary
LEARN MORE div.tile-content > div.tile-footer > pp-button.pp-new-button > a.pp-new-button__primary
DONATE TODAY div.tile-content > div.tile-footer > pp-button.pp-new-button > a.pp-new-button__primary
CHAT NOW div.tile-content > div.tile-footer > pp-button.pp-new-button > a.pp-new-button__primary
GET CARE NOW header#e216f7ca-ce9b-4e61-871c-f9f32572eb27 > div.text-actions > pp-button.pp-new-button > a.pp-new-button__primary
FIND OPPORTUNTIES div.ribbon-new--container > section.ribbon-new--content > pp-button.pp-new-button > a.pp-new-button__primary
BOOK AN APPOINTMENT div.grid-container > div.ribbon-content > div.input-group-button > a.button
1-800-230-7526 div.ribbon-content > div.phone-number > p.call-pp > a
Privacy Notice div.cookieBanner__main-body > p.paragraph-xs > span#relaxed-prompt-text > a
Cookie settings div.cookieBanner__wrapper > div.cookieBanner__actions > pp-link#openCookieBannerSettings > a.pp-link__inline
ALLOW ALL div.cookieBanner__wrapper > div.cookieBanner__actions > pp-button#CookieBannerAllowAll > button.pp-new-button__primary

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
Need an abortion?  section.tile > div.tile-content > div > h3.heading-4

These are opportunities to improve keyboard navigation in your application.

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
Español div.page-wrap > header#site-header > nav.site-utility > ul

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Español nav.site-utility > ul > span > li

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Español ul > span > li > a.site-language-toggler-desktop
TELEHEALTH header#04512158-6fc5-4ba4-9ad9-c39977fa4a42 > div.text-actions > pp-button.pp-new-button > a.pp-new-button__primary
CHAT NOW div.tile-content > div.tile-footer > pp-button.pp-new-button > a.pp-new-button__primary
GET CARE NOW header#e216f7ca-ce9b-4e61-871c-f9f32572eb27 > div.text-actions > pp-button.pp-new-button > a.pp-new-button__primary
FIND OPPORTUNTIES div.ribbon-new--container > section.ribbon-new--content > pp-button.pp-new-button > a.pp-new-button__primary
○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
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Links are distinguishable without relying on color.
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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
Alt Text Quality
1 of 7 images have issues
PASS
1 of 7 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
5 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
7 images 1 good alt text 5 decorative 1 missing
IssueCount
missing1 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.

Send Feedback