The White Housewhitehouse.gov
Accessibility Score
Issues Found
Issues Found
SeriousForm elements should have a visible label1 element
The title and aria-describedby attributes provide supplementary hints, not labels. Screen readers treat these as advisory information rather than true labels, which prevents them from properly conveying the form element's purpose. Form fields need proper labels that can be programmatically determined.
Failing Elements
<input type="email" value="" name="EMAIL" placeholder="Your email" title="Your email" required="">
Fix all of the following:
- Only title used to generate label for form element
ModerateLandmarks should have a unique role or role/label/title (i.e. accessible name) combination1 element
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Failing Elements
<nav class="wp-block-whitehouse-header__primary-navigation" data-wp-init="callbacks.initPrimaryNavigation" data-wp-on-async-window--resize="callbacks.handlePrimaryNavigationResize" data-wp-on-async--scroll="callbacks.handlePrimaryNavigationScroll">
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
MinorHeadings should not be empty1 element
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Failing Elements
<h1 class="wp-block-whitehouse-topper__headline"> </h1>
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
Passed Audits
<html> element must have a lang attribute1 element
Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.
Audit Elements
<html lang="en-US">
<html> element must have a valid value for the lang attribute1 element
Screen readers use language-specific sound libraries for proper pronunciation. Invalid language attributes cause screen readers to use the wrong library, making text sound like a confusing accent or completely unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<html lang="en-US">
<li> elements must be contained in a <ul> or <ol>29 elements
Lists require proper semantic hierarchy with ul or ol parent elements and li child elements. This structure allows screen readers to announce when users enter a list, how many items it contains, and which item they're currently on, providing essential context for understanding the content.
Audit Elements
<li id="menu-item-37" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-37"><a href="https://www.whitehouse.gov/news/" data-wp-on-async--mouseenter="callbacks.handlePopoverMenuMouseover" data-wp-on-async--mouseleave="callbacks.handlePopoverMenuMouseout">News</a></li>
<li id="menu-item-33713" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-33713">
<li id="menu-item-33714" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-33714">
<li id="menu-item-33794" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-33794">
<li id="menu-item-35725" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-35725">
<li id="menu-item-39958" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-39958"><a href="https://www.whitehouse.gov/wire/" data-wp-on-async--mouseenter="callbacks.handlePopoverMenuMouseover" data-wp-on-async--mouseleave="callbacks.handlePopoverMenuMouseout">WH Wire</a></li>
<li id="menu-item-33716" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-33716">
<li id="menu-item-33104" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-33104">
<li id="menu-item-22561" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-22561">
<li id="menu-item-33103" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-33103">
Showing first 10 of 29 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements5 elements
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Audit Elements
<ul id="menu-primary-navigation" class="menu menu--desktop">
<ul id="menu-about" class="menu">
<ul id="menu-media" class="menu">
<ul id="menu-initiatives" class="menu">
<ul class="wp-block-social-links is-layout-flex wp-block-social-links-is-layout-flex">
All page content should be contained by landmarks207 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<a class="skip-link screen-reader-text" id="wp-skip-link" href="#wp--skip-link--target">Skip to content</a>
<div class="wp-site-blocks">
<header class="alignfull site-header wp-block-template-part">
<a id="announcement-bar" href="https://www.whitehouse.gov/app" class="announcement-bar--link announcement-bar--marquee">
<div class="announcement-bar__marquee-track" style="animation-duration: 20s;">
<div class="announcement-bar__marquee-content"><span class="announcement-bar__text">Download the Official White House App • Real-Time News • Live Updates • A Direct Line to the Administration →</span></div>
<span class="announcement-bar__text">Download the Official White House App • Real-Time News • Live Updates • A Direct Line to the Administration →</span>
<div class="wp-block-whitehouse-..." data-wp-interactive="whitehouse-header" data-wp-context="{"scrollDirectionThr..." data-wp-init="callbacks.initHeader" data-wp-watch="callbacks.watchHeade..." data-wp-on-async-win...="callbacks.handleWind..." data-wp-on-async-win...="callbacks.handleWind..." ...><div id="wp-block-whitehouse-header-5__main" class="wp-block-whitehouse-header__main">
<div class="wp-block-whitehouse-header__main-content">
Showing first 10 of 207 audited elements.
Alternative text of images should not be repeated as text3 elements
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Audit Elements
<img width="1022" height="1146" src="https://www.whitehou..." class="attachment-large siz..." alt="" loading="lazy" decoding="async" srcset="https://www.whitehou..." sizes="auto, (max-width: 10...">
<img width="419" height="464" src="https://www.whitehouse.gov/wp-content/uploads/2026/01/54986761298_15680bb214_o.jpg?w=419" class="attachment-large size-large" alt="" loading="lazy" decoding="async">
<img fetchpriority="high" decoding="async" width="800" height="450" src="https://www.whitehouse.gov/wp-content/uploads/2026/01/POTUS-Signature-V2-Transparent-11.gif" alt="" class="wp-image-33496" style="width:225px">
ARIA attributes must be used as specified for the element's role7 elements
Using ARIA attributes where they're not expected causes unpredictable behavior in assistive technologies. Following the ARIA specification ensures that screen readers and other tools can properly interpret and communicate your content's meaning to people with disabilities.
Audit Elements
<button class="button-icon" aria-controls="wp-block-whitehouse-..." aria-haspopup="dialog" data-wp-on--click="actions.toggleMenu" data-wp-class--is-ac...="state.isMenuActive" data-wp-bind--aria-e...="callbacks.isMenuActi..." data-wp-bind--title="callbacks.getMenuBut..." title="Open menu">
<button class="button-icon" aria-controls="wp-block-whitehouse-..." aria-haspopup="dialog" data-wp-on--click="actions.toggleSearch" data-wp-class--is-ac...="state.isSearchActive" data-wp-bind--aria-e...="callbacks.isSearchAc..." data-wp-bind--title="callbacks.getSearchB..." title="Open search">
<a href="https://www.whitehouse.gov/priorities/border-immigration/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="secure the border"></a>
<a href="https://www.whitehouse.gov/priorities/economy/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="grow the economy"></a>
<a href="https://www.whitehouse.gov/priorities/national-security/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="Strengthen national security"></a>
<a href="https://www.whitehouse.gov/priorities/energy/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="unleash american energy"></a>
<a href="https://www.whitehouse.gov/priorities/maha/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="make america healthy again"></a>
ARIA attributes must conform to valid names7 elements
Misspelled or non-existent ARIA attributes cannot perform their intended accessibility function. Assistive technologies rely on correctly spelled, current ARIA attributes to convey proper user interface behaviors and structural information to people with disabilities.
Audit Elements
<button class="button-icon" aria-controls="wp-block-whitehouse-..." aria-haspopup="dialog" data-wp-on--click="actions.toggleMenu" data-wp-class--is-ac...="state.isMenuActive" data-wp-bind--aria-e...="callbacks.isMenuActi..." data-wp-bind--title="callbacks.getMenuBut..." title="Open menu">
<button class="button-icon" aria-controls="wp-block-whitehouse-..." aria-haspopup="dialog" data-wp-on--click="actions.toggleSearch" data-wp-class--is-ac...="state.isSearchActive" data-wp-bind--aria-e...="callbacks.isSearchAc..." data-wp-bind--title="callbacks.getSearchB..." title="Open search">
<a href="https://www.whitehouse.gov/priorities/border-immigration/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="secure the border"></a>
<a href="https://www.whitehouse.gov/priorities/economy/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="grow the economy"></a>
<a href="https://www.whitehouse.gov/priorities/national-security/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="Strengthen national security"></a>
<a href="https://www.whitehouse.gov/priorities/energy/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="unleash american energy"></a>
<a href="https://www.whitehouse.gov/priorities/maha/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="make america healthy again"></a>
ARIA attributes must conform to valid values5 elements
ARIA attributes must contain correctly spelled values that match the attribute's expected options. Invalid values prevent the accessibility feature from working, making content inaccessible to assistive technology users who depend on these attributes for navigation and interaction.
Audit Elements
<a href="https://www.whitehouse.gov/priorities/border-immigration/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="secure the border"></a>
<a href="https://www.whitehouse.gov/priorities/economy/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="grow the economy"></a>
<a href="https://www.whitehouse.gov/priorities/national-security/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="Strengthen national security"></a>
<a href="https://www.whitehouse.gov/priorities/energy/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="unleash american energy"></a>
<a href="https://www.whitehouse.gov/priorities/maha/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="make america healthy again"></a>
ARIA hidden element must not be focusable or contain focusable elements38 elements
Elements with aria-hidden="true" are removed from the accessibility API but remain keyboard-focusable, creating confusion about their visibility state. When users tab to these hidden elements, screen readers stay silent, leaving users unaware of what they've focused on or why nothing is being announced.
Audit Elements
<div class="announcement-bar__marquee-content" aria-hidden="true"><span class="announcement-bar__text">Download the Official White House App • Real-Time News • Live Updates • A Direct Line to the Administration →</span></div>
<div class="announcement-bar__marquee-content" aria-hidden="true"><span class="announcement-bar__text">Download the Official White House App • Real-Time News • Live Updates • A Direct Line to the Administration →</span></div>
<span class="menu-item-submenu-indicator" aria-hidden="true"><svg class="menu-item-submenu-indicator-icon" xmlns="http://www.w3.org/2000/svg" width="6" height="7" viewBox="0 0 6 7" fill="none"> <path d="M6 3.5L0.75 6.53109L0.75 0.468911L6 3.5Z" fill="currentColor"></path> </svg></span>
<span class="menu-item-submenu-indicator" aria-hidden="true"><svg class="menu-item-submenu-indicator-icon" xmlns="http://www.w3.org/2000/svg" width="6" height="7" viewBox="0 0 6 7" fill="none"> <path d="M6 3.5L0.75 6.53109L0.75 0.468911L6 3.5Z" fill="currentColor"></path> </svg></span>
<span class="menu-item-submenu-indicator" aria-hidden="true"><svg class="menu-item-submenu-indicator-icon" xmlns="http://www.w3.org/2000/svg" width="6" height="7" viewBox="0 0 6 7" fill="none"> <path d="M6 3.5L0.75 6.53109L0.75 0.468911L6 3.5Z" fill="currentColor"></path> </svg></span>
<span class="menu-item-submenu-indicator" aria-hidden="true"><svg class="menu-item-submenu-indicator-icon" xmlns="http://www.w3.org/2000/svg" width="6" height="7" viewBox="0 0 6 7" fill="none"> <path d="M6 3.5L0.75 6.53109L0.75 0.468911L6 3.5Z" fill="currentColor"></path> </svg></span>
<span class="menu-item-submenu-indicator" aria-hidden="true"><svg class="menu-item-submenu-indicator-icon" xmlns="http://www.w3.org/2000/svg" width="6" height="7" viewBox="0 0 6 7" fill="none"> <path d="M6 3.5L0.75 6.53109L0.75 0.468911L6 3.5Z" fill="currentColor"></path> </svg></span>
<span class="menu-item-submenu-indicator" aria-hidden="true"><svg class="menu-item-submenu-indicator-icon" xmlns="http://www.w3.org/2000/svg" width="6" height="7" viewBox="0 0 6 7" fill="none"> <path d="M6 3.5L0.75 6.53109L0.75 0.468911L6 3.5Z" fill="currentColor"></path> </svg></span>
<span class="menu-item-submenu-indicator" aria-hidden="true"><svg class="menu-item-submenu-indicator-icon" xmlns="http://www.w3.org/2000/svg" width="6" height="7" viewBox="0 0 6 7" fill="none"> <path d="M6 3.5L0.75 6.53109L0.75 0.468911L6 3.5Z" fill="currentColor"></path> </svg></span>
<span class="menu-item-submenu-indicator" aria-hidden="true"><svg class="menu-item-submenu-indicator-icon" xmlns="http://www.w3.org/2000/svg" width="6" height="7" viewBox="0 0 6 7" fill="none"> <path d="M6 3.5L0.75 6.53109L0.75 0.468911L6 3.5Z" fill="currentColor"></path> </svg></span>
Showing first 10 of 38 audited elements.
ARIA role should be appropriate for the element2 elements
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Audit Elements
<form role="search" method="get" action="https://www.whitehouse.gov">
<div id="wp-block-whitehouse-header-5__menu" class="wp-block-whitehouse-header__menu" role="dialog" data-wp-init="callbacks.initMenu" data-wp-watch="callbacks.watchMenu" data-wp-class--is-active="state.isMenuActive">
aria-hidden="true" must not be present on the document body1 element
Setting <body aria-hidden="true" hides all page content from assistive technologies while leaving it visible on screen. This creates a confusing experience where keyboard users can still tab to elements, but screen readers remain completely silent, providing no information about what's focused.
Audit Elements
<body class="home wp-singular page-template-default page page-id-2 wp-embed-responsive wp-theme-whitehouse remove-content-margins has-immersive-header has-topper has-notification-bar has-dynamic-announcement-bar" id="top" style="--wh-scrollbar-width-max: 0px; --wh-scrollbar-width: 0px;">
Banner landmark should not be contained in another landmark1 element
Banner landmarks must be top-level to effectively designate the header portion of the page. Nested banner landmarks fail to provide the structural information screen reader users need to navigate efficiently through the page layout.
Audit Elements
<header class="alignfull site-header wp-block-template-part">
Buttons must have discernible text2 elements
Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.
Audit Elements
<button class="button-icon" aria-controls="wp-block-whitehouse-..." aria-haspopup="dialog" data-wp-on--click="actions.toggleMenu" data-wp-class--is-ac...="state.isMenuActive" data-wp-bind--aria-e...="callbacks.isMenuActi..." data-wp-bind--title="callbacks.getMenuBut..." title="Open menu">
<button class="button-icon" aria-controls="wp-block-whitehouse-..." aria-haspopup="dialog" data-wp-on--click="actions.toggleSearch" data-wp-class--is-ac...="state.isSearchActive" data-wp-bind--aria-e...="callbacks.isSearchAc..." data-wp-bind--title="callbacks.getSearchB..." title="Open search">
Contentinfo landmark should not be contained in another landmark1 element
The contentinfo landmark must be at the top level to help screen reader users quickly navigate to footer information. When nested inside another landmark, it becomes harder to find, defeating its purpose of providing quick access to content information.
Audit Elements
<footer class="alignfull site-footer wp-block-template-part">
Document should have one main landmark1 element
Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.
Audit Elements
<html lang="en-US">
Document should not have more than one banner landmark1 element
Multiple banner landmarks force screen reader users to sort through duplicate options to find header information. Each page should have only one banner landmark to enable quick, predictable navigation to the header without overwhelming users with unnecessary choices.
Audit Elements
<header class="alignfull site-header wp-block-template-part">
Document should not have more than one contentinfo landmark1 element
Multiple contentinfo landmarks force screen reader users to sort through extra options to find footer information. Each page should have only one content info landmark to enable quick, predictable navigation without overwhelming users with duplicate structural markers.
Audit Elements
<footer class="alignfull site-footer wp-block-template-part">
Document should not have more than one main landmark1 element
Multiple main landmarks confuse screen reader users about where the primary content is located. Each page should have only one main landmark so users can quickly and predictably navigate to the primary content area.
Audit Elements
<main class="wp-block-group site-content is-layout-flow wp-block-group-is-layout-flow" id="wp--skip-link--target">
Documents must have <title> element to aid in navigation1 element
The page title is the first thing screen reader users hear when loading a page. Without a descriptive, unique title, users must read through the entire page to understand its contents and purpose, wasting valuable time on every page visit.
Audit Elements
<html lang="en-US">
Elements marked as presentational should be consistently ignored3 elements
Elements with role="none" or role="presentation" should be removed from the accessibility tree. Adding global ARIA attributes or making these elements focusable prevents their removal, leaving them accessible to screen readers when they should be ignored, creating unexpected and confusing behavior.
Audit Elements
<img width="1022" height="1146" src="https://www.whitehou..." class="attachment-large siz..." alt="" loading="lazy" decoding="async" srcset="https://www.whitehou..." sizes="auto, (max-width: 10...">
<img width="419" height="464" src="https://www.whitehouse.gov/wp-content/uploads/2026/01/54986761298_15680bb214_o.jpg?w=419" class="attachment-large size-large" alt="" loading="lazy" decoding="async">
<img fetchpriority="high" decoding="async" width="800" height="450" src="https://www.whitehouse.gov/wp-content/uploads/2026/01/POTUS-Signature-V2-Transparent-11.gif" alt="" class="wp-image-33496" style="width:225px">
Elements must meet minimum color contrast ratio thresholds29 elements
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Audit Elements
<span class="announcement-bar__text">Download the Official White House App • Real-Time News • Live Updates • A Direct Line to the Administration →</span>
<span class="announcement-bar__text">Download the Official White House App • Real-Time News • Live Updates • A Direct Line to the Administration →</span>
<input type="search" id="wp-block-whitehouse-header-5__search-input" class="wp-block-whitehouse-header__search-input" value="" name="s" title="Search for:">
<h2 class="wp-block-whitehouse-footer__menu-heading">About</h2>
<a href="https://www.whitehouse.gov/administration/" data-wp-on-async--mouseenter="callbacks.handlePopoverMenuMouseover" data-wp-on-async--mouseleave="callbacks.handlePopoverMenuMouseout">Administration</a>
<a href="https://www.whitehouse.gov/contact/" data-wp-on-async--mouseenter="callbacks.handlePopoverMenuMouseover" data-wp-on-async--mouseleave="callbacks.handlePopoverMenuMouseout">Contact</a>
<a href="https://www.whitehouse.gov/internships/" data-wp-on-async--mouseenter="callbacks.handlePopoverMenuMouseover" data-wp-on-async--mouseleave="callbacks.handlePopoverMenuMouseout">Internships</a>
<a target="_blank" rel="noopener" href="https://www.whitehouse.gov/subscribe" data-wp-on-async--mouseenter="callbacks.handlePopoverMenuMouseover" data-wp-on-async--mouseleave="callbacks.handlePopoverMenuMouseout">Stay Informed</a>
<a href="https://www.whitehouse.gov/privacy/" data-wp-on-async--mouseenter="callbacks.handlePopoverMenuMouseover" data-wp-on-async--mouseleave="callbacks.handlePopoverMenuMouseout">Privacy Policy</a>
<h2 class="wp-block-whitehouse-footer__menu-heading">Media</h2>
Showing first 10 of 29 audited elements.
Elements must only use permitted ARIA attributes7 elements
Using prohibited ARIA attributes prevents important information from reaching assistive technology users. It also causes assistive technologies to behave inconsistently as they attempt to compensate for the error.
Audit Elements
<button class="button-icon" aria-controls="wp-block-whitehouse-..." aria-haspopup="dialog" data-wp-on--click="actions.toggleMenu" data-wp-class--is-ac...="state.isMenuActive" data-wp-bind--aria-e...="callbacks.isMenuActi..." data-wp-bind--title="callbacks.getMenuBut..." title="Open menu">
<button class="button-icon" aria-controls="wp-block-whitehouse-..." aria-haspopup="dialog" data-wp-on--click="actions.toggleSearch" data-wp-class--is-ac...="state.isSearchActive" data-wp-bind--aria-e...="callbacks.isSearchAc..." data-wp-bind--title="callbacks.getSearchB..." title="Open search">
<a href="https://www.whitehouse.gov/priorities/border-immigration/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="secure the border"></a>
<a href="https://www.whitehouse.gov/priorities/economy/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="grow the economy"></a>
<a href="https://www.whitehouse.gov/priorities/national-security/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="Strengthen national security"></a>
<a href="https://www.whitehouse.gov/priorities/energy/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="unleash american energy"></a>
<a href="https://www.whitehouse.gov/priorities/maha/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="make america healthy again"></a>
Elements must only use supported ARIA attributes7 elements
Using ARIA attributes in roles where they're not allowed can disable accessibility for entire sections of your application. Invalid attribute-role combinations create conflicts that cause assistive technologies to report incorrect or nonsensical information about your interface.
Audit Elements
<button class="button-icon" aria-controls="wp-block-whitehouse-..." aria-haspopup="dialog" data-wp-on--click="actions.toggleMenu" data-wp-class--is-ac...="state.isMenuActive" data-wp-bind--aria-e...="callbacks.isMenuActi..." data-wp-bind--title="callbacks.getMenuBut..." title="Open menu">
<button class="button-icon" aria-controls="wp-block-whitehouse-..." aria-haspopup="dialog" data-wp-on--click="actions.toggleSearch" data-wp-class--is-ac...="state.isSearchActive" data-wp-bind--aria-e...="callbacks.isSearchAc..." data-wp-bind--title="callbacks.getSearchB..." title="Open search">
<a href="https://www.whitehouse.gov/priorities/border-immigration/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="secure the border"></a>
<a href="https://www.whitehouse.gov/priorities/economy/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="grow the economy"></a>
<a href="https://www.whitehouse.gov/priorities/national-security/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="Strengthen national security"></a>
<a href="https://www.whitehouse.gov/priorities/energy/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="unleash american energy"></a>
<a href="https://www.whitehouse.gov/priorities/maha/" class="wp-block-whitehouse-video-accordion-item__link" aria-label="make america healthy again"></a>
Elements should not have tabindex greater than zero5 elements
Using tabindex values greater than 0 creates unexpected tab orders that disorient users. It makes elements appear to be skipped when users tab past them, requires setting tabindex on every element to maintain order, and forces all tabindex items to be visited before any normal elements, breaking natural navigation flow.
Audit Elements
<video src="https://www.whitehouse.gov/wp-content/uploads/2026/01/Wide_Border-Security1.mp4#t=0.1" preload="metadata" style="object-position:50% 30%;" muted="" loop="" playsinline="" tabindex="-1"></video>
<video src="https://www.whitehouse.gov/wp-content/uploads/2026/01/Wide_Site_Economy_03.mov#t=0.1" preload="metadata" style="object-position:50% 30%;" muted="" loop="" playsinline="" tabindex="-1"></video>
<video src="https://www.whitehouse.gov/wp-content/uploads/2026/01/Wide_Site_National-Security_03.mov#t=0.1" preload="metadata" style="object-position:49% 28%;" muted="" loop="" playsinline="" tabindex="-1"></video>
<video src="https://www.whitehouse.gov/wp-content/uploads/2025/04/Energy.mov#t=0.1" preload="metadata" style="object-position:47% 67%;" muted="" loop="" playsinline="" tabindex="-1"></video>
<video src="https://www.whitehouse.gov/wp-content/uploads/2026/01/Wide_Site_MAHA-031.mp4#t=0.1" preload="metadata" style="object-position:50% 40%;" muted="" loop="" playsinline="" tabindex="-1"></video>
Form elements must have labels1 element
Form labels are essential for screen reader users to understand what information each field requires. Without proper labels, screen readers cannot identify input expectations, fields don't receive focus when announced, and users with motor impairments lose the benefit of larger clickable areas that labels provide.
Audit Elements
<input type="email" value="" name="EMAIL" placeholder="Your email" title="Your email" required="">
Form field must not have multiple label elements1 element
Multiple labels on the same form field cause inconsistent behavior across screen reader and browser combinations. Some will read the first label, others the last, and some will read both, creating confusion about what information the field requires.
Audit Elements
<input type="email" value="" name="EMAIL" placeholder="Your email" title="Your email" required="">
Heading levels should only increase by one11 elements
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h1 class="wp-block-whitehouse-topper__headline"> </h1>
<h2 class="wp-block-heading has-text-align-center" style="font-size:30px">Donald J. Trump</h2>
<h3 class="wp-block-whitehouse-video-accordion-item__title">
<h3 class="wp-block-whitehouse-video-accordion-item__title">
<h3 class="wp-block-whitehouse-video-accordion-item__title">
<h3 class="wp-block-whitehouse-video-accordion-item__title">
<h3 class="wp-block-whitehouse-video-accordion-item__title">
<h2 class="wp-block-whitehouse-footer__menu-heading">About</h2>
<h2 class="wp-block-whitehouse-footer__menu-heading">Media</h2>
<h2 class="wp-block-whitehouse-footer__menu-heading">Initiatives</h2>
Showing first 10 of 11 audited elements.
Headings should not be empty10 elements
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h2 class="wp-block-heading has-text-align-center" style="font-size:30px">Donald J. Trump</h2>
<h3 class="wp-block-whitehouse-video-accordion-item__title">
<h3 class="wp-block-whitehouse-video-accordion-item__title">
<h3 class="wp-block-whitehouse-video-accordion-item__title">
<h3 class="wp-block-whitehouse-video-accordion-item__title">
<h3 class="wp-block-whitehouse-video-accordion-item__title">
<h2 class="wp-block-whitehouse-footer__menu-heading">About</h2>
<h2 class="wp-block-whitehouse-footer__menu-heading">Media</h2>
<h2 class="wp-block-whitehouse-footer__menu-heading">Initiatives</h2>
<h3 class="wp-block-whitehouse-footer__newsletter-heading wp-block-heading">Subscribe to the WH Newsletter</h3>
IDs used in ARIA and labels must be unique4 elements
Duplicate IDs break the accessibility of ARIA elements, form labels, and table headers. When IDs are duplicated, assistive technologies and scripts only reference the first instance, causing subsequent elements with the same ID to be ignored or incorrectly associated.
Audit Elements
<search id="wp-block-whitehouse-header-5__search" class="wp-block-whitehouse-header__search" role="dialog" data-wp-init="callbacks.initSearch" data-wp-watch="callbacks.watchSearch" data-wp-class--is-active="state.isSearchActive">
<input type="search" id="wp-block-whitehouse-header-5__search-input" class="wp-block-whitehouse-header__search-input" value="" name="s" title="Search for:">
<div id="wp-block-whitehouse-header-5__menu" class="wp-block-whitehouse-header__menu" role="dialog" data-wp-init="callbacks.initMenu" data-wp-watch="callbacks.watchMenu" data-wp-class--is-active="state.isMenuActive">
<input type="text" name="b_255057cc391ca0facb169b81c_004f59aa22" tabindex="-1" value="" id="mailchimp-signup-form-6">
Images must have alternative text3 elements
Screen readers cannot translate images into text without alt attributes. Alternative text is essential for blind users and beneficial for users with low vision or color blindness, providing the same information that sighted users get from viewing the image.
Audit Elements
<img width="1022" height="1146" src="https://www.whitehou..." class="attachment-large siz..." alt="" loading="lazy" decoding="async" srcset="https://www.whitehou..." sizes="auto, (max-width: 10...">
<img width="419" height="464" src="https://www.whitehouse.gov/wp-content/uploads/2026/01/54986761298_15680bb214_o.jpg?w=419" class="attachment-large size-large" alt="" loading="lazy" decoding="async">
<img fetchpriority="high" decoding="async" width="800" height="450" src="https://www.whitehouse.gov/wp-content/uploads/2026/01/POTUS-Signature-V2-Transparent-11.gif" alt="" class="wp-image-33496" style="width:225px">
Inline text spacing must be adjustable with custom stylesheets9 elements
Single-spaced text makes it difficult for people with cognitive disabilities to track lines while reading. Providing line spacing between 1.5 to 2 helps these users start a new line more easily after finishing the previous one.
Audit Elements
<body class="home wp-singular page-template-default page page-id-2 wp-embed-responsive wp-theme-whitehouse remove-content-margins has-immersive-header has-topper has-notification-bar has-dynamic-announcement-bar" id="top" style="--wh-scrollbar-width-max: 0px; --wh-scrollbar-width: 0px;">
<div class="announcement-bar__marquee-track" style="animation-duration: 20s;">
<div style="--wh--video-accordio..." class="is-vertical alignful..." data-show-title="both">
<video src="https://www.whitehouse.gov/wp-content/uploads/2026/01/Wide_Border-Security1.mp4#t=0.1" preload="metadata" style="object-position:50% 30%;" muted="" loop="" playsinline="" tabindex="-1"></video>
<video src="https://www.whitehouse.gov/wp-content/uploads/2026/01/Wide_Site_Economy_03.mov#t=0.1" preload="metadata" style="object-position:50% 30%;" muted="" loop="" playsinline="" tabindex="-1"></video>
<video src="https://www.whitehouse.gov/wp-content/uploads/2026/01/Wide_Site_National-Security_03.mov#t=0.1" preload="metadata" style="object-position:49% 28%;" muted="" loop="" playsinline="" tabindex="-1"></video>
<video src="https://www.whitehouse.gov/wp-content/uploads/2025/04/Energy.mov#t=0.1" preload="metadata" style="object-position:47% 67%;" muted="" loop="" playsinline="" tabindex="-1"></video>
<video src="https://www.whitehouse.gov/wp-content/uploads/2026/01/Wide_Site_MAHA-031.mp4#t=0.1" preload="metadata" style="object-position:50% 40%;" muted="" loop="" playsinline="" tabindex="-1"></video>
<span style="color: #FF0000">45470</span>
Input buttons must have discernible text1 element
Screen reader users cannot understand an input type="button"'s purpose without an accessible name. Unnamed button images provide no description of their destination, purpose, or function, leaving users unable to make informed decisions about activating them.
Audit Elements
<input type="submit" value="Sign Up" class="wp-element-button">
Interactive controls must not be nested3 elements
Nested interactive elements create empty tab stops where screen readers remain silent. When users tab to a focusable element inside another interactive control, they receive no information about its name, role, or state, creating a confusing and broken navigation experience.
Audit Elements
<button class="button-icon" aria-controls="wp-block-whitehouse-..." aria-haspopup="dialog" data-wp-on--click="actions.toggleMenu" data-wp-class--is-ac...="state.isMenuActive" data-wp-bind--aria-e...="callbacks.isMenuActi..." data-wp-bind--title="callbacks.getMenuBut..." title="Open menu">
<button class="button-icon" aria-controls="wp-block-whitehouse-..." aria-haspopup="dialog" data-wp-on--click="actions.toggleSearch" data-wp-class--is-ac...="state.isSearchActive" data-wp-bind--aria-e...="callbacks.isSearchAc..." data-wp-bind--title="callbacks.getSearchB..." title="Open search">
<input type="submit" value="Sign Up" class="wp-element-button">
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination3 elements
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Audit Elements
<header class="alignfull site-header wp-block-template-part">
<main class="wp-block-group site-content is-layout-flow wp-block-group-is-layout-flow" id="wp--skip-link--target">
<footer class="alignfull site-footer wp-block-template-part">
Links must be distinguishable without relying on color1 element
People with low vision or color blindness cannot visually distinguish links from surrounding text without sufficient color contrast (3:1 ratio minimum). When link colors are too similar to regular text, users with visual impairments cannot identify which text is clickable.
Audit Elements
<a href="https://my.community.com/realdonaldtrump?t=VICTORY" target="_blank" rel="noopener">Click here</a>
Links must have discernible text41 elements
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Audit Elements
<a class="skip-link screen-reader-text" id="wp-skip-link" href="#wp--skip-link--target">Skip to content</a>
<a id="announcement-bar" href="https://www.whitehouse.gov/app" class="announcement-bar--link announcement-bar--marquee">
<a class="wp-block-whitehouse-header__logo" href="https://www.whitehouse.gov" rel="home" title="The White House">
<a href="https://www.whitehouse.gov/news/" data-wp-on-async--mouseenter="callbacks.handlePopoverMenuMouseover" data-wp-on-async--mouseleave="callbacks.handlePopoverMenuMouseout">News</a>
<a href="https://www.whitehouse.gov/gallery/" data-wp-on-async--mouseenter="callbacks.handlePopoverMenuMouseover" data-wp-on-async--mouseleave="callbacks.handlePopoverMenuMouseout">Gallery</a>
<a href="https://www.whitehouse.gov/live/" data-wp-on-async--mouseenter="callbacks.handlePopoverMenuMouseover" data-wp-on-async--mouseleave="callbacks.handlePopoverMenuMouseout">Livestream</a>
<a href="https://www.whitehouse.gov/investments/" data-wp-on-async--mouseenter="callbacks.handlePopoverMenuMouseover" data-wp-on-async--mouseleave="callbacks.handlePopoverMenuMouseout">Investments</a>
<a href="https://www.whitehouse.gov/saveamerica/" data-wp-on-async--mouseenter="callbacks.handlePopoverMenuMouseover" data-wp-on-async--mouseleave="callbacks.handlePopoverMenuMouseout">SAVE America</a>
<a href="https://www.whitehouse.gov/wire/" data-wp-on-async--mouseenter="callbacks.handlePopoverMenuMouseover" data-wp-on-async--mouseleave="callbacks.handlePopoverMenuMouseout">WH Wire</a>
<a href="https://www.whitehouse.gov/contact/" data-wp-on-async--mouseenter="callbacks.handlePopoverMenuMouseover" data-wp-on-async--mouseleave="callbacks.handlePopoverMenuMouseout">Contact</a>
Showing first 10 of 41 audited elements.
Main landmark should not be contained in another landmark1 element
The main landmark must be at the top level and not nested inside other landmarks. This ensures screen reader users can quickly navigate to the primary content without searching through complex hierarchy, making page navigation simpler and more predictable.
Audit Elements
<main class="wp-block-group site-content is-layout-flow wp-block-group-is-layout-flow" id="wp--skip-link--target">
Page must have means to bypass repeated blocks1 element
Keyboard-only users must tab through all navigation and header content before reaching the main content, which can take several minutes and cause physical pain for users with motor limitations. Bypass mechanisms like skip links allow these users to jump directly to main content, saving time and reducing fatigue.
Audit Elements
<html lang="en-US">
Page should contain a level-one heading1 element
Screen reader users use keyboard shortcuts to jump directly to the first h1, expecting to land at the main content. Without an h1 or with a misplaced one, users must listen to more of the page to understand its structure, wasting valuable time on every page visit.
Audit Elements
<html lang="en-US">
The skip-link target should exist and be focusable1 element
Skip links allow keyboard users to bypass repetitive navigation and jump directly to main content. Without skip links, users must tab through potentially hundreds of navigation links on every page, which is time-consuming and can cause physical pain for users with motor limitations.
Audit Elements
<a class="skip-link screen-reader-text" id="wp-skip-link" href="#wp--skip-link--target">Skip to content</a>
Users should be able to zoom and scale the text up to 500%1 element
The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1">
Zooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1">