Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 ✗

Heading Hierarchy

11 headings

REVIEW

11 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 The Rundown
H2 Our Work
H3 Latest In Advance Health & Well-Being
H3 Latest In Build Communities
H3 Latest In Improve Economic Advancement
H3 Latest In Improve Federal Policy
H3 Latest In Protect Marine Life
H3 Latest In Strengthen State Government
H3 Latest In Support People & Nature
H2 Latest in
H2 Sign up for Newsletters

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Alt Text Quality

5 of 21 images have issues

REVIEW

5 of 21 images have issues

5 image(s) with generic alt text

2 image(s) with alt text over 125 characters

5 decorative image(s) correctly marked

9 image(s) with good alt text

21 images 9 good alt text 5 decorative 5 generic

Issue	Count
generic	5 image(s)
too long	2 image(s)

Link & Button Quality

3 issue(s) across 134 links and 29 buttons

REVIEW

3 issue(s) across 134 links and 29 buttons

3 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /en/about/how-we-work#approach ("Learn More"); /en/about/how-we-work#invest ("Learn More"); /en/get-involved ("Learn More")

10 link(s) open in new tab without warning

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

Got: https://www.pewresearch.org/; https://www.pewresearch.org/; https://www.pewresearch.org/short-reads/2026/04/13/most-new-data-centers-in-t…; https://cloud.pewtrusts.org/pewsignup; https://www.pewresearch.org; https://www.facebook.com/pewcharitabletrusts; https://www.instagram.com/pewtrusts/; https://www.linkedin.com/company/20974/; https://twitter.com/pewtrusts; http://youtube.com/pew

121 link(s) with descriptive text

134 links

0 empty

3 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.pewresearch.org/	Pew Research Center	new tab	Add '(opens in new tab)' to text
https://www.pewresearch.org/	Pew Research Center	new tab	Add '(opens in new tab)' to text
https://www.pewresearch.org/short-reads/…	Data Centers Are Moving to Rur…	new tab	Add '(opens in new tab)' to text
/en/about/how-we-work#approach	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: How We Work#Approach
/en/about/how-we-work#invest	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: How We Work#Invest
/en/get-involved	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Get Involved
https://cloud.pewtrusts.org/pewsignup	PICK YOUR TOPIC	new tab	Add '(opens in new tab)' to text
https://www.pewresearch.org	Pew Research Center	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/pewcharitabletr…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/pewtrusts/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/20974/	LinkedIn	new tab	Add '(opens in new tab)' to text
https://twitter.com/pewtrusts	Twitter	new tab	Add '(opens in new tab)' to text
http://youtube.com/pew	YouTube	new tab	Add '(opens in new tab)' to text

150 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/en/about/how-we-work#approach ("Learn More"); /en/about/how-we-work#invest ("Learn More"); /en/get-involved ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.pewresearch.org/; https://www.pewresearch.org/; https://www.pewresearch.org/short-reads/2026/04/13/most-new-data-centers-in-t…; https://cloud.pewtrusts.org/pewsignup; https://www.pewresearch.org; https://www.facebook.com/pewcharitabletrusts; https://www.instagram.com/pewtrusts/; https://www.linkedin.com/company/20974/; https://twitter.com/pewtrusts; http://youtube.com/pew

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

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 Page Not Found | The Pew Charitable Trusts ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Lighthouse Accessibility Audits

Score 89/100 — 3 failing, 26 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
Cookie Notice. `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-imprint-link`

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.promo-card > div.promo-card__inner-wrapper > div.promo-card__image-container > img.image-element`
`div.promo-card > div.promo-card__inner-wrapper > div.promo-card__image-container > img.image-element`

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

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
STRENGTHEN STATE GOVERNMENT `div.promo-card > div.promo-card__inner-wrapper > div.promo-card__content > a.promo-card__eyebrow`
ADVANCE HEALTH & WELL-BEING `div.promo-card > div.promo-card__inner-wrapper > div.promo-card__content > a.promo-card__eyebrow`
ADVANCE HEALTH & WELL-BEING `div.promo-card > div.promo-card__inner-wrapper > div.promo-card__content > a.promo-card__eyebrow`
ADVANCE HEALTH & WELL-BEING `div.featured-content__tertiary-item > div.promo-card > div.promo-card__content > a.promo-card__eyebrow`
PROTECT MARINE LIFE `div.featured-content__tertiary-item > div.promo-card > div.promo-card__content > a.promo-card__eyebrow`
PROTECT MARINE LIFE `div.featured-content__tertiary-item > div.promo-card > div.promo-card__content > a.promo-card__eyebrow`
ADVANCE HEALTH & WELL-BEING `div.featured-content__tertiary-item > div.promo-card > div.promo-card__content > a.promo-card__eyebrow`
ADVANCE HEALTH & WELL-BEING `div.featured-content__tertiary-item > div.promo-card > div.promo-card__content > a.promo-card__eyebrow`

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

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

●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

●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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○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

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

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

○Identical links have the same purpose.

○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

8 landmarks

PASS

8 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Form Accessibility

All 5 controls labeled

PASS

All 5 controls labeled

5 control(s) properly labeled

5 controls

5 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#newsletter-signup-input-799180bef0894937b491d8f959ab989f	email	Email	aria-label
#quick-search-de3050bd4bd84a5b97496dfefc33d585	search	Search	aria-label
#newsletter-signup-input-cc68f88e3a9e41bf95f4cc9068796080	email	Enter email address	aria-label
#newsletter-signup-input-0340edf6161e4dba819a1a6b57a5db3f	email	Enter email address	aria-label
#newsletter-signup-input-aeb5a92a30ec4d489188105089bff7eb	email	Email	aria-label

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
h2 Our Work	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h2 Latest in	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h2 Sign up for Newslett…	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 Latest In	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 Latest In	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 Latest In	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 Latest In	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 Latest In	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 Latest In	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 Latest In	18.43:1	3.0:1	#000000	#F0F0F0	Pass
title The Pew Charitable T…	20.13:1	4.5:1	#000000	#FCFAF5	Pass
a Skip to content	20.13:1	4.5:1	#000000	#FCFAF5	Pass
span Open main menu	20.13:1	4.5:1	#000000	#FCFAF5	Pass
span Our Work	20.13:1	4.5:1	#000000	#FCFAF5	Pass
div Our Work	20.13:1	4.5:1	#000000	#FCFAF5	Pass
p Our projects are amb…	20.13:1	4.5:1	#000000	#FCFAF5	Pass
p Our affiliate	20.13:1	4.5:1	#000000	#FCFAF5	Pass
span Pew Research Center	20.13:1	4.5:1	#000000	#FCFAF5	Pass
p is focused around tr…	20.13:1	4.5:1	#000000	#FCFAF5	Pass
span Advance Health & Wel…	20.13:1	4.5:1	#000000	#FCFAF5	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.

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