Bloomberg bloomberg.com
Accessibility score
League position
8thof 10
Issues found
6
Audits passed
50
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
CriticalButtons must have discernible text1 element
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.
Failing Elements
<button type="button" class="media-ui-Button_butt..." data-component="rounded-button" title="" name="roundedButton" aria-label="">
Fix any of the following:
- Element does not have inner 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 an empty title attribute
- Element does not have an implicit (wrapped) <label>
- Element does not have an explicit <label>
- Element's default semantics were not overridden with role="none" or role="presentation"
CriticalImages must have alternative text1 element
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.
Failing Elements
<img src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/iZvxdLe_Nw0o/v0/96x96.jpg" data-component="image" loading="lazy">
Fix any of the following:
- Element does not have an alt attribute
- 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
- Element's default semantics were not overridden with role="none" or role="presentation"
SeriousText must remain readable when spacing is increased7 elements
People with low vision and dyslexia increase line height, letter spacing, word spacing, and paragraph spacing so they can read. Fixed-height boxes and overflow: hidden containers clip or overlap that text, which is a loss of content under WCAG 1.4.12.
Failing Elements
<div class="PlayIconWithDuration_duration__4Siw4">
<div class="PlayIconWithDuration_duration__4Siw4">
<div class="PlayIconWithDuration_duration__4Siw4">
<h3 id=":Rr2eqel9l6:" class="intercom-video-card_videoCardTitle-Ey1CXsBv-50- cs...">
<h3 id=":R1r2eqel9l6:" class="intercom-video-card_videoCardTitle-Ey1CXsBv-50- cs...">
<h3 id=":R3b2eqel9l6:" class="intercom-video-card_videoCardTitle-Ey1CXsBv-50- cs...">
<h3 id=":R3r2eqel9l6:" class="intercom-video-card_videoCardTitle-Ey1CXsBv-50- cs...">
ModerateLandmarks should have a unique role or role/label/title (i.e. accessible name) combination4 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.
Failing Elements
<nav class="bb-that">
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
<div id="skylight-vod-2179b6a..." poster="https://assets.bwbx...." class="video-js vjs-fluid s..." tabindex="-1" lang="en" translate="no" role="region" aria-label="Video Player">
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
<div tabindex="-1" role="region" aria-live="polite" aria-atomic="false" aria-relevant="additions text" aria-label="Notifications"></div>
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
<div class="media-ui-BaseAd_base..." data-component="immersive-ad" data-ad-status="rendering" role="region" aria-label="Immersive advertisem..." aria-busy="true">
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
ModerateAll page content should be contained by landmarks2 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.
Failing Elements
<h2 style="font-weight: bold; font-size: 18px; margin-bottom: 5px;">We've updated our terms</h2>
Fix any of the following:
- Some page content is not contained by landmarks
<p>
Fix any of the following:
- Some page content is not contained by landmarks
MinorAlternative text of images should not be repeated as text13 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.
Failing Elements
<img class="atomics-Image-root s..." data-component="Image" loading="eager" data-has-height="" data-has-width="" src="https://assets.bwbx...." alt="Insolvent Australian..." srcset="https://assets.bwbx...." sizes="100px" style="--_atomics-Image-hei...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img class="atomics-Image-root s..." data-component="Image" loading="eager" data-has-height="" data-has-width="" src="https://assets.bwbx...." alt="Canada Loses 41,700 ..." srcset="https://assets.bwbx...." sizes="100px" style="--_atomics-Image-hei...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img class="atomics-Image-root s..." data-component="Image" loading="eager" data-has-height="" data-has-width="" src="https://assets.bwbx...." alt="Morgan Stanley Banke..." srcset="https://assets.bwbx...." sizes="100px" style="--_atomics-Image-hei...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img class="atomics-Image-root s..." data-component="Image" loading="eager" data-has-height="" data-has-width="" src="https://assets.bwbx...." alt="AI Startup That Upen..." srcset="https://assets.bwbx...." sizes="100px" style="--_atomics-Image-hei...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img class="atomics-Image-root s..." data-component="Image" loading="eager" data-has-height="" data-has-width="" src="https://assets.bwbx...." alt="Point72 Seeks to Dou..." srcset="https://assets.bwbx...." sizes="100px" style="--_atomics-Image-hei...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img class="atomics-Image-root s..." data-component="Image" loading="eager" data-has-height="" data-has-width="" src="https://assets.bwbx...." alt="Ingenia Shares Surge..." srcset="https://assets.bwbx...." sizes="100px" style="--_atomics-Image-hei...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img class="atomics-Image-root s..." data-component="Image" loading="eager" data-has-height="" data-has-width="" src="https://assets.bwbx...." alt="War-Tested Oil Trade..." srcset="https://assets.bwbx...." sizes="100px" style="--_atomics-Image-hei...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img class="atomics-Image-root s..." data-component="Image" loading="eager" data-has-height="" data-has-width="" src="https://assets.bwbx...." alt="Peso Left Behind in ..." srcset="https://assets.bwbx...." sizes="100px" style="--_atomics-Image-hei...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img class="atomics-Image-root s..." data-component="Image" loading="eager" data-has-height="" data-has-width="" src="https://assets.bwbx...." alt="NZ’s National Vows t..." srcset="https://assets.bwbx...." sizes="100px" style="--_atomics-Image-hei...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img class="atomics-Image-root s..." data-component="Image" loading="eager" data-has-height="" data-has-width="" src="https://assets.bwbx...." alt="EM Stocks Jump to 2-..." srcset="https://assets.bwbx...." sizes="100px" style="--_atomics-Image-hei...">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
Showing first 10 of 13 failing elements.
Passed audits50 across 1 page
<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">
<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">
<li> elements must be contained in a <ul> or <ol>66 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 aria-label="Markets" class="nav-ui-MenuDesktop__menuItem__TWVud" data-menuid="markets">
<li aria-label="Finance" class="nav-ui-MenuDesktop__menuItem__TWVud" data-menuid="finance"><a href="https://www.bloomberg.com/finance">Finance</a></li>
<li aria-label="Economics" class="nav-ui-MenuDesktop__menuItem__TWVud" data-menuid="economics"><a href="https://www.bloomberg.com/economics">Economics</a></li>
<li aria-label="Industries" class="nav-ui-MenuDesktop__menuItem__TWVud" data-menuid="industries"><a href="https://www.bloomberg.com/industries">Industries</a></li>
<li aria-label="Tech" class="nav-ui-MenuDesktop__menuItem__TWVud" data-menuid="tech"><a href="https://www.bloomberg.com/technology">Tech</a></li>
Showing first 5 of 66 audited elements.
<svg> elements with an img or image role must have alternative text24 elements
SVG images need text alternatives so their information can be accessed through any sensory modality - visual, auditory, or tactile. Text alternatives enable screen readers to convert visual information into speech or braille, support future translation into sign language, and ensure content is accessible regardless of a user's sensory abilities.
Audit Elements
<svg width="100%" height="100%" version="1.1" viewBox="429.6 479.5 476.4 96.1" xmlns="http://www.w3.org/2000/svg" role="img" fill="currentColor" aria-label="Bloomberg" data-component="bloombergLogo">
<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="Search">
<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" aria-label="Chevron Down" role="img">
<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" aria-label="Chevron Down" role="img">
<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" aria-label="Chevron Down" role="img">
Showing first 5 of 24 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements11 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 class="nav-ui-MenuDesktop__menuItemsContainer__TWVud">
<ul class="intercom-carousel_iterableComponentsContainer-DQkh-K22P0c-" style="gap: 12px; --transition-duration: 300ms; --touch-transition-duration: 200ms;">
<ul class="atomics-List-root List__list__TGlzd" data-list-variant="unstyled" data-testid="list">
<ul class="atomics-List-root List__list__TGlzd" data-list-variant="unstyled" data-testid="list">
<ul class="atomics-List-root List__list__TGlzd" data-list-variant="unstyled" data-testid="list">
Showing first 5 of 11 audited elements.
All page content should be contained by landmarks2561 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
<div>
<div>
<div id="__next">
<main>
<div data-page-type="lineup-curation">
Showing first 5 of 2561 audited elements.
Alternative text of images should not be repeated as text110 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 src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/ihrP.bKBqSxg/v0/600x400.jpg" data-component="image" alt="Iran, US Trade Tanker Attacks as Six-Month Conflict Escalates" loading="eager">
<img src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/ifSq1fyZowRo/v0/715x477.jpg" data-component="image" alt="Yuan Banknotes as China Boosts Yuan Support as Dollar Strength Pressures Asia" loading="lazy">
<img loading="lazy" alt="" src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/i.0CCamjZbB0/v3/640x-1.webp">
<img src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/iLQLWzzFD2HM/v1/600x400.jpg" data-component="image" alt="Spanish Solar Park Operated by Zelestra Corp. SA" loading="eager">
<img src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/ijWc5wAiYmH0/v0/72x72.png" data-component="image" alt="Europe Looks Back at a Summer of Record Heat as El Niño Looms in 2027" loading="eager">
Showing first 5 of 110 audited elements.
ARIA attributes must be used as specified for the element's role146 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
<div class="media-ui-BaseAd_base..." data-component="leaderboard-ad" data-ad-status="rendered" role="region" aria-label="Leaderboard advertis..." aria-busy="false" data-ad-size="970x250">
<iframe id="google_ads_iframe_/5..." name="google_ads_iframe_/5..." title="3rd party ad content" width="970" height="250" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
<a href="#that-jump-content" class="bb-that__skip-to-content" aria-label="Skip to content" role="button" tabindex="0">Skip to content</a>
<a class="bb-that-header__link..." href="https://www.bloomber..." role="button" aria-controls="bb-that--container" aria-expanded="false" data-element="tophat-link" data-description="Bloomberg the Compan..." data-label="bcom">
<div aria-label="logo" class="nav-ui-Logo__logo__TG9nb nav-ui-Logo__dark__TG9nb" data-component="logo">
Showing first 5 of 146 audited elements.
ARIA attributes must conform to valid names146 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
<div class="media-ui-BaseAd_base..." data-component="leaderboard-ad" data-ad-status="rendered" role="region" aria-label="Leaderboard advertis..." aria-busy="false" data-ad-size="970x250">
<iframe id="google_ads_iframe_/5..." name="google_ads_iframe_/5..." title="3rd party ad content" width="970" height="250" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
<a href="#that-jump-content" class="bb-that__skip-to-content" aria-label="Skip to content" role="button" tabindex="0">Skip to content</a>
<a class="bb-that-header__link..." href="https://www.bloomber..." role="button" aria-controls="bb-that--container" aria-expanded="false" data-element="tophat-link" data-description="Bloomberg the Compan..." data-label="bcom">
<div aria-label="logo" class="nav-ui-Logo__logo__TG9nb nav-ui-Logo__dark__TG9nb" data-component="logo">
Showing first 5 of 146 audited elements.
ARIA attributes must conform to valid values145 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
<div class="media-ui-BaseAd_base..." data-component="leaderboard-ad" data-ad-status="rendered" role="region" aria-label="Leaderboard advertis..." aria-busy="false" data-ad-size="970x250">
<iframe id="google_ads_iframe_/5..." name="google_ads_iframe_/5..." title="3rd party ad content" width="970" height="250" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
<a href="#that-jump-content" class="bb-that__skip-to-content" aria-label="Skip to content" role="button" tabindex="0">Skip to content</a>
<a class="bb-that-header__link..." href="https://www.bloomber..." role="button" aria-controls="bb-that--container" aria-expanded="false" data-element="tophat-link" data-description="Bloomberg the Compan..." data-label="bcom">
<div aria-label="logo" class="nav-ui-Logo__logo__TG9nb nav-ui-Logo__dark__TG9nb" data-component="logo">
Showing first 5 of 145 audited elements.
ARIA commands must have an accessible name7 elements
Screen reader users cannot determine the purpose of interactive elements with role="link", role="button", or role="menuitem" that lack an accessible name. Without a name, these controls are essentially invisible to assistive technology users.
Audit Elements
<div aria-expanded="false" aria-label="Select Region" class="nav-ui-RegionPicker__region__UmVna" data-testid="region-button" role="button" tabindex="0">
<span class="styles_dot__4CJdb styles_activeDot__jPGWM" aria-label="navigation dot" role="button" tabindex="0"></span>
<span class="styles_dot__4CJdb" aria-label="navigation dot" role="button" tabindex="0"></span>
<span class="styles_dot__4CJdb" aria-label="navigation dot" role="button" tabindex="0"></span>
<span class="styles_dot__4CJdb" aria-label="navigation dot" role="button" tabindex="0"></span>
Showing first 5 of 7 audited elements.
ARIA hidden element must not be focusable or contain focusable elements64 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
<span aria-hidden="true">
<span aria-hidden="true">
<span aria-hidden="true">
<span aria-hidden="true">
<span aria-hidden="true">
Showing first 5 of 64 audited elements.
ARIA input fields must have an accessible name1 element
ARIA input fields with roles like combobox, listbox, searchbox, slider, spinbutton, and textbox must have accessible names. Without names, screen reader users cannot identify what information these fields expect or their purpose in the form.
Audit Elements
<div tabindex="0" class="vjs-progress-holder vjs-slider vjs-slider-horizontal" role="slider" aria-valuenow="6.60" aria-valuemin="0" aria-valuemax="100" aria-label="Progress Bar" aria-valuetext="0:03 of 0:50">
ARIA role should be appropriate for the element105 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
<div class="media-ui-BaseAd_base..." data-component="leaderboard-ad" data-ad-status="rendered" role="region" aria-label="Leaderboard advertis..." aria-busy="false" data-ad-size="970x250">
<a href="#that-jump-content" class="bb-that__skip-to-content" aria-label="Skip to content" role="button" tabindex="0">Skip to content</a>
<a class="bb-that-header__link..." href="https://www.bloomber..." role="button" aria-controls="bb-that--container" aria-expanded="false" data-element="tophat-link" data-description="Bloomberg the Compan..." data-label="bcom">
<div id="bb-that--container" class="bb-that__sitemap bb-that--container" tabindex="-1" role="dialog">
<svg width="100%" height="100%" version="1.1" viewBox="429.6 479.5 476.4 96.1" xmlns="http://www.w3.org/2000/svg" role="img" fill="currentColor" aria-label="Bloomberg" data-component="bloombergLogo">
Showing first 5 of 105 audited elements.
ARIA roles used must conform to valid values57 elements
Invalid ARIA role values prevent assistive technologies from understanding and communicating the element's purpose to users. Without valid roles, screen readers cannot provide information about the element's features, properties, or how users should interact with it.
Audit Elements
<div class="media-ui-BaseAd_base..." data-component="leaderboard-ad" data-ad-status="rendered" role="region" aria-label="Leaderboard advertis..." aria-busy="false" data-ad-size="970x250">
<a href="#that-jump-content" class="bb-that__skip-to-content" aria-label="Skip to content" role="button" tabindex="0">Skip to content</a>
<a class="bb-that-header__link..." href="https://www.bloomber..." role="button" aria-controls="bb-that--container" aria-expanded="false" data-element="tophat-link" data-description="Bloomberg the Compan..." data-label="bcom">
<svg width="100%" height="100%" version="1.1" viewBox="429.6 479.5 476.4 96.1" xmlns="http://www.w3.org/2000/svg" role="img" fill="currentColor" aria-label="Bloomberg" data-component="bloombergLogo">
<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="Search">
Showing first 5 of 57 audited elements.
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 style="overflow-y: auto;">
Buttons must have discernible text68 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="nav-ui-LogoBar__signInButton__TG9nb" data-testid="sign-in-button">Sign In</button>
<button class="nav-ui-LogoBar__searchButton__TG9nb" data-testid="nav-search-button">
<button id="downshift-29240-toggle-button" class="dropdown-button" data-component="dropdown-button" tabindex="0" aria-controls="downshift-29240-toggle-button" aria-labelledby="downshift-29240-toggle-button" aria-haspopup="listbox" aria-label="Top Securities" aria-expanded="false" ...>
<button class="media-ui-Slider_arrow--r5pSh5snEo-" type="button" disabled="">Back</button>
<button class="media-ui-Slider_arrow--r5pSh5snEo-" type="button">Forward</button>
Showing first 5 of 68 audited elements.
Deprecated ARIA roles must not be used57 elements
Deprecated ARIA roles are not recognized by modern screen readers and assistive technologies. Using outdated roles means some users cannot access essential information or functionality on your site.
Audit Elements
<div class="media-ui-BaseAd_base..." data-component="leaderboard-ad" data-ad-status="rendered" role="region" aria-label="Leaderboard advertis..." aria-busy="false" data-ad-size="970x250">
<a href="#that-jump-content" class="bb-that__skip-to-content" aria-label="Skip to content" role="button" tabindex="0">Skip to content</a>
<a class="bb-that-header__link..." href="https://www.bloomber..." role="button" aria-controls="bb-that--container" aria-expanded="false" data-element="tophat-link" data-description="Bloomberg the Compan..." data-label="bcom">
<svg width="100%" height="100%" version="1.1" viewBox="429.6 479.5 476.4 96.1" xmlns="http://www.w3.org/2000/svg" role="img" fill="currentColor" aria-label="Bloomberg" data-component="bloombergLogo">
<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="Search">
Showing first 5 of 57 audited elements.
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">
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>
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">
Elements marked as presentational should be consistently ignored9 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 loading="lazy" alt="" src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/i.0CCamjZbB0/v3/640x-1.webp">
<img alt="" class="intercom-video-card_videoCardMedia-jDetZlZpHSw-" src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/iBx0mYF.nbAw/v3/540x-1.webp" style="aspect-ratio:2 / 3">
<img alt="" class="intercom-video-card_videoCardMedia-jDetZlZpHSw-" src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/i6YlVqfwkF0I/v3/540x-1.webp" style="aspect-ratio:2 / 3">
<img alt="" class="intercom-video-card_videoCardMedia-jDetZlZpHSw-" src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/i3IuykAe1APM/v3/540x-1.webp" style="aspect-ratio:2 / 3">
<img alt="" class="intercom-video-card_videoCardMedia-jDetZlZpHSw-" src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/i1lHf9ScFXE8/v3/540x-1.webp" style="aspect-ratio:2 / 3">
Showing first 5 of 9 audited elements.
Elements must meet minimum color contrast ratio thresholds394 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>Bloomberg the Company & Its Products</span>
<a class="bb-that-header__link" href="https://www.bloomberg.com/professional/contact-menu/?utm_source=bloomberg-menu&utm_medium=bcom&bbgsum=DG-WS-PROF-DEMO-bbgmenu" data-element="tophat-link" data-description="Bloomberg Terminal Demo Request" data-label="bcom">
<span>Bloomberg Anywhere Remote Login</span>
<span>Bloomberg Customer Support</span>
<button class="nav-ui-LogoBar__signInButton__TG9nb" data-testid="sign-in-button">Sign In</button>
Showing first 5 of 394 audited elements.
Elements must only use permitted ARIA attributes137 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
<div class="media-ui-BaseAd_base..." data-component="leaderboard-ad" data-ad-status="rendered" role="region" aria-label="Leaderboard advertis..." aria-busy="false" data-ad-size="970x250">
<iframe id="google_ads_iframe_/5..." name="google_ads_iframe_/5..." title="3rd party ad content" width="970" height="250" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
<a href="#that-jump-content" class="bb-that__skip-to-content" aria-label="Skip to content" role="button" tabindex="0">Skip to content</a>
<a class="bb-that-header__link..." href="https://www.bloomber..." role="button" aria-controls="bb-that--container" aria-expanded="false" data-element="tophat-link" data-description="Bloomberg the Compan..." data-label="bcom">
<svg width="100%" height="100%" version="1.1" viewBox="429.6 479.5 476.4 96.1" xmlns="http://www.w3.org/2000/svg" role="img" fill="currentColor" aria-label="Bloomberg" data-component="bloombergLogo">
Showing first 5 of 137 audited elements.
Elements must only use supported ARIA attributes146 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
<div class="media-ui-BaseAd_base..." data-component="leaderboard-ad" data-ad-status="rendered" role="region" aria-label="Leaderboard advertis..." aria-busy="false" data-ad-size="970x250">
<iframe id="google_ads_iframe_/5..." name="google_ads_iframe_/5..." title="3rd party ad content" width="970" height="250" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
<a href="#that-jump-content" class="bb-that__skip-to-content" aria-label="Skip to content" role="button" tabindex="0">Skip to content</a>
<a class="bb-that-header__link..." href="https://www.bloomber..." role="button" aria-controls="bb-that--container" aria-expanded="false" data-element="tophat-link" data-description="Bloomberg the Compan..." data-label="bcom">
<div aria-label="logo" class="nav-ui-Logo__logo__TG9nb nav-ui-Logo__dark__TG9nb" data-component="logo">
Showing first 5 of 146 audited elements.
Elements should not have tabindex greater than zero30 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
<iframe id="google_ads_iframe_/5..." name="google_ads_iframe_/5..." title="3rd party ad content" width="970" height="250" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
<a href="#that-jump-content" class="bb-that__skip-to-content" aria-label="Skip to content" role="button" tabindex="0">Skip to content</a>
<div id="that-jump-content--default" tabindex="-1"></div>
<div data-testid="chevron-arrow" tabindex="0">
<div data-testid="chevron-arrow" tabindex="0">
Showing first 5 of 30 audited elements.
Focused elements must not be entirely hidden by author-created content25 elements
Keyboard users have no pointer to show where they are. The focus indicator is their only cue, and a sticky header, footer, cookie banner, or other author-created overlay that completely hides the focused control strands them with no idea what will activate next.
Audit Elements
<a href="#that-jump-content" class="bb-that__skip-to-content" aria-label="Skip to content" role="button" tabindex="0">
<a class="bb-that-header__link bb-that-header--sitemap-trigg..." href="https://www.bloomberg.com/company/?utm_source=bloo..." role="button" aria-controls="bb-that--container" aria-expanded="false" data-element="tophat-link" data-description="Bloomberg the Company & Its Products" data-label="bcom...
<a class="bb-that-header__link" href="https://bba.bloomberg.net/?utm_source=bloomberg-me..." data-element="tophat-link" data-description="Bloomberg Anywhere Remote Login" data-label="bcom">
<a class="nav-ui-Logo__logo__TG9nb" href="/">
<button class="nav-ui-LogoBar__signInButton__TG9nb" data-testid="sign-in-button">
Showing first 5 of 25 audited elements.
Form elements must have labels2 elements
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" data-component="text-input" class="media-ui-InputField_input-trz7AzJlxTU- text-input-input text-input" id="form-for-phoenix_newsletter" name="text-input" placeholder="Enter your email" aria-invalid="false" aria-label="text-input" value="">
<input aria-label="seek" class="media-ui-Seek_seek-roHEwjLz-X0- seek" data-component="seek" type="range" min="0" max="387" style="--max:387;--val:0" value="0">
Form elements should have a visible label2 elements
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.
Audit Elements
<input type="email" data-component="text-input" class="media-ui-InputField_input-trz7AzJlxTU- text-input-input text-input" id="form-for-phoenix_newsletter" name="text-input" placeholder="Enter your email" aria-invalid="false" aria-label="text-input" value="">
<input aria-label="seek" class="media-ui-Seek_seek-roHEwjLz-X0- seek" data-component="seek" type="range" min="0" max="387" style="--max:387;--val:0" value="0">
Form field must not have multiple label elements2 elements
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" data-component="text-input" class="media-ui-InputField_input-trz7AzJlxTU- text-input-input text-input" id="form-for-phoenix_newsletter" name="text-input" placeholder="Enter your email" aria-invalid="false" aria-label="text-input" value="">
<input aria-label="seek" class="media-ui-Seek_seek-roHEwjLz-X0- seek" data-component="seek" type="range" min="0" max="387" style="--max:387;--val:0" value="0">
Frames must have a unique title attribute1 element
Screen reader users navigate frames using a list of frame titles. Duplicate or missing titles make it impossible to distinguish between frames, forcing users to explore each frame's content manually. Unique, descriptive titles enable quick navigation to the correct frame.
Audit Elements
<iframe id="google_ads_iframe_/5..." name="google_ads_iframe_/5..." title="3rd party ad content" width="970" height="250" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
Frames must have an accessible name3 elements
Screen reader users rely on frame titles to understand frame content without exploring each one. Without descriptive, unique titles, users receive unhelpful information like "frame," "JavaScript," or URLs, making navigation through frames difficult and confusing.
Audit Elements
<iframe id="google_ads_iframe_/5..." name="google_ads_iframe_/5..." title="3rd party ad content" width="970" height="250" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
<iframe title="Third party embed iframe" src="https://www.bloomberg.com/games/embed?display=fluid" allowfullscreen="" frameborder="0" scrolling="no" width="100%" height="116.203125" data-testid="iframe" data-embedid=":Rccqel9l6:"></iframe>
<iframe title="Third party embed iframe" src="https://www.bloomberg.com/graphics/market-reactions-iran-war/embed-dash/?display=fluid" allowfullscreen="" frameborder="0" scrolling="no" width="100%" height="439" data-testid="iframe" data-embedid=":R6kqel9l6:"></iframe>
Heading levels should only increase by one34 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
<h3 data-component="title" class="LineupContentOpinion_title__2VdbI typography_coreHeadlineXxs__I27qw typography_core__ts8O_ typography_coreHeadline__Vh_JB"><a href="https://www.bloomberg.com/opinion">Bloomberg Opinion</a></h3>
<h3 data-component="title" class="typography_coreHeadlineXxs__I27qw typography_core__ts8O_ typography_coreHeadline__Vh_JB">Today’s Videos</h3>
<h3 data-component="title" class="StoryListLatestFiltered_titleLink__5Y9qU typography_coreHeadlineXs__fj38Z typography_core__ts8O_ typography_coreHeadline__Vh_JB">Latest</h3>
<h3 data-component="title" class="ModuleHeader_title__eAyEi typography_coreHeadlineXxs__I27qw typography_core__ts8O_ typography_coreHeadline__Vh_JB">In Focus</h3>
<h3 class="EmbedAudio_summaryText__onH_t typography_articleDek__A_HWs">Listen to the latest: Amazon Cargo Plane Crash, US Envoys-Zelenskyy Meet, More</h3>
Showing first 5 of 34 audited elements.
Headings should not be empty34 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
<h3 data-component="title" class="LineupContentOpinion_title__2VdbI typography_coreHeadlineXxs__I27qw typography_core__ts8O_ typography_coreHeadline__Vh_JB"><a href="https://www.bloomberg.com/opinion">Bloomberg Opinion</a></h3>
<h3 data-component="title" class="typography_coreHeadlineXxs__I27qw typography_core__ts8O_ typography_coreHeadline__Vh_JB">Today’s Videos</h3>
<h3 data-component="title" class="StoryListLatestFiltered_titleLink__5Y9qU typography_coreHeadlineXs__fj38Z typography_core__ts8O_ typography_coreHeadline__Vh_JB">Latest</h3>
<h3 data-component="title" class="ModuleHeader_title__eAyEi typography_coreHeadlineXxs__I27qw typography_core__ts8O_ typography_coreHeadline__Vh_JB">In Focus</h3>
<h3 class="EmbedAudio_summaryText__onH_t typography_articleDek__A_HWs">Listen to the latest: Amazon Cargo Plane Crash, US Envoys-Zelenskyy Meet, More</h3>
Showing first 5 of 34 audited elements.
IDs used in ARIA and labels must be unique37 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
<div id="bb-that--container" class="bb-that__sitemap bb-that--container" tabindex="-1" role="dialog">
<h3 id="that-list--for_customers--2" class="bb-that-category__title">For Customers</h3>
<h3 id="that-list--company--4" class="bb-that-category__title">Company</h3>
<h3 id="that-list--communications--5" class="bb-that-category__title">Communications</h3>
<h3 id="that-list--follow--6" class="bb-that-category__title">Follow</h3>
Showing first 5 of 37 audited elements.
Images must have alternative text122 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 src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/ihrP.bKBqSxg/v0/600x400.jpg" data-component="image" alt="Iran, US Trade Tanker Attacks as Six-Month Conflict Escalates" loading="eager">
<img src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/ifSq1fyZowRo/v0/715x477.jpg" data-component="image" alt="Yuan Banknotes as China Boosts Yuan Support as Dollar Strength Pressures Asia" loading="lazy">
<img loading="lazy" alt="" src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/i.0CCamjZbB0/v3/640x-1.webp">
<img src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/iLQLWzzFD2HM/v1/600x400.jpg" data-component="image" alt="Spanish Solar Park Operated by Zelestra Corp. SA" loading="eager">
<img src="https://assets.bwbx.io/images/users/iqjWHBFdfxIU/ijWc5wAiYmH0/v0/72x72.png" data-component="image" alt="Europe Looks Back at a Summer of Record Heat as El Niño Looms in 2027" loading="eager">
Showing first 5 of 122 audited elements.
Inline text spacing must be adjustable with custom stylesheets135 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 style="overflow-y: auto;">
<div id="leaderboard-decoupled" data-testid="sparkle-ad" data-ad-status="rendered" classname="display" style="">
<div class="bb-ads__ad bb-ads__rendered" id="83fe32f15d8f8c481c401d7956b2d113" style="" data-google-query-id="CM3c2LLL25YDFU56TAgd9wMt-A">
<div id="google_ads_iframe_/5262/bloomberg/home/americas/phoenix/index_0__container__" style="border: 0pt;">
<iframe id="google_ads_iframe_/5..." name="google_ads_iframe_/5..." title="3rd party ad content" width="970" height="250" scrolling="no" marginwidth="0" marginheight="0" frameborder="0" aria-label="Advertisement" tabindex="0" allow="private-state-token-..." data-load-complete="true" ...>
Showing first 5 of 135 audited elements.
Interactive controls must not be nested217 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
<a href="#that-jump-content" class="bb-that__skip-to-content" aria-label="Skip to content" role="button" tabindex="0">Skip to content</a>
<a class="bb-that-header__link..." href="https://www.bloomber..." role="button" aria-controls="bb-that--container" aria-expanded="false" data-element="tophat-link" data-description="Bloomberg the Compan..." data-label="bcom">
<svg width="100%" height="100%" version="1.1" viewBox="429.6 479.5 476.4 96.1" xmlns="http://www.w3.org/2000/svg" role="img" fill="currentColor" aria-label="Bloomberg" data-component="bloombergLogo">
<button class="nav-ui-LogoBar__signInButton__TG9nb" data-testid="sign-in-button">Sign In</button>
<button class="nav-ui-LogoBar__searchButton__TG9nb" data-testid="nav-search-button">
Showing first 5 of 217 audited elements.
Interactive elements must have a visible focus indicator35 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Audit Elements
<a href="#that-jump-content" class="bb-that__skip-to-content" aria-label="Skip to content" role="button" tabindex="0">
<a class="bb-that-header__link bb-that-header--sitemap-trigg..." href="https://www.bloomberg.com/company/?utm_source=bloo..." role="button" aria-controls="bb-that--container" aria-expanded="false" data-element="tophat-link" data-description="Bloomberg the Company & Its Products" data-label="bcom...
<a class="bb-that-header__link" href="https://www.bloomberg.com/professional/contact-men..." data-element="tophat-link" data-description="Bloomberg Terminal Demo Request" data-label="bcom">
<a class="bb-that-header__link" href="https://bba.bloomberg.net/?utm_source=bloomberg-me..." data-element="tophat-link" data-description="Bloomberg Anywhere Remote Login" data-label="bcom">
<a class="bb-that-header__link" href="https://www.bloomberg.com/professional/support/?ut..." data-element="tophat-link" data-description="Bloomberg Customer Support" data-label="bcom">
Showing first 5 of 35 audited elements.
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
<main>
<div class="media-ui-BaseAd_base..." data-component="leaderboard-ad" data-ad-status="rendered" role="region" aria-label="Leaderboard advertis..." aria-busy="false" data-ad-size="970x250">
<div class="media-ui-BaseAd_base..." data-component="box-ad" data-ad-status="rendering" role="region" aria-label="Advertisement" aria-busy="true">
lang attribute must have a valid value2 elements
Screen readers use language-specific pronunciation libraries that must match the content's language. Invalid language declarations cause screen readers to use the wrong pronunciation library, making content sound confusing or unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<div id="skylight-vod-2179b6a..." poster="https://assets.bwbx...." class="video-js vjs-fluid s..." tabindex="-1" lang="en" translate="no" role="region" aria-label="Video Player">
<div id="skylight-vod-81d79f8..." poster="https://assets.bwbx...." class="video-js vjs-paused ..." tabindex="-1" lang="en" translate="no" role="region" aria-label="Video Player">
Links must be distinguishable without relying on color5 elements
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://www.bloomberg.com/notices/privacy/" rel="noopener noreferrer" target="_blank">Privacy Policy</a>
<a href="https://www.bloomberg.com/notices/tos/" rel="noopener noreferrer" target="_blank">Terms of Service</a>
<a href="/notices/tos" target="_blank" rel="noopener noreferrer" style="text-decoration: underline; color: black;">Terms of Service,</a>
<a href="/notices/privacy" target="_blank" rel="noopener noreferrer" style="text-decoration: underline; color: black;">Privacy Policy,</a>
<a href="https://www.bloomberg.com/" target="_blank" rel="noopener noreferrer" style="text-decoration: underline; color: black;">Bloomberg.com</a>
Links must have discernible text342 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 href="#that-jump-content" class="bb-that__skip-to-content" aria-label="Skip to content" role="button" tabindex="0">Skip to content</a>
<a class="bb-that-header__link..." href="https://www.bloomber..." role="button" aria-controls="bb-that--container" aria-expanded="false" data-element="tophat-link" data-description="Bloomberg the Compan..." data-label="bcom">
<a class="bb-that-header__link" href="https://www.bloomberg.com/professional/contact-menu/?utm_source=bloomberg-menu&utm_medium=bcom&bbgsum=DG-WS-PROF-DEMO-bbgmenu" data-element="tophat-link" data-description="Bloomberg Terminal Demo Request" data-label="bcom">
<a class="bb-that-header__link" href="https://bba.bloomberg.net/?utm_source=bloomberg-menu&utm_medium=bcom" data-element="tophat-link" data-description="Bloomberg Anywhere Remote Login" data-label="bcom"><span>Bloomberg Anywhere Remote Login</span><span>Bloomberg Anywhere Login</span></a>
<a class="bb-that-header__link" href="https://www.bloomberg.com/professional/support/?utm_source=bloomberg-menu&utm_medium=bcom" data-element="tophat-link" data-description="Bloomberg Customer Support" data-label="bcom"><span>Bloomberg Customer Support</span><span>Customer Support</span></a>
Showing first 5 of 342 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>
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">
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">
Required ARIA attributes must be provided57 elements
ARIA widget roles need required attributes to describe their current state. Without these attributes, screen readers cannot communicate essential information like whether a checkbox is checked or a slider's current value, leaving users unable to interact effectively with the widget.
Audit Elements
<div class="media-ui-BaseAd_base..." data-component="leaderboard-ad" data-ad-status="rendered" role="region" aria-label="Leaderboard advertis..." aria-busy="false" data-ad-size="970x250">
<a href="#that-jump-content" class="bb-that__skip-to-content" aria-label="Skip to content" role="button" tabindex="0">Skip to content</a>
<a class="bb-that-header__link..." href="https://www.bloomber..." role="button" aria-controls="bb-that--container" aria-expanded="false" data-element="tophat-link" data-description="Bloomberg the Compan..." data-label="bcom">
<svg width="100%" height="100%" version="1.1" viewBox="429.6 479.5 476.4 96.1" xmlns="http://www.w3.org/2000/svg" role="img" fill="currentColor" aria-label="Bloomberg" data-component="bloombergLogo">
<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="Search">
Showing first 5 of 57 audited elements.
Scrollable region must have keyboard access2 elements
Scrollable regions must contain focusable elements or be focusable themselves to enable keyboard navigation. Without keyboard access, users cannot scroll to view content that extends beyond the visible area, making that content completely inaccessible to keyboard-only users.
Audit Elements
<div data-component="slider-track" class="media-ui-Slider_track-AspceFK4VEs-">
<div class="styles_tagPicker__ivJBq">
Users should be able to zoom and scale the text up to 500%3 elements
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">
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
<meta name="viewport" content="width=device-width">
Zooming and scaling must not be disabled3 elements
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">
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
<meta name="viewport" content="width=device-width">
How does your site stack up against Bloomberg?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in News & Media