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 3 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

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

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 Missing

✓ PNG Icons Present

✗ 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 ✗

Link & Button Quality

Action

5 issue(s) across 325 links and 45 buttons

REVIEW

5 issue(s) across 325 links and 45 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: #

4 link(s) with generic text

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

Got: /en/about-us/artificial-intelligence ("Read More"); /en/know/future-ready-lawyer-2026 ("Read More"); /en/know/future-ready-cfo ("Read More"); /en/about-us ("Learn More")

9 link(s) open in new tab without warning

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

Got: https://www.wolterskluwer.cn; /en; https://assets.contenthub.wolterskluwer.com/api/public/content/3210406-wolter…; https://www.wolterskluwer.cn; https://www.facebook.com/wolterskluwer; https://www.instagram.com/_wolterskluwer/ ; https://www.linkedin.com/company/wolters-kluwer/; https://www.youtube.com/@WoltersKluwerComms; /en

311 link(s) with descriptive text

325 links

1 empty

4 generic text

9 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.wolterskluwer.cn	Simplified Chinese	new tab	Add '(opens in new tab)' to text
/en	Wolters Kluwer Logo	new tab	Add '(opens in new tab)' to text
https://assets.contenthub.wolterskluwer.…	Annual Report	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
https://www.wolterskluwer.cn	Simplified Chinese	new tab	Add '(opens in new tab)' to text
/en/about-us/artificial-intelligence	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Artificial Intelligence
/en/know/future-ready-lawyer-2026	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Future Ready Lawyer 2026
/en/know/future-ready-cfo	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Future Ready Cfo
/en/about-us	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: About Us
https://www.facebook.com/wolterskluwer	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/_wolterskluwer…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/wolters…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@WoltersKluwerCo…	YouTube	new tab	Add '(opens in new tab)' to text
/en	Wolters Kluwer Logo	new tab	Add '(opens in new tab)' to text

356 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

/en/about-us/artificial-intelligence ("Read More"); /en/know/future-ready-lawyer-2026 ("Read More"); /en/know/future-ready-cfo ("Read More"); /en/about-us ("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.

https://www.wolterskluwer.cn; /en; https://assets.contenthub.wolterskluwer.com/api/public/content/3210406-wolter…; https://www.wolterskluwer.cn; https://www.facebook.com/wolterskluwer; https://www.instagram.com/_wolterskluwer/ ; https://www.linkedin.com/company/wolters-kluwer/; https://www.youtube.com/@WoltersKluwerComms; /en

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Page introuvable | Wolters Kluwer ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA

h1 AI-powered solutions for professionals

1.82:1

#000000

#393939

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Solutions & Products

1.82:1

#000000

#393939

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Powering healthcare solutions with AI to…

1.82:1

#000000

#393939

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Expert solutions to optimize your entire…

1.82:1

#000000

#393939

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Technology-enabled services and solution…

1.82:1

#000000

#393939

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Legal and regulatory insights and soluti…

1.82:1

#000000

#393939

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Global enterprise software

1.82:1

#000000

#393939

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Solutions & Products

1.82:1

#000000

#393939

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Powering healthcare solutions with AI to…

1.82:1

#000000

#393939

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Expert solutions to optimize your entire…

1.82:1

#000000

#393939

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Technology-enabled services and solution…

1.82:1

#000000

#393939

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Legal and regulatory insights and soluti…

1.82:1

#000000

#393939

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Global enterprise software

1.82:1

#000000

#393939

needs 3.0:1 (large text)

24px · bottom of viewport

h2 About Wolters Kluwer

1.82:1

#000000

#393939

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Brazil

1.00:1

#000000

needs 3.0:1 (large text)

19px · above the fold

h3 Canada

1.00:1

#000000

needs 3.0:1 (large text)

19px · mid-page

h3 Latin America

1.00:1

#000000

needs 3.0:1 (large text)

19px · mid-page

h3 Belgium

1.82:1

#000000

#393939

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Czech Republic

1.82:1

#000000

#393939

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 AI-powered solutions…	1.82:1	3.0:1	#000000	#393939	Fail
h2 Solutions & Products	1.82:1	3.0:1	#000000	#393939	Fail
h2 Powering healthcare …	1.82:1	3.0:1	#000000	#393939	Fail
h2 Expert solutions to …	1.82:1	3.0:1	#000000	#393939	Fail
h2 Technology-enabled s…	1.82:1	3.0:1	#000000	#393939	Fail
h2 Legal and regulatory…	1.82:1	3.0:1	#000000	#393939	Fail
h2 Global enterprise so…	1.82:1	3.0:1	#000000	#393939	Fail
h2 Solutions & Products	1.82:1	3.0:1	#000000	#393939	Fail
h2 Powering healthcare …	1.82:1	3.0:1	#000000	#393939	Fail
h2 Expert solutions to …	1.82:1	3.0:1	#000000	#393939	Fail
h2 Technology-enabled s…	1.82:1	3.0:1	#000000	#393939	Fail
h2 Legal and regulatory…	1.82:1	3.0:1	#000000	#393939	Fail
h2 Global enterprise so…	1.82:1	3.0:1	#000000	#393939	Fail
h2 About Wolters Kluwer	1.82:1	3.0:1	#000000	#393939	Fail
h3 Brazil	1.00:1	3.0:1	#000000	#000000	Fail
h3 Canada	1.00:1	3.0:1	#000000	#000000	Fail
h3 Latin America	1.00:1	3.0:1	#000000	#000000	Fail
h3 United States	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Belgium	1.82:1	3.0:1	#000000	#393939	Fail
h3 Czech Republic	1.82:1	3.0:1	#000000	#393939	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.

A+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

120 headings, 1 skip(s)

PASS

120 headings, 1 skip(s)

Single H1 present

Heading level skipped: H3 → H5 (missing H4)

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

H3 Brazil
H3 Canada
H3 Latin America
H3 United States
H3 Belgium
H3 Czech Republic
H3 Denmark
H3 France
H3 Germany
H3 Hungary
H3 Italy
H3 Netherlands
H3 Norway
H3 Poland
H3 Portugal
H3 Romania
H3 Slovakia
H3 Spain
H3 Sweden
H3 United Kingdom
H3 Australia
H3 China
H3 Hong Kong
H3 India
H3 Japan
H3 Malaysia
H3 New Zealand
H3 Philippines
H3 Singapore
H3 South Korea
H3 Taiwan
H3 Thailand
H3 Vietnam
H3 Health
H3 Tax & Accounting
H3 Financial & Corporate Compliance
H3 Legal & Regulatory
H3 Corporate Performance & ESG
H3 Useful Links
H3 Solutions
H3 Roles
H3 Solutions
H3 Solutions
H3 Roles
H3 Solutions
H3 Solutions
H3 Business Insights Hub
H3 Featured Reports
H3 Trending Topics
H3 Insights
H3 Trending Topics
H3 Insights
H3 Trending Topics
H3 Insights
H3 Trending Topics
H3 Insights
H3 Trending Topics
H3 Insights
H3 News
H3 Newsroom Hub
H3 Latest News
H3 About Wolters Kluwer
H3 Organization
H3 Useful Links
H3 Brazil
H3 Canada
H3 Latin America
H3 United States
H3 Belgium
H3 Czech Republic
H3 Denmark
H3 France
H3 Germany
H3 Hungary
H3 Italy
H3 Netherlands
H3 Norway
H3 Poland
H3 Portugal
H3 Romania
H3 Slovakia
H3 Spain
H3 Sweden
H3 United Kingdom
H3 Australia
H3 China
H3 Hong Kong
H3 India
H3 Japan
H3 Malaysia
H3 New Zealand
H3 Philippines
H3 Singapore
H3 South Korea
H3 Taiwan
H3 Thailand
H3 Vietnam
H1 AI-powered solutions for professionals
H2 Solutions & Products
H2 Powering healthcare solutions with AI to drive quality outcomes
H2 Expert solutions to optimize your entire firm
H2 Technology-enabled services and solutions
H2 Legal and regulatory insights and solutions
H2 Global enterprise software
H2 Solutions & Products
H2 Powering healthcare solutions with AI to drive quality outcomes
H2 Expert solutions to optimize your entire firm
H2 Technology-enabled services and solutions
H2 Legal and regulatory insights and solutions
H2 Global enterprise software
H3 Wolters Kluwer Expert AI
H3 Future Ready Lawyer
H3 Future Ready CFO
H2 About Wolters Kluwer
H3 Wolters Kluwer CCH Tagetik kicks off Global inTouch 2026 series showcasing Expert AI in action for the office of CFO
H3 Wolters Kluwer Future Ready CFO report shows APAC CFOs embrace AI with a governance‑first mindset, closely aligned with global peers
H3 Wolters Kluwer extends digital lending momentum by enabling liquidity access for commercial assets
H3 Deliver deep impact when it matters most
H5 Footer Navigation skipped
H6 Follow Wolters Kluwer

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

Alt Text Quality

1 of 24 images have issues

PASS

1 of 24 images have issues

1 image(s) with filename as alt text

1 image(s) with alt text over 125 characters

22 image(s) with good alt text

24 images 22 good alt text 1 generic

Issue	Count
filename	1 image(s)
too long	1 image(s)

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-input	search	Search	aria-label
#focus_retriever	text	Input box to get the focus back to the page on mouse move	aria-label

A+

Lighthouse Accessibility Audits

Score 99/100 — 2 failing, 32 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.

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
Footer Navigation `body.ow-corporate-home-template > div#wrapper > footer > h5#footer-nav`

These are opportunities to improve keyboard navigation in your application.

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
people-of-progress `div.component > div.component-content > div.wkbuttonlarge-link > a.btn-link`
Privacy & Cookie Notice `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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]`s are contained by their required parent element

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

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

●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

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

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

●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 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

○Form elements have associated labels

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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