Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FHeading HierarchyAction231 headings, 85 skip(s)FIX
- H6 Priorities
- H6 Topics
- H6 States
- H4 Trump and Congressional Republicans’ Plan To Pump More Money Into ICE and Border Patrol Is a Missed Opportunity To Help Americans
- H4 The Human and Environmental Costs of the War in Iran
- H4 Why Alaska and U.S. Territories Get Damage, Not Dollars, From Deep-Sea Mining
- H2 The Path Forward
- H4 A Patients’ Bill of Rights To Lower Health Care Costs skipped
- H4 Stopping Sticker Shock at the Grocery Store: A Plan To Make Food More Affordable
- H4 Build, Baby, Build: A Plan To Lower Housing Costs for All
- H4 The Corporate Power Reset That Makes Citizens United Irrelevant
- H4 Most Recent
- H4 Trump and Congressional Republicans’ Plan To Pump More Money Into ICE and Border Patrol Is a Missed Opportunity To Help Americans
- H4 Why Alaska and U.S. Territories Get Damage, Not Dollars, From Deep-Sea Mining
- H4 The one question Trump’s Fed chair nominee must answer
- H4 The Human and Environmental Costs of the War in Iran
- H4 Stabilizing and Strengthening State Funding for Public Higher Education After the Big Beautiful Bill
- H2 Spotlight
- H4 What America Has Lost in the War With Iran skipped
- H4 Orbán’s Defeat in the Hungarian Election Signals a Blow to the Global Authoritarian Movement
- H4 The Trump Administration’s $1,000 Tax Refund Promise Falls Short by $665
- H4 Trump’s War May Be Over But the Economic Damage Is Not
- H4 Trump Global Weakness Watch: How Trump Is Undermining American Power
- H4 4 Strategies To Improve ICE and CBP Recruiting, Hiring, and Training Using State and Local Best Practices
- H4 Event
- H4 Climate Action, Close to Home
- H2 Economy
- H4 The Trump Administration’s Policies Have Hurt Growth, Jobs, and Prices skipped
- H4 Volatile Job Numbers Mask Stagnant Labor Market in the Trump Administration’s Economy: Analysis of the March 2026 Jobs Report
- H4 5 Ways the Trump Administration’s War With Iran Is Making It Harder To Make Things in America
- H4 Trump’s War in Iran Is Increasing Mortgage Rates
- H4 Congress Must Stop Prediction Market Corruption
- H2 Climate
- H4 Climate Change Is Here—and America’s Most Marginalized Communities Are on the Front Lines skipped
- H4 Trading Offshore Wind for LNG: A Lose-Lose for Americans
- H4 The War in Iran Will Raise Fuel Prices and Costs Throughout the Economy
- H4 Trump’s ‘God Squad’ Is Killing Whales Under the Guise of National Security
- H4 How the Trump Administration Could Lower Energy Prices and What It Is Doing Instead
- H3 InProgress Stay informed on the most pressing issues of our time.
- H3 Default Opt Ins
- H3 Variable Opt Ins
- H2 Health
- H4 Does Medicare Still Cover Durable Medical Equipment? skipped
- H4 Escaping the Medigap Trap: A Path to Real Choice in Medicare
- H4 How the Trump Administration’s Embrace of Oil, Gas, and Chemical Industry Interests Will Endanger Children’s Health
- H4 6 Ways States Can Protect Vaccine Access While the Trump Administration Dismantles the Federal System
- H4 How States Can Combat Health Care Consolidation and Corporate Conflicts of Interest
- H4 Featured Experts
- H4 Akua Amaning
- H6 Bipartisan Momentum Is Growing for Automatic Record Sealing Through the Clean Slate and Fresh Start Acts skipped
- H4 Shannon Baker-Branstetter
- H6 Residents of 49 States and Washington, D.C., Face Increasing Electric and Natural Gas Bills skipped
- H4 Gréta Bedekovics
- H6 Orbán’s Defeat in the Hungarian Election Signals a Blow to the Global Authoritarian Movement skipped
- H4 Robert Benson
- H6 An EU-China bridge is designed to crumble skipped
- H4 Alan Cohen
- H6 Trump made a promise not to touch Medicare. His megabill just broke it. skipped
- H4 Frances Colón
- H6 Marco Rubio’s Deal: Trading Venezuelan Democracy for Oil skipped
- H4 Adam Conner
- H6 5 Things You Should Know About AI Right Now skipped
- H4 Margaret Cooney
- H6 Trump’s ‘God Squad’ Is Killing Whales Under the Guise of National Security skipped
- H4 David Cutler
- H4 Rudy deLeon
- H6 1.3 Million Active-Duty Service Members Would Go Without Pay During a Government Shutdown skipped
- H4 Zeke Emanuel
- H6 FORMER BIDEN HEALTH ADVISOR: We’re running out of time. American businesses should start requiring vaccinations for their workers. skipped
- H4 Sara Estep
- H6 Immigrants Make the Labor Market Great skipped
- H4 Emily Gee
- H6 Trump’s War May Be Over But the Economic Damage Is Not skipped
- H4 Hailey Gibbs
- H6 The Trump Administration’s Changes to the Child Care and Development Fund Would Strip Families of Thousands of Dollars in Potential Child Care Savings skipped
- H4 Mark Haggerty
- H6 Why Alaska and U.S. Territories Get Damage, Not Dollars, From Deep-Sea Mining skipped
- H4 Cody Hankerson
- H6 The Lasting Threat of Trump’s Cuts to NOAA and NWS on American Communities skipped
- H4 Johan Hassel
- H6 Progressives should use COP30 to show democracies can deliver prosperity and save the planet skipped
- H4 Trevor Higgins
- H6 The War in Iran Will Raise Fuel Prices and Costs Throughout the Economy skipped
- H4 Mia Ives-Rublee
- H6 Does Medicare Still Cover Durable Medical Equipment? skipped
- H4 Cathleen Kelly
- H6 How the Trump Administration’s Embrace of Oil, Gas, and Chemical Industry Interests Will Endanger Children’s Health skipped
- H4 Bobby Kogan
- H6 Trump and Congressional Republicans’ Plan To Pump More Money Into ICE and Border Patrol Is a Missed Opportunity To Help Americans skipped
- H4 David Madland
- H6 4 Things To Know About Sectoral Bargaining skipped
- H4 Alan Makovsky
- H6 Opportunities and Challenges in the Eastern Mediterranean: Examining U.S. Interests and Regional Cooperation skipped
- H4 Elisa Massimino
- H6 It’s time to close Guantanamo skipped
- H4 Silva Mathema
- H6 The Trump Administration’s ICE and CBP Have Become a Threat to Americans: Congress Must Ensure That DHS Follows the Law and Adopts Commonsense Reforms skipped
- H4 Drew McConville
- H6 Reimagining Endangered Species Conservation in a Time of Crisis skipped
- H4 Allison McManus
- H6 What America Has Lost in the War With Iran skipped
- H4 Natasha Murphy
- H6 A Patients’ Bill of Rights To Lower Health Care Costs skipped
- H4 Ben Olinsky
- H6 Four changes in the day-to-day work of Congress that could meaningfully improve governance. skipped
- H4 Allie Preston
- H6 Fact Sheet: Mandating 21st Century Policing Standards for Federal Immigration Enforcement skipped
- H4 Will Ragland
- H6 Mapping Federal Funding Cuts to U.S. Colleges and Universities skipped
- H4 Mariam Rashid
- H6 The Nature Gap: Communities of Color and Those With Low Incomes Are Bearing the Brunt of America’s Nature Loss skipped
- H4 Dan Restrepo
- H6 Borders, Burdens, and Balance: A Strategic Vision for Migration in the United States and the European Union skipped
- H4 William Roberts
- H6 Trump’s Agenda Is a Direct Threat to the Black Middle Class skipped
- H4 Jill Rosenthal
- H6 The Cost of Measles? The Health of Our Families and Communities. skipped
- H4 Jenny Rowland-Shea
- H6 How the Trump Administration Could Lower Energy Prices and What It Is Doing Instead skipped
- H4 Kat So
- H6 Why Energy Diversification Matters as Extreme Cold Intensifies skipped
- H4 Michael Sozan
- H6 As Americans Deepen Their Nonviolent Mobilization, the Trump Administration Begins To Make Concessions skipped
- H4 Alexandra Thornton
- H6 Congress Must Stop Prediction Market Corruption skipped
- H4 Angelo Villagomez
- H6 Why Alaska and U.S. Territories Get Damage, Not Dollars, From Deep-Sea Mining skipped
- H4 Karla Walter
- H6 Virginia Workers’ Biggest Win in Decades Could Come in 2026 skipped
- H4 Madison Weiss
- H6 CAP Urges the Department of Education To Strengthen Safeguards for Workforce Pell Grants and Protect Students From Low-Value Programs skipped
- H4 Christian E. Weller
- H6 Volatile Job Numbers Mask Stagnant Labor Market in the Trump Administration’s Economy: Analysis of the March 2026 Jobs Report skipped
- H4 Molly Weston Williamson
- H6 Fast Facts About Paid Leave in Virginia skipped
- H4 Mike Williams
- H6 Trading Offshore Wind for LNG: A Lose-Lose for Americans skipped
- H4 Nick Wilson
- H6 Fact Sheet: Mandating 21st Century Policing Standards for Federal Immigration Enforcement skipped
- H4 Donald Berwick
- H6 Kennedy Is Right That America’s Kids Are Unhealthy. But His ‘MAHA’ Report Is the Wrong Medicine. skipped
- H4 Fan Dai
- H4 Jamie Friedman
- H6 Electric and Natural Gas Utility Rate Hikes Tracker skipped
- H4 Glen S. Fukushima
- H6 How Japan can drive faster toward a clean-energy future skipped
- H4 Veronica Goodman
- H6 Moving Federal Education Programs Will Create More Bureaucracy, Not Less skipped
- H4 Chandler Hall
- H6 What City Leaders Say Is Helping Drive Down Gun Violence in Their Communities skipped
- H4 Dan Herman
- H6 The Trump Administration’s ICE and CBP Have Become a Threat to Americans: Congress Must Ensure That DHS Follows the Law and Adopts Commonsense Reforms skipped
- H4 Weadé James
- H6 10 Policy Recommendations To Address Cellphone Use in Schools skipped
- H4 Andrew Miller
- H6 What America Has Lost in the War With Iran skipped
- H4 Ryan Mulholland
- H6 5 Ways the Trump Administration’s War With Iran Is Making It Harder To Make Things in America skipped
- H4 Devon Ombres
- H6 The Trump Administration Has No Legal Authority To Invoke National Security and Take Over Elections skipped
- H4 Sara Partridge
- H6 Stabilizing and Strengthening State Funding for Public Higher Education After the Big Beautiful Bill skipped
- H4 Casey Peeks
- H6 The Trump Administration’s Changes to the Child Care and Development Fund Would Strip Families of Thousands of Dollars in Potential Child Care Savings skipped
- H4 Dave Rank
- H6 Trump and China: An Unprincipled, Impractical, Reactionary Approach to China Policy skipped
- H4 Megan Shahi
- H6 The Senate Republican Budget Bill Adds Broadband Funding That Favors Musk’s Starlink and Bans State AI Laws skipped
- H4 Paige Shoemaker DeMio
- H6 10 Policy Recommendations To Address Cellphone Use in Schools skipped
- H4 Nicole Svajlenka
- H6 DACA Boosts Recipients’ Well-Being and Economic Contributions: 2022 Survey Results skipped
- H4 Steven Woolf
- H6 What the Trump Administration, RFK Jr., and the MAHA Report Got Wrong About Improving Children’s Health skipped
- H4 Sam Zeno
- H6 The Nature Gap: Communities of Color and Those With Low Incomes Are Bearing the Brunt of America’s Nature Loss skipped
- H4 Rosa Barrientos-Ferrer
- H6 The Trump Administration’s ICE and CBP Have Become a Threat to Americans: Congress Must Ensure That DHS Follows the Law and Adopts Commonsense Reforms skipped
- H4 Debu Gandhi
- H6 The Trump Administration’s ICE and CBP Have Become a Threat to Americans: Congress Must Ensure That DHS Follows the Law and Adopts Commonsense Reforms skipped
- H4 Ben Greenho
- H6 The Trump Administration’s ICE and CBP Have Become a Threat to Americans: Congress Must Ensure That DHS Follows the Law and Adopts Commonsense Reforms skipped
- H4 H.A. Hellyer
- H6 Regional Recalibration After the Iran Strikes skipped
- H4 Tom Jawetz
- H6 Vice President Kamala Harris and Migration in the Americas: Setting the Record Straight skipped
- H4 Frank Kendall
- H6 What Both Anthropic and the Pentagon Get Wrong skipped
- H4 Lucero Marquez
- H6 How Climate Change Is Fueling More Deadly and Destructive Floods skipped
- H4 Damian Murphy
- H6 Exporting MAGA Ideology: Why Orbán’s Loss Doesn’t End the Threat Posed by the Extreme Right skipped
- H4 Jessica Ordóñez-Lancet
- H6 Climate Change Is Subjecting More Americans to Unbearable Extreme Heat skipped
- H4 Kyle Ross
- H6 Trump’s War May Be Over But the Economic Damage Is Not skipped
- H4 Chad Maisel
- H6 How to Change the Politics Blocking the Housing We Need skipped
- H4 Steven Kosiak
- H4 Corey Husak
- H6 The Trump Administration’s $1,000 Tax Refund Promise Falls Short by $665 skipped
- H4 Michael Negron
- H6 In the First Year, President Trump’s Tariffs Have Cost Small-Business Importers $306,000 on Average skipped
- H2 National Security
- H4 Exporting MAGA Ideology: Why Orbán’s Loss Doesn’t End the Threat Posed by the Extreme Right skipped
- H4 The Case Against Trump’s War of Choice in Iran
- H4 Iran Spotlights How Trump Is Fracturing the Transatlantic Alliance
- H4 Trump’s Short-Sighted Africa Strategy
- H2 Democracy
- H4 Protecting Constitutional Freedoms of Speech and Assembly During the Second Trump Administration skipped
- H4 As Americans Deepen Their Nonviolent Mobilization, the Trump Administration Begins To Make Concessions
- H4 10 Reasons the Ten Commandments Should Not Be Posted in Public School Classrooms
- H4 The SAVE America Act Explained: How the New ‘Show Your Papers’ Voting Bill Is Even More Extreme Than the SAVE Act
- H4 Trump’s Take
- H2 Education
- H4 Stabilizing and Strengthening State Funding for Public Higher Education After the Big Beautiful Bill skipped
- H4 The Trump Administration’s Changes to the Child Care and Development Fund Would Strip Families of Thousands of Dollars in Potential Child Care Savings
- H4 10 Policy Recommendations To Address Cellphone Use in Schools
- H4 Trump’s Attack on Child Care Funding Undermines Early Educators, Shortchanges Children, and Increases Costs for Families
- H2 Rights and Justice
- H4 What City Leaders Say Is Helping Drive Down Gun Violence in Their Communities skipped
- H4 The Trump Administration’s ICE and CBP Have Become a Threat to Americans: Congress Must Ensure That DHS Follows the Law and Adopts Commonsense Reforms
- H4 The Trump Administration Is Intentionally Erasing the Black History Told by Public Lands and Waters
- H4 Toolkit: Ensuring State Implementation of HHS’ Updated Section 504 Rule
- H4 Democracy Denied for Disabled Americans: Guardianship and the Right To Vote
- H3 InProgress
- H3 Default Opt Ins
- H3 Variable Opt Ins
- H3 InProgress Stay informed on the most pressing issues of our time.
- H3 Default Opt Ins
- H3 Variable Opt Ins
Every page should have one H1 that describes the page content.
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
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
DLink & Button QualityAction2 issue(s) across 398 links and 8 buttonsFIX
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://www.americanprogress.org/cap-pri… | Privacy Policy | new tab | Add '(opens in new tab)' to text |
| https://secure.actblue.com/donate/center… | Donate | new tab | Add '(opens in new tab)' to text |
| https://www.americanprogress.org/issues/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/issues/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/issues/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/issues/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/issues/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://secure.actblue.com/donate/center… | Donate | new tab | Add '(opens in new tab)' to text |
| # | (empty) | empty | Add link text or aria-label |
| https://www.americanprogress.org/article… | Learn more | generic text | Replace with descriptive text |
Before: Learn more Suggested: The Path Forward Ideas Worth Fighting For | |||
| https://www.ms.now/opinion/trump-fed-cha… | The one question Trump’s Fed… | new tab | Add '(opens in new tab)' to text |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/people/… | <img src="https://www.american… | img no alt | Add alt attribute to the image |
| https://www.americanprogress.org/feature… | Trump’s Take | new tab | Add '(opens in new tab)' to text |
| https://twitter.com/amprog | new tab | Add '(opens in new tab)' to text | |
| https://www.facebook.com/americanprogres… | new tab | Add '(opens in new tab)' to text | |
| https://www.youtube.com/user/seeprogress | YouTube | new tab | Add '(opens in new tab)' to text |
| https://www.instagram.com/americanprogre… | new tab | Add '(opens in new tab)' to text | |
| https://www.linkedin.com/company/center-… | new tab | Add '(opens in new tab)' to text | |
| https://bsky.app/profile/americanprogres… | BlueSky | new tab | Add '(opens in new tab)' to text |
| https://www.americanprogressaction.org | CAP Action | new tab | Add '(opens in new tab)' to text |
Links without text are announced as raw URLs by screen readers.
#
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Generic link text like 'click here' doesn't describe the destination.
https://www.americanprogress.org/article/the-path-forward-ideas-worth-fightin… ("Learn more")
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
Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.
a[href="https://www.americanprogress.org/issues/building-an-economy-for-all/"]; a[href="https://www.americanprogress.org/issues/restoring-social-trust-in-democracy/"]; a[href="https://www.americanprogress.org/issues/advancing-racial-equity-and-justice/"]; a[href="https://www.americanprogress.org/issues/tackling-climate-change-and-environme…"]; a[href="https://www.americanprogress.org/issues/strengthening-public-health/"]; a[href="https://www.americanprogress.org/people/amaning-akua/"]; a[href="https://www.americanprogress.org/people/baker-branstetter-shannon/"]; a[href="https://www.americanprogress.org/people/greta-bedekovics/"]; a[href="https://www.americanprogress.org/people/robert-benson/"]; a[href="https://www.americanprogress.org/people/cohen-alan/"] (+73 more)
Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.
Source: WCAG 2.1 SC 2.4.4
Add '(opens in new tab)' to link text or aria-label.
https://www.americanprogress.org/cap-privacy-policy/; https://secure.actblue.com/donate/center-for-american-progress-1?refcode=c3we…; https://secure.actblue.com/donate/center-for-american-progress-1?refcode=c3we…; https://www.ms.now/opinion/trump-fed-chair-kevin-warsh-hearing-question; https://www.americanprogress.org/feature/trumps-take/; https://twitter.com/amprog; https://www.facebook.com/americanprogress; https://www.youtube.com/user/seeprogress; https://www.instagram.com/americanprogress/; https://www.linkedin.com/company/center-for-american-progress/ (+2 more)
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
DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
CLandmark StructureAction4 landmarksREVIEW
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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
Multiple navigations need aria-label to distinguish them for screen readers.
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
CForm AccessibilityAction5 of 88 controls have issuesREVIEW
| Control | Type | Label | Method |
|---|---|---|---|
| #search-form | text | Search | for/id |
| #input_3_1 | Email Address(Required) | for/id | |
| #input_3_32 | text | C3 General | for/id |
| #input_3_6 | text | C3 Events | for/id |
| #input_3_7 | text | C3 Fundraising | for/id |
| #input_3_8 | text | C3 Cultivation | for/id |
| #input_3_9 | text | C3 InProgress | for/id |
| #input_3_33 | text | C3 Digital Contact | for/id |
| #input_3_11 | url | Redirect url | for/id |
| #input_3_12 | url | Post url | for/id |
| #input_3_14 | text | utm_source | for/id |
| #input_3_15 | text | utm_medium | for/id |
| #input_3_16 | text | utm_campaign | for/id |
| #input_3_17 | text | utm_content | for/id |
| #input_3_18 | text | utm_term | for/id |
| #input_3_19 | text | en_txn1 | for/id |
| #input_3_20 | text | en_txn2 | for/id |
| #input_3_21 | text | en_txn3 | for/id |
| #input_3_22 | text | en_txn4 | for/id |
| #input_3_23 | text | en_txn5 | for/id |
| #input_3_24 | text | en_txn6 | for/id |
| #input_3_25 | text | en_txn7 | for/id |
| #input_3_26 | text | en_txn8 | for/id |
| #input_3_27 | text | en_txn9 | for/id |
| #input_3_28 | text | en_txn10 | for/id |
| #input_3_29 | textarea | extra_note | for/id |
| #input_3_34 | text | Opt-in ID | for/id |
| ak_hp_textarea | textarea | Δ | none |
| #input_4_1 | Email Address(Required) | for/id | |
| #input_4_32 | text | C3 General | for/id |
| #input_4_6 | text | C3 Events | for/id |
| #input_4_7 | text | C3 Fundraising | for/id |
| #input_4_8 | text | C3 Cultivation | for/id |
| #input_4_9 | text | C3 InProgress | for/id |
| #input_4_33 | text | C3 Digital Contact | for/id |
| #input_4_11 | url | Redirect url | for/id |
| #input_4_12 | url | Post url | for/id |
| #input_4_14 | text | utm_source | for/id |
| #input_4_15 | text | utm_medium | for/id |
| #input_4_16 | text | utm_campaign | for/id |
| #input_4_17 | text | utm_content | for/id |
| #input_4_18 | text | utm_term | for/id |
| #input_4_19 | text | en_txn1 | for/id |
| #input_4_20 | text | en_txn2 | for/id |
| #input_4_21 | text | en_txn3 | for/id |
| #input_4_22 | text | en_txn4 | for/id |
| #input_4_23 | text | en_txn5 | for/id |
| #input_4_24 | text | en_txn6 | for/id |
| #input_4_25 | text | en_txn7 | for/id |
| #input_4_26 | text | en_txn8 | for/id |
| #input_4_27 | text | en_txn9 | for/id |
| #input_4_28 | text | en_txn10 | for/id |
| #input_4_29 | textarea | extra_note | for/id |
| #input_4_34 | text | Opt-in ID | for/id |
| ak_hp_textarea | textarea | Δ | none |
| #input_5_36 | text | for/id | |
| #input_5_1 | Email Address(Required) | for/id | |
| #input_5_32 | text | C3 General | for/id |
| #input_5_6 | text | C3 Events | for/id |
| #input_5_7 | text | C3 Fundraising | for/id |
| #input_5_8 | text | C3 Cultivation | for/id |
| #input_5_9 | text | C3 InProgress | for/id |
| #input_5_33 | text | C3 Digital Contact | for/id |
| #input_5_11 | url | Redirect url | for/id |
| #input_5_12 | url | Post url | for/id |
| #input_5_14 | text | utm_source | for/id |
| #input_5_15 | text | utm_medium | for/id |
| #input_5_16 | text | utm_campaign | for/id |
| #input_5_17 | text | utm_content | for/id |
| #input_5_18 | text | utm_term | for/id |
| #input_5_19 | text | en_txn1 | for/id |
| #input_5_20 | text | en_txn2 | for/id |
| #input_5_21 | text | en_txn3 | for/id |
| #input_5_22 | text | en_txn4 | for/id |
| #input_5_23 | text | en_txn5 | for/id |
| #input_5_24 | text | en_txn6 | for/id |
| #input_5_25 | text | en_txn7 | for/id |
| #input_5_26 | text | en_txn8 | for/id |
| #input_5_27 | text | en_txn9 | for/id |
| #input_5_28 | text | en_txn10 | for/id |
| #input_5_29 | textarea | extra_note | for/id |
| #input_5_34 | text | Opt-in ID | for/id |
| ak_hp_textarea | textarea | Δ | none |
| #gform_submit_button_4 | submit | (none) | none |
| #gform_submit_button_5 | submit | (none) | none |
| #gform_submit_button_3 | submit | (none) | none |
| #g-recaptcha-response-100000 | textarea | (none) | none |
| #g-recaptcha-response-100001 | textarea | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit" id="gform_submit_button_3">; <input type="submit" id="gform_submit_button_4">; <input type="submit" id="gform_submit_button_5">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100001">
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
B404 Error PageHTTP 404, custom pageREVIEW
BFavicon & Branding7 icon(s) detectedREVIEW
CWeb ManifestActionValid manifestREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 16 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h2 The Path Forward | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| h2 Spotlight | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| h2 Economy | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| h2 Climate | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| h2 Health | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| h2 National Security | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| h2 Democracy | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| h2 Education | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| h2 Rights and Justice | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| h3 Default Opt Ins | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| h3 Variable Opt Ins | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| h3 InProgress | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| h3 Default Opt Ins | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| h3 Variable Opt Ins | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| h3 Default Opt Ins | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| h3 Variable Opt Ins | 1.10:1 | 3.0:1 | #000000 | #100F0F | Fail |
| title Center for American … | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Opens in a new windo… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Opens an external we… | 7.70:1 | 4.5:1 | #000000 | #969DAA | Pass |
| span Opens an external we… | 6.64:1 | 4.5:1 | #000000 | #8B919E | 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+Alt Text Quality1 of 129 images have issuesPASS
| Issue | Count |
|---|---|
| generic | 1 image(s) |
| too long | 1 image(s) |
A+Lighthouse Accessibility AuditsScore 95/100 — 2 failing, 27 passedPASS
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
A Patients’ Bill of Rights To Lower Health Care Costs div.card2-main > div.card2-header > div.card2-inner > h4.card2-title |
What America Has Lost in the War With Iran div.card2-main > div.card2-header > div.card2-inner > h4.card2-title |
The Trump Administration’s Policies Have Hurt Growth, Jobs, and Prices div.card2-main > div.card2-header > div.card2-inner > h4.card2-title |
Climate Change Is Here—and America’s Most Marginalized Communities Are on the F… div.card2-main > div.card2-header > div.card2-inner > h4.card2-title |
Does Medicare Still Cover Durable Medical Equipment? div.card2-main > div.card2-header > div.card2-inner > h4.card2-title |
Fact Sheet: Mandating 21st Century Policing Standards for Federal Immigration E… div.-o:h > div.grid1 > div.card3 > h6.card3-title |
Trump’s War May Be Over But the Economic Damage Is Not div.-o:h > div.grid1 > div.card3 > h6.card3-title |
What the Trump Administration, RFK Jr., and the MAHA Report Got Wrong About Imp… div.-o:h > div.grid1 > div.card3 > h6.card3-title |
A Patients’ Bill of Rights To Lower Health Care Costs div.-o:h > div.grid1 > div.card3 > h6.card3-title |
Regional Recalibration After the Iran Strikes div.-o:h > div.grid1 > div.card3 > h6.card3-title |
Borders, Burdens, and Balance: A Strategic Vision for Migration in the United S… div.-o:h > div.grid1 > div.card3 > h6.card3-title |
Why Energy Diversification Matters as Extreme Cold Intensifies div.-o:h > div.grid1 > div.card3 > h6.card3-title |
Opportunities and Challenges in the Eastern Mediterranean: Examining U.S. Inter… div.-o:h > div.grid1 > div.card3 > h6.card3-title |
Exporting MAGA Ideology: Why Orbán’s Loss Doesn’t End the Threat Posed by the E… div.card2-main > div.card2-header > div.card2-inner > h4.card2-title |
Protecting Constitutional Freedoms of Speech and Assembly During the Second Tru… div.card2-main > div.card2-header > div.card2-inner > h4.card2-title |
Stabilizing and Strengthening State Funding for Public Higher Education After t… div.card2-main > div.card2-header > div.card2-inner > h4.card2-title |
What City Leaders Say Is Helping Drive Down Gun Violence in Their Communities div.card2-main > div.card2-header > div.card2-inner > h4.card2-title |
These are opportunities to improve keyboard navigation in your application.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Bobby Kogan div.card2-main > div.card2-meta > p.card2-authors > a |
Tom Moore div.card2-main > div.card2-meta > p.card2-authors > a |
Bobby Kogan div.card2-main > div.card2-meta > p.card2-authors > a |
Corey Husak div.card2-main > div.card2-meta > p.card2-authors > a |
Jared Bernstein div.card2-main > div.card2-meta > p.card2-authors > a |
Ryan Mulholland div.card2-main > div.card2-meta > p.card2-authors > a |
Kyle Ross div.card2-main > div.card2-meta > p.card2-authors > a |
Alexandra Thornton div.card2-main > div.card2-meta > p.card2-authors > a |
Jill Rosenthal div.card2-main > div.card2-meta > p.card2-authors > a |
Natasha Murphy div.card2-main > div.card2-meta > p.card2-authors > a |
Robert Benson div.card2-main > div.card2-meta > p.card2-authors > a |
Melissa Zelikoff div.card2-main > div.card2-meta > p.card2-authors > a |
Michael Sozan div.card2-main > div.card2-meta > p.card2-authors > a |
Guthrie Graves-Fitzsimmons div.card2-main > div.card2-meta > p.card2-authors > a |
Gréta Bedekovics div.card2-main > div.card2-meta > p.card2-authors > a |
Sara Partridge div.card2-main > div.card2-meta > p.card2-authors > a |
Chandler Hall div.card2-main > div.card2-meta > p.card2-authors > a |
Casey Doherty div.card2-main > div.card2-meta > p.card2-authors > a |
Terms of Use div.footer1-main > ul.footer1-legal > li > a |
Privacy Policy div.footer1-main > ul.footer1-legal > li > a |
CAP - En Español div.footer1-main > ul.footer1-legal > li > a |
Our Supporters div.footer1-main > ul.footer1-legal > li > a |
These items highlight common accessibility best practices.