Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 4 REVIEW 6 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-cci90u

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

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

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://bloomberglaw.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://bloomberglaw.com/manifest.json

Manifest contains invalid JSON.

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 ✗

Landmark Structure

Action

2 landmarks

REVIEW

2 landmarks

No <main> landmark found

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

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No banner (header) landmark

No contentinfo (footer) landmark

Skip navigation link present

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" name="username" id="username">; <input type="password" name="password" id="password">

2 controls

0 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
#username	text	(Enter username)	placeholder only
#password	password	(Enter password)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

1 issue(s) across 100 links and 1 buttons

REVIEW

1 issue(s) across 100 links and 1 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://pro.bloomberglaw.com/the-complete-legal-research-resource/?trackingco… ("Learn More")

8 link(s) open in new tab without warning

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

Got: http://www.facebook.com/Bloomberglp; https://twitter.com/bloomberg; https://www.linkedin.com/company/2494; https://www.instagram.com/bloomberg/; http://www.facebook.com/Bloomberglp; https://twitter.com/bloomberg; https://www.linkedin.com/company/2494; https://www.instagram.com/bloomberg/

91 link(s) with descriptive text

100 links

0 empty

1 generic text

8 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
http://www.facebook.com/Bloomberglp	Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/bloomberg	Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/2494	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/bloomberg/	Instagram	new tab	Add '(opens in new tab)' to text
http://www.facebook.com/Bloomberglp	Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/bloomberg	Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/2494	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/bloomberg/	Instagram	new tab	Add '(opens in new tab)' to text
https://pro.bloomberglaw.com/the-complet…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: ?Trackingcode=Blaw22108720&Utm Medium=Referral&Utm Source=Mainblawlogin

92 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://pro.bloomberglaw.com/the-complete-legal-research-resource/?trackingco… ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

http://www.facebook.com/Bloomberglp; https://twitter.com/bloomberg; https://www.linkedin.com/company/2494; https://www.instagram.com/bloomberg/; http://www.facebook.com/Bloomberglp; https://twitter.com/bloomberg; https://www.linkedin.com/company/2494; https://www.instagram.com/bloomberg/

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 16 fail WCAG AA

REVIEW

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

4 pass 16 fail WCAG AA

h1 One price, one platform,

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h1 unlimited benefits

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h3 Communications

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Follow

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Products

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Industry Products

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Media

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Media Services

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Company

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Communications

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Follow

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Products

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Industry Products

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Media

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Media Services

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Bloomberg

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 One price, one platf…	1.00:1	3.0:1	#000000	#000000	Fail
h1 unlimited benefits	1.00:1	3.0:1	#000000	#000000	Fail
h3 Bloomberg	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 For Customers	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Support	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Company	5.32:1	3.0:1	#000000	#808080	Pass
h3 Communications	1.00:1	3.0:1	#000000	#000000	Fail
h3 Follow	1.00:1	3.0:1	#000000	#000000	Fail
h3 Products	1.00:1	3.0:1	#000000	#000000	Fail
h3 Industry Products	1.00:1	3.0:1	#000000	#000000	Fail
h3 Media	1.00:1	3.0:1	#000000	#000000	Fail
h3 Media Services	1.00:1	3.0:1	#000000	#000000	Fail
h3 Company	1.00:1	3.0:1	#000000	#000000	Fail
h3 Communications	1.00:1	3.0:1	#000000	#000000	Fail
h3 Follow	1.00:1	3.0:1	#000000	#000000	Fail
h3 Products	1.00:1	3.0:1	#000000	#000000	Fail
h3 Industry Products	1.00:1	3.0:1	#000000	#000000	Fail
h3 Media	1.00:1	3.0:1	#000000	#000000	Fail
h3 Media Services	1.00:1	3.0:1	#000000	#000000	Fail
h3 Bloomberg	1.00:1	3.0:1	#000000	#000000	Fail

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.

Heading Hierarchy

22 headings, 1 skip(s)

PASS

22 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H4 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H3 Bloomberg
H3 For Customers
H3 Support
H3 Company
H3 Communications
H3 Follow
H3 Products
H3 Industry Products
H3 Media
H3 Media Services
H3 Company
H3 Communications
H3 Follow
H3 Products
H3 Industry Products
H3 Media
H3 Media Services
H3 Bloomberg
H3 For Customers
H3 Support
H1 One price, one platform,unlimited benefits
H4 Looking for Bloomberg Law News? skipped

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Lighthouse Accessibility Audits

Score 98/100 — 1 failing, 23 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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.hydrated `html.hydrated`

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

●Form elements have associated labels

●`[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 use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●Links have a discernible name

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○`[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

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

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

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

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

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

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

○Identical links have the same purpose.

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