Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 1 REVIEW 7 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Missing

✗ 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 ✗

Lighthouse Accessibility Audits

Action

Score 62/100 — 11 failing, 20 passed

FIX

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 roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#form-text-63-wrapper > div.views-widget > div.form-item > input#form-text-63 `div#form-text-63-wrapper > div.views-widget > div.form-item > input#form-text-63`

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
Learn more about cookies `body.html > div.cc-window > span#cookieconsent:desc > a.cc-link`
SHORT READS `div.group-right > div.field > div.field-items > div.field-item`
APRIL 2026 `div.field > div.field-items > div.field-item > span.date-display-single`
RECENT PUBLICATIONS see all > `div.inside > div.panel-pane > div.pane-content > h3`
FACT SHEETS `div.group-right > div.field > div.field-items > div.field-item`
MARCH 2026 `div.field > div.field-items > div.field-item > span.date-display-single`
By Greg García, Gloria Choi and Lorena Mancilla `div.group-right > div.field > div.field-items > div.field-item`
Greg García, Gloria Choi and Lorena Mancilla `div.field > div.field-items > div.field-item > span.textformatter-list`
REPORTS `div.group-right > div.field > div.field-items > div.field-item`
FEBRUARY 2026 `div.field > div.field-items > div.field-item > span.date-display-single`
By María Belén Zanzuchi, Kate Hooper and Abigail Goldfarb `div.group-right > div.field > div.field-items > div.field-item`
María Belén Zanzuchi, Kate Hooper and Abigail Goldfarb `div.field > div.field-items > div.field-item > span.textformatter-list`
FACT SHEETS `div.group-right > div.field > div.field-items > div.field-item`
FEBRUARY 2026 `div.field > div.field-items > div.field-item > span.date-display-single`
By Valerie Lacarte `div.group-right > div.field > div.field-items > div.field-item`
Valerie Lacarte `div.field > div.field-items > div.field-item > span.textformatter-list`
FACT SHEETS `div.group-right > div.field > div.field-items > div.field-item`
FEBRUARY 2026 `div.field > div.field-items > div.field-item > span.date-display-single`
By Jeanne Batalova `div.group-right > div.field > div.field-items > div.field-item`
Jeanne Batalova `div.field > div.field-items > div.field-item > span.textformatter-list`

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
Native Language Assessments for K-12 English Learners: A 2025 State-Level Snaps… `div.field > div.field-items > div.field-item > h5`

These are opportunities to improve keyboard navigation in your application.

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.field-content > p > a > img `div.field-content > p > a > img`
div.content > p > a > img `div.content > p > a > img`
div.content > p > a > img `div.content > p > a > img`
div.content > p > a > img `div.content > p > a > img`
div.content > p > a > img `div.content > p > a > img`
div.content > p > a > img `div.content > p > a > img`
div.content > p > a > img `div.content > p > a > img`

Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.views-exposed-widgets > div#edit-submit-2-search-fullsite-page-1-wrapper > div.views-widget > input#edit-submit-2-search-fullsite-page-1 `div.views-exposed-widgets > div#edit-submit-2-search-fullsite-page-1-wrapper > div.views-widget > input#edit-submit-2-search-fullsite-page-1`

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#form-text-63-wrapper > div.views-widget > div.form-item > input#form-text-63 `div#form-text-63-wrapper > div.views-widget > div.form-item > input#form-text-63`

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
All MPI Research Publications Articles Multimedia Events News `div#edit-field-publication-type-wrapper > div.views-widget > div.form-item > select#edit-field-publication-type`

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.views-field > div.field-content > p > a `div.views-field > div.field-content > p > a`
div.block-inner > div.content > p > a `div.block-inner > div.content > p > a`
div.block-inner > div.content > p > a `div.block-inner > div.content > p > a`
div.block-inner > div.content > p > a `div.block-inner > div.content > p > a`
div.block-inner > div.content > p > a `div.block-inner > div.content > p > a`
div.block-inner > div.content > p > a `div.block-inner > div.content > p > a`
div.block-inner > div.content > p > a `div.block-inner > div.content > 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.

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#viewport `head > meta#viewport`

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
1 `div.view > div.view-header > div#slideshow-nav-sidebar > a.activeSlide`
2 `div.view > div.view-header > div#slideshow-nav-sidebar > a`
3 `div.view > div.view-header > div#slideshow-nav-sidebar > a`
4 `div.view > div.view-header > div#slideshow-nav-sidebar > a`
5 `div.view > div.view-header > div#slideshow-nav-sidebar > a`
6 `div.view > div.view-header > div#slideshow-nav-sidebar > a`
7 `div.view > div.view-header > div#slideshow-nav-sidebar > a`

These items highlight common accessibility best practices.

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
I understand `body.html > div.cc-window > div.cc-compliance > a.cc-btn`

○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]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

○Buttons have an accessible name

○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

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

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Error - Page Not Found | migrationpolicy.org ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

A+

Heading Hierarchy

4 headings

PASS

4 headings

Single H1 present

H1 Sorry, you have been blocked
H2 You are unable to access migrationpolicy.org
H2 Why have I been blocked?
H2 What can I do to resolve this?

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

1 links, 1 buttons — all OK

PASS

1 links, 1 buttons — all OK

1 link(s) open in new tab without warning

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

Got: https://www.cloudflare.com/5xx-error-landing

1 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.cloudflare.com/5xx-error-lan…	Cloudflare	new tab	Add '(opens in new tab)' to text

1 links and buttons have descriptive text

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

https://www.cloudflare.com/5xx-error-landing

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

A+

Color Contrast (Screenshot)

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

18 pass

Show all checked elements (18)

Element	Ratio	Required	FG	BG	Result
h1 Sorry, you have been…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 migrationpolicy.org	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Why have I been bloc…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 What can I do to res…	17.62:1	3.0:1	#000000	#EBEBEB	Pass
title Attention Required! …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Please enable cookie…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span You are unable to ac…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p This website is usin…	17.62:1	4.5:1	#000000	#EBEBEB	Pass
p You can email the si…	17.62:1	4.5:1	#000000	#EBEBEB	Pass
span Cloudflare Ray ID:	17.62:1	4.5:1	#000000	#EBEBEB	Pass
strong 9f0888b32f886ee5	17.62:1	3.0:1	#000000	#EBEBEB	Pass
span •	18.76:1	4.5:1	#000000	#F2F2F2	Pass
span Your IP:	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Click to reveal	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 2001:41d0:ab00::4:0:…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span •	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Performance & securi…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Cloudflare	21.00:1	4.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.

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