Skip to content
https://law.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Alt Text Quality
Action
2 of 64 images have issues
FIX
2 of 64 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
5 decorative image(s) correctly marked
Info::
57 image(s) with good alt text
64 images 57 good alt text 5 decorative 2 missing
IssueCount
missing2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
42 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 42 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
57 landmarks
REVIEW
57 landmarks
Info::
<main> landmark present
Info::
42 <nav> landmark(s) found
Warning::
31 of 42 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV MAIN ASIDE CONTENTINFO footer

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

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found - Law.com ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 80/100 — 7 failing, 25 passed
REVIEW
80

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.

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Law.com Compass div.overflow-auto > div.grid > div.grid > a.inline-flex
Law.com Radar div.overflow-auto > div.grid > div.grid > a.inline-flex
Verdict Search div.overflow-auto > div.grid > div.grid > a.inline-flex
Scholar div.overflow-auto > div.grid > div.grid > a.inline-flex
China Law & Practice div.overflow-auto > div.grid > div.grid > a.inline-flex
Legal Dictionary div.overflow-auto > div.grid > div.grid > a.inline-flex

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
May 27, 2026 div.flex > div.flex > div.flex > p
June 02, 2026 div.flex > div.flex > div.flex > p
Chicago li > div.flex > div.flex > p.legends-2
September 04, 2026 div.flex > div.flex > div.flex > p
Johannesburg li > div.flex > div.flex > p.legends-2

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Gen AI Disruption Is Hitting Legal Research. Are Legacy Players Under Threat? ul.grid > li.w-full > article > h3#story-title-{{ storyIndex }}

These are opportunities to improve keyboard navigation in your application.

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
div.flex > span.flex > span > img.w-10 div.flex > span.flex > span > img.w-10
div.flex > span.flex > span > img.w-[40px] div.flex > span.flex > span > img.w-[40px]

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.desktop:col-span-2 > article.flex > div.card-icon > a div.desktop:col-span-2 > article.flex > div.card-icon > a
div.desktop:col-span-2 > article.flex > div.card-icon > a div.desktop:col-span-2 > article.flex > div.card-icon > a
div.desktop:col-span-2 > article.flex > div.card-icon > a div.desktop:col-span-2 > article.flex > div.card-icon > a
div.desktop:col-span-2 > article.flex > div.card-icon > a div.desktop:col-span-2 > article.flex > div.card-icon > a
div.desktop:col-span-2 > article.flex > div.card-icon > a div.desktop:col-span-2 > article.flex > div.card-icon > a
div.desktop:col-span-2 > article.flex > div.card-icon > a div.desktop:col-span-2 > article.flex > div.card-icon > a

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
CONTRACTUAL DISPUTES div.select-none > article > div.text-xs > a
Texas Lawyer div.select-none > article > div.text-xs > a.font-medium
LAW FIRM MANAGEMENT div.select-none > article > div.text-xs > a
New York Law Journal div.select-none > article > div.text-xs > a.font-medium
LAW FIRM PARTNERS div.select-none > article > div.text-xs > a
Daily Business Review div.select-none > article > div.text-xs > a.font-medium

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
LITIGATION div.flex > div.flex > div.relative > a
BANKING AND FINANCE LAWS div.flex > div.flex > div.relative > a
UNITED STATES SUPREME COURT div.flex > div.flex > div.relative > a
LAW FIRM PROFITABILITY div.flex > div.flex > div.relative > a
MASS TORTS div.flex > div.flex > div.relative > a
TOOL Law.com Radar Real-time updates on new state and federal lawsuits and emer… aside.desktop:w-1/4 > div.w-full > div > a.ml-auto
TOOL Law.com Compass Comprehensive data and insights on law firm performance, i… aside.desktop:w-1/4 > div.w-full > div > a.ml-auto
○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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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.
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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.
○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.
A
Heading Hierarchy
14 headings, 1 skip(s)
PASS
14 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Fed Chair Nominee Vows Independence as Trump Pressure Looms
  • H3 Gen AI Disruption Is Hitting Legal Research. Are Legacy Players Under Threat? skipped
  • H3 Sneak Peek at the 2026 Go-To Law Schools: Big Law Nos. 1-10
  • H3 Texas Big Law Firms Are Prioritizing M&A, PE Partner Laterals
  • H3 Mega-Grant of Stock Serves as Fitting Finale for Retiring CLO Who Helped Script AppLovin's Storybook Run
  • H3 'An Inflection Point': 13 Lawyers Apply to Lead Talc MDL's Next Phase
  • H3 New York AG Sues Coinbase, Gemini Over Their Prediction Markets
  • H3 The Week in Data April 21: A Look at Legal Industry Trends by the Numbers
  • H2 Article Slider
  • H2 Litigation
  • H2 Legal Education
  • H2 Law Firm Management
  • H2 Artificial Intelligence
  • H2 Diversity

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+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#header-search-inputtextSearch Input Fieldaria-label
#header-search-inputtextSearch Input Fieldaria-label
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Fed Chair Nominee Vo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Article Slider21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Litigation21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Legal Education21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Law Firm Management21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Artificial Intellige…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Diversity21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Gen AI Disruption Is…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Sneak Peek at the 20…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Texas Big Law Firms …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Mega-Grant of Stock …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 'An Inflection Point…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 New York AG Sues Coi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The Week in Data Apr…21.00:13.0:1
#000000
#FFFFFF
Pass
title Law.com | The Premie…21.00:14.5:1
#000000
#FFFFFF
Pass
p Law.com Products & R…21.00:14.5:1
#000000
#FFFFFF
Pass
a Law.com21.00:14.5:1
#000000
#FFFFFF
Pass
a Compass21.00:14.5:1
#000000
#FFFFFF
Pass
a Radar21.00:14.5:1
#000000
#FFFFFF
Pass
a VerdictSearch21.00:14.5:1
#000000
#FFFFFF
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.

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

Send Feedback