Skip to content
https://wri.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
12 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 12 <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.
C
Form Accessibility
Action
3 of 9 controls have issues
REVIEW
3 of 9 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="submit">; <input type="submit">; <input type="submit" name="op" id="edit-submit">
Info::
6 control(s) properly labeled
9 controls
6 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#osano-cm-dialog-toggle--category_MARKETINGcheckboxnone
#osano-cm-dialog-toggle--category_PERSONALIZATIONcheckboxnone
#osano-cm-dialog-toggle--category_ANALYTICScheckboxnone
#wrinsearch_2textWhat can we help you find?for/id
#wrinsearchtextWhat can we help you find?for/id
#edit-emailemailEmailfor/id
inputsubmit(none)none
inputsubmit(none)none
#edit-submitsubmit(none)none

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

<input type="submit">; <input type="submit">; <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 Click to see more ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
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 As Iran War Strains Fuel Supplies,
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Main navigation
1.43:1
#000000
on
#28282A
needs 3.0:1 (large text)
24px · mid-page
h2 Secondary Navigation
1.39:1
#000000
on
#252629
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Donate
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Quick Links
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Main navigation
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Footer menu - secondary
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mega Menu
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Filter Your Site Experience by Topic
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Search WRI.org
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What We Do
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Global Reach
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Resources
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Recently Published
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get updates on WRI’s upcoming events a…
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Stay Informed
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Footer menu - main
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Footer menu - secondary
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Footer menu - Offices
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Footer menu - Additional
1.52:1
#000000
on
#2C2D2E
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 As Iran War Strains …1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Main navigation1.43:13.0:1
#000000
#28282A
Fail
h2 Secondary Navigation1.39:13.0:1
#000000
#252629
Fail
h2 Donate1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Quick Links1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Main navigation1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Footer menu - second…1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Mega Menu1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Filter Your Site Exp…1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Search WRI.org1.52:13.0:1
#000000
#2C2D2E
Fail
h2 What We Do1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Our Global Reach1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Featured Resources1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Recently Published1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Get updates on WRI…1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Stay Informed1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Footer menu - main1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Footer menu - second…1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Footer menu - Office…1.52:13.0:1
#000000
#2C2D2E
Fail
h2 Footer menu - Additi…1.52:13.0:1
#000000
#2C2D2E
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.

A+
Landmark Structure
15 landmarks
PASS
15 landmarks
Info::
<main> landmark present
Info::
12 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "block-ts-wrin-main-menu-menu" MAIN CONTENTINFO footer
A
Heading Hierarchy
39 headings, 1 skip(s)
PASS
39 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Main navigation
  • H2 Secondary Navigation
  • H2 Donate
  • H2 Quick Links
  • H2 Main navigation
  • H2 Footer menu - secondary
  • H2 Mega Menu
  • H2 Filter Your Site Experience by Topic
  • H2 Search WRI.org
  • H1 As Iran War Strains Fuel Supplies, Clean Energy Offers Security
  • H3 Iran War Could Worsen Middle East’s Water Woes skipped
  • H3 Despite Unprecedented Challenges, Clean Energy Is Still Growing in the US. The Future Is More Uncertain.
  • H2 What We Do
  • H3 Other Topics
  • H3 Global Forest Watch
  • H3 UrbanShift
  • H3 NDC Partnership
  • H3 Partnering for Green Growth and the Global Goals 2030 (P4G)
  • H2 Our Global Reach
  • H2 Featured Resources
  • H3 Shenzhen, China Pioneers ‘Near-Zero Carbon Communities’
  • H3 Urban Trees: An Underused Tool for Keeping People Cool
  • H3 Dwindling Seagrass Is Disproportionately Impacting Coastal Women along Mozambique’s Inhambane Bay
  • H3 Can Forests Withstand and Recover from Wildfires?
  • H2 Recently Published
  • H3 RELEASE: Colombia Commits to Sustainable Management of All National Waters by 2030; Joins the 100% Alliance
  • H3 Climate Readiness as a Driver of Urban Transformation: Lessons from the WRI Ross Center Prize for Cities cycle 2023–2024
  • H3 RELEASE: Grassroots Coalition in the Philippines Wins Global Cities Prize for Transport Reform
  • H3 Shenzhen, China Pioneers ‘Near-Zero Carbon Communities’
  • H3 ADVISORY: Embargoed WRI Press Call on 2025 Global Tree Cover Loss Data and Analysis
  • H3 Urban Trees: An Underused Tool for Keeping People Cool
  • H2 Get updates on WRI’s upcoming events and insightful breakdowns of our latest research, data and other resources.
  • H3 How You Can Help
  • H2 Stay Informed
  • H2 Footer menu - main
  • H2 Footer menu - secondary
  • H2 Footer menu - Offices
  • H2 Footer menu - Additional
  • H2 Social menu

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

A+
Alt Text Quality
All 22 images OK
PASS
All 22 images OK
Info::
22 image(s) with good alt text
22 images 22 good alt text
All images have appropriate alt text.
A+
Lighthouse Accessibility Audits
Score 99/100 — 1 failing, 29 passed
PASS
99

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.

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
Iran War Could Worsen Middle East’s Water Woes div.field__item > div.node > div.field > h3

These are opportunities to improve keyboard navigation in your application.

○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]` 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
●`[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
●Background and foreground colors have a sufficient contrast ratio
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○`[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
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback