Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 1 REVIEW 7 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

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

No <nav> landmark found

No contentinfo (footer) landmark

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

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

Why this matters

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

Learn more ▾

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

Source: WAI-ARIA / WCAG 2.4.1

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title Bloomberg - Are you a robot? ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Color Contrast (Screenshot)

Action

19 text elements analyzed, 1 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

18 pass 1 fail WCAG AA 1 pass AA only

title Bloomberg - Are you a robot?

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (19)

Element	Ratio	Required	FG	BG	Result
h1 Bloomberg	3.39:1	3.0:1	#000000	#616161	Pass
h2 We've detected unusu…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Why did this happen?	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Need Help?	18.76:1	3.0:1	#000000	#F2F2F2	Pass
title Bloomberg - Are you …	1.00:1	4.5:1	#000000	#000000	Fail
a Need help? Contact u…	18.76:1	4.5:1	#000000	#F2F2F2	Pass
p To continue, please …	18.76:1	4.5:1	#000000	#F2F2F2	Pass
p Please make sure you…	18.76:1	4.5:1	#000000	#F2F2F2	Pass
a Terms of Service	18.76:1	4.5:1	#000000	#F2F2F2	Pass
p and	18.76:1	4.5:1	#000000	#F2F2F2	Pass
a Cookie Policy	18.76:1	4.5:1	#000000	#F2F2F2	Pass
p For inquiries relate…	18.76:1	4.5:1	#000000	#F2F2F2	Pass
a contact …	18.76:1	4.5:1	#000000	#F2F2F2	Pass
p and provide the refe…	18.76:1	4.5:1	#000000	#F2F2F2	Pass
div Block reference ID:d…	18.76:1	4.5:1	#000000	#F2F2F2	Pass
p Get the most importa…	18.76:1	4.5:1	#000000	#F2F2F2	Pass
a Bloomberg.com	18.76:1	4.5:1	#000000	#F2F2F2	Pass
p subscription.	18.76:1	4.5:1	#000000	#F2F2F2	Pass
a SUBSCRIBE NOW	18.76:1	4.5:1	#000000	#F2F2F2	Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+

Heading Hierarchy

4 headings

PASS

4 headings

Single H1 present

H1 Bloomberg
H2 We've detected unusual activity from your computer network
H3 Why did this happen?
H3 Need Help?

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

6 links, 0 buttons — all OK

PASS

6 links, 0 buttons — all OK

6 link(s) open in new tab without warning

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

Got: /feedback; /notices/tos; /notices/tos; /feedback; https://bloomberg.com; /subscription

6 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/feedback	Need help? Contact us	new tab	Add '(opens in new tab)' to text
/notices/tos	Terms of Service	new tab	Add '(opens in new tab)' to text
/notices/tos	Cookie Policy	new tab	Add '(opens in new tab)' to text
/feedback	contact …	new tab	Add '(opens in new tab)' to text
https://bloomberg.com	Bloomberg.com	new tab	Add '(opens in new tab)' to text
/subscription	SUBSCRIBE NOW	new tab	Add '(opens in new tab)' to text

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

/feedback; /notices/tos; /notices/tos; /feedback; https://bloomberg.com; /subscription

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 25 passed

PASS

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section#header_text > figure.SectionFrontHeaderImageTitle_imageStyles__j6IPz > picture.styles_lazy___9s4S > img `section#header_text > figure.SectionFrontHeaderImageTitle_imageStyles__j6IPz > picture.styles_lazy___9s4S > img`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
navigation dot `section#shadow_magazine_cover_carousel > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb`
navigation dot `section#shadow_magazine_cover_carousel > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb`
navigation dot `section#shadow_magazine_cover_carousel > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb`
navigation dot `section#shadow_magazine_cover_carousel > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb`
navigation dot `div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb`
navigation dot `div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb`
navigation dot `div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb`
navigation dot `div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb`
navigation dot `div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb`
navigation dot `div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb`
navigation dot `div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb`
navigation dot `div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb`
navigation dot `div.VariantBase_headerSiblingContainer__3nEJ6 > div.styles_carouselNav__Mgj6h > div.styles_navSection__IZYQv > span.styles_dot__4CJdb`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

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

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

●Buttons have an accessible name

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

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