Skip to content
https://brookings.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Form Accessibility
Action
12 of 12 controls have issues
FIX
12 of 12 controls have issues
Critical::
9 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" name="nl_brookingsbrief">; <input type="text" name="name">; <textarea name="notes">; <input type="checkbox" name="verification">; <input type="checkbox" name="nl_brookingsbrief">; <input type="text" name="name">; <textarea name="notes">; <input type="checkbox" name="verification">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s" id="search">; <input type="email" name="email" id="subscribe-email">; <input type="email" name="email">
12 controls
0 labeled
3 placeholder only
9 unlabeled
ControlTypeLabelMethod
#searchsearch(Start typing to search)placeholder only
#subscribe-emailemail(Email Address)placeholder only
emailemail(Email Address)placeholder only
notestextarea(none)none
verificationcheckbox(none)none
nl_brookingsbriefcheckbox(none)none
nl_brookingsbriefcheckbox(none)none
nametext(none)none
notestextarea(none)none
verificationcheckbox(none)none
nametext(none)none
#g-recaptcha-response-100000textarea(none)none

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

<input type="checkbox" name="nl_brookingsbrief">; <input type="text" name="name">; <textarea name="notes">; <input type="checkbox" name="verification">; <input type="checkbox" name="nl_brookingsbrief">; <input type="text" name="name">; <textarea name="notes">; <input type="checkbox" name="verification">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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

Placeholder text disappears on focus and is not a reliable label.

<input type="search" name="s" id="search">; <input type="email" name="email" id="subscribe-email">; <input type="email" name="email">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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::
5 navigation landmark(s) detected
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 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <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

B
Heading Hierarchy
12 headings
REVIEW
12 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Advancing ideas that matter
  • H3 Brookings’ scholarly research educates the public and informs decisionmakers on complex policy challenges.
  • H3 Quality research
  • H3 Independent analysis
  • H3 Lasting impact
  • H2 Iran
  • H2 Climate & Energy
  • H2 Brookings Brief
  • H2 Brookings Podcast Network
  • H2 2026 Midterm Elections
  • H2 Education
  • H2 Upcoming Events

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

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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | Brookings ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
B
Favicon & Branding
9 icon(s) detected
REVIEW
9 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 Present
✓ Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
A
Alt Text Quality
All 42 images OK
PASS
All 42 images OK
Info::
12 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
28 image(s) with good alt text
42 images 28 good alt text 2 decorative
IssueCount
too long12 image(s)
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)
ElementRatioRequiredFGBGResult
h2 Advancing ideas that…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Iran21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Climate & Energy21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Brookings Brief21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Brookings Podcast Ne…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 2026 Midterm Electio…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Education21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Upcoming Events21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Brookings’ scholar…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Quality research21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Independent analysis21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Lasting impact21.00:13.0:1
#000000
#FFFFFF
Pass
title Brookings - Quality.…21.00:14.5:1
#000000
#FFFFFF
Pass
span Opens in a new windo…21.00:14.5:1
#000000
#FFFFFF
Pass
span Opens an external we…21.00:14.5:1
#000000
#FFFFFF
Pass
span Opens an external we…21.00:14.5:1
#000000
#FFFFFF
Pass
span This website utilize…21.00:14.5:1
#000000
#FFFFFF
Pass
a Privacy Policy21.00:14.5:1
#000000
#FFFFFF
Pass
button Accept21.00:14.5:1
#000000
#FFFFFF
Pass
button Deny Non-Essential21.00:14.5:1
#000000
#FFFFFF
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.

A
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 24 passed
PASS
91

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.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer-main-cta > div.footer-main-cta-form > form#footerSubscribe > input.screen-reader-text div.footer-main-cta > div.footer-main-cta-form > form#footerSubscribe > input.screen-reader-text

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
header.header > div.primary-nav > div.flex > a.uk-navbar-toggle header.header > div.primary-nav > div.flex > a.uk-navbar-toggle
div.footer-main > div.footer-main-cta > div.brookings-b > a div.footer-main > div.footer-main-cta > div.brookings-b > 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.

○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
●`[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
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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 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
○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
○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.
○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.
○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