Skip to content
https://lexology.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
✗ 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
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Landmark Structure
Action
8 landmarks
REVIEW
8 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) CONTENTINFO footer

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

B
Form Accessibility
2 of 12 controls have issues
REVIEW
2 of 12 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="qfoot">
Info::
10 control(s) properly labeled
12 controls
10 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#header-searchtextSearch Lexologyaria-label
inputsubmitSubmit searcharia-label
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextVendor Searcharia-label
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
#qfoottext(Search Lexology)placeholder only
inputsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text" name="q" id="qfoot">

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

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Content not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 The number one
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
32px · bottom of viewport
h1 platform for mitigating risk, staying ab…
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
32px · bottom of viewport
h2 NEWS AND ANALYSIS
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Lexology is built on insights, forward-l…
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
24px · bottom of viewport
h2 LEGAL RESEARCH
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
24px · bottom of viewport
h2 REGULATORY COMPLIANCE
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
24px · bottom of viewport
h2 PRACTICAL RESOURCES
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
24px · bottom of viewport
h2 RANKINGS
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
24px · bottom of viewport
h2 EVENTS AND MASTERCLASSES
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Cookie Preference Centre
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Track the developments that matter
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Regulatory Compliance
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Artificial intelligence
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
19px · bottom of viewport
h3 ESG
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Data protection
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Trade & customs
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Employment
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sanctions
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Anti-bribery & corruption
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Banking
1.03:1
#000000
on
#050505
needs 3.0:1 (large text)
19px · bottom of viewport

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The number one1.03:13.0:1
#000000
#050505
Fail
h1 platform for mitigat…1.03:13.0:1
#000000
#050505
Fail
h2 NEWS AND ANALYSIS1.03:13.0:1
#000000
#050505
Fail
h2 Lexology is built on…1.03:13.0:1
#000000
#050505
Fail
h2 LEGAL RESEARCH1.03:13.0:1
#000000
#050505
Fail
h2 REGULATORY COMPLIANC…1.03:13.0:1
#000000
#050505
Fail
h2 PRACTICAL RESOURCES1.03:13.0:1
#000000
#050505
Fail
h2 RANKINGS1.03:13.0:1
#000000
#050505
Fail
h2 EVENTS AND MASTERCLA…1.03:13.0:1
#000000
#050505
Fail
h2 Cookie Preference Ce…1.03:13.0:1
#000000
#050505
Fail
h3 Track the developmen…1.03:13.0:1
#000000
#050505
Fail
h3 Regulatory Complianc…1.03:13.0:1
#000000
#050505
Fail
h3 Artificial intellige…1.03:13.0:1
#000000
#050505
Fail
h3 ESG1.03:13.0:1
#000000
#050505
Fail
h3 Data protection1.03:13.0:1
#000000
#050505
Fail
h3 Trade & customs1.03:13.0:1
#000000
#050505
Fail
h3 Employment1.03:13.0:1
#000000
#050505
Fail
h3 Sanctions1.03:13.0:1
#000000
#050505
Fail
h3 Anti-bribery & corru…1.03:13.0:1
#000000
#050505
Fail
h3 Banking1.03:13.0:1
#000000
#050505
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.

B
Lighthouse Accessibility Audits
Score 89/100 — 5 failing, 25 passed
REVIEW
89

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Latest intelligence Legal research Regulatory monitoring Practical resources Ex… div#mobile-navigation > div.bottom-row > nav.lbr-nav > ul

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Login nav.lbr-nav > ul > div.mobile-login-register > li#mylex-nav-login
Register nav.lbr-nav > ul > div.mobile-login-register > li#mylex-nav-register

These are opportunities to improve the experience of reading tabular or list data using 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
Scroll left div.carousel-wrapper > div.carousel-root > div.carousel > button.control-link
Scroll right div.carousel-wrapper > div.carousel-root > div.carousel > button.control-link
div.col-sm-4 > div.foot-search-container > form#SearchForm > input.submit div.col-sm-4 > div.foot-search-container > form#SearchForm > input.submit

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 html

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
cookie policy div#onetrust-group-container > div#onetrust-policy > p#onetrust-policy-text > a
○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
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●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.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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.
○`<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
50 headings
PASS
50 headings
Info::
Single H1 present
  • H1 The number one global legal intelligence platform for mitigating risk, staying abreast of change and finding expert counsel
  • H2 NEWS AND ANALYSIS
  • H3 Track the developments that matter
  • H3 Regulatory Compliance
  • H3 Artificial intelligence
  • H3 ESG
  • H3 Data protection
  • H3 Trade & customs
  • H3 Employment
  • H3 Sanctions
  • H3 Anti-bribery & corruption
  • H3 Banking
  • H2 Lexology is built on insights, forward-looking analysis and expert guidance from the world's leading law firms
  • H2 LEGAL RESEARCH
  • H3 Find trusted answers to legal questions, fast
  • H2 REGULATORY COMPLIANCE
  • H3 Track global regulatory change and stay compliant
  • H4 Scanner
  • H5 Essential regulatory monitoring
  • H4 Compliance calendar
  • H5 Horizon scanning
  • H4 Analysis and guidance
  • H5 From experienced journalists
  • H4 Regulatory data APIs
  • H5 Advanced workflows
  • H2 PRACTICAL RESOURCES
  • H3 Draft, review and act with confidence
  • H3 Featured How-to-guide
  • H3 How-to guide: How to navigate the legal implications of Executive Orders 14151 and 14173 for workplace DEI programs (USA)
  • H3 Featured Checklist
  • H3 Checklist: Mitigating the risk of civil liability claims and preparing to respond to claims under the False Claims Act (USA)
  • H3 Featured Contract
  • H3 Data Subject Rectification Request Form (GDPR)
  • H2 RANKINGS
  • H3 Find the right expert for your legal questions
  • H2 EVENTS AND MASTERCLASSES
  • H3 Join the conversation in person and online
  • H4 UPCOMING EVENTS
  • H2 Cookie Preference Centre
  • H3 Your Privacy
  • H3 Strictly Necessary Cookies
  • H3 Performance Cookies
  • H3 Functional Cookies
  • H3 Targeting Cookies
  • H4 Your Privacy
  • H4 Strictly Necessary Cookies
  • H4 Performance Cookies
  • H4 Functional Cookies
  • H4 Targeting Cookies
  • H3 Back
A+
Alt Text Quality
All 20 images OK
PASS
All 20 images OK
Info::
20 image(s) with good alt text
20 images 20 good alt text
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback