Skip to content
https://veeam.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
5
REVIEW
7
PASS
1
INFO
0
Checks
13
1 PASS 7 REVIEW 5 FIX
F
Alt Text Quality
Action
9 of 88 images have issues
FIX
9 of 88 images have issues
Critical::
9 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::
11 decorative image(s) correctly marked
Info::
68 image(s) with good alt text
88 images 68 good alt text 11 decorative 9 missing
IssueCount
missing9 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

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
No navigation patterns
FIX
No navigation patterns
Info::
3 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 3 <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
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <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 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

C
Form Accessibility
Action
3 of 4 controls have issues
REVIEW
3 of 4 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-01gvkvh7xniz">; <textarea name="h-captcha-response" id="h-captcha-response-01gvkvh7xniz">
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">
Info::
1 control(s) properly labeled
4 controls
1 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#gsc-i-id1textsearcharia-label
qtext(Search)placeholder only
#g-recaptcha-response-01gvkvh7xniztextarea(none)none
#h-captcha-response-01gvkvh7xniztextarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-01gvkvh7xniz">; <textarea name="h-captcha-response" id="h-captcha-response-01gvkvh7xniz">

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

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 Veeam logo ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
14 icon(s) detected
REVIEW
14 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Info::
Name present: veeamMoeTest
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name veeamMoeTest ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓
Name veeamMoeTest Display Mode standalone Icons 1 icon(s)
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 Agent Commander
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Agent Commander
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Data Trust and
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Resilience Report
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Detect AI risks. Protect AI systems. Und…
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Learn how data leaders and practitioners…
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 govern AI, and recover fast in the agent…
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Data Trust and
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Resilience Report
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Detect AI risks. Protect AI systems. Und…
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Learn how data leaders and practitioners…
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 govern AI, and recover fast in the agent…
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Data Trust and
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Resilience Report
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Accelerate safe AI at scale
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Innovate at the speed of AI and
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 reduce risk at the same time
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The risks shaping your business aren’t…
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How resilient is the data your AI depend…
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore the latest news from Veeam
1.78:1
#000000
on
#35383C
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Agent Commander1.78:13.0:1
#000000
#35383C
Fail
h1 Agent Commander1.78:13.0:1
#000000
#35383C
Fail
h2 Data Trust and1.78:13.0:1
#000000
#35383C
Fail
h2 Resilience Report1.78:13.0:1
#000000
#35383C
Fail
h2 Detect AI risks. Pro…1.78:13.0:1
#000000
#35383C
Fail
h2 Learn how data leade…1.78:13.0:1
#000000
#35383C
Fail
h2 govern AI, and recov…1.78:13.0:1
#000000
#35383C
Fail
h2 Data Trust and1.78:13.0:1
#000000
#35383C
Fail
h2 Resilience Report1.78:13.0:1
#000000
#35383C
Fail
h2 Detect AI risks. Pro…1.78:13.0:1
#000000
#35383C
Fail
h2 Learn how data leade…1.78:13.0:1
#000000
#35383C
Fail
h2 govern AI, and recov…1.78:13.0:1
#000000
#35383C
Fail
h2 Data Trust and1.78:13.0:1
#000000
#35383C
Fail
h2 Resilience Report1.78:13.0:1
#000000
#35383C
Fail
h2 Accelerate safe AI …1.78:13.0:1
#000000
#35383C
Fail
h2 Innovate at the sp…1.78:13.0:1
#000000
#35383C
Fail
h2 reduce risk at the…1.78:13.0:1
#000000
#35383C
Fail
h2 The risks shaping yo…1.78:13.0:1
#000000
#35383C
Fail
h2 How resilient is the…1.78:13.0:1
#000000
#35383C
Fail
h2 Explore the latest n…1.78:13.0:1
#000000
#35383C
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.

C
Lighthouse Accessibility Audits
Action
Score 70/100 — 10 failing, 24 passed
REVIEW
70

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Close body.header-component__button-first--inherited > div#wistia-0083ah0jm6-1_popover_container
Close body.header-component__button-first--inherited > div#wistia-hubnopr482-1_popover_container
Close body.header-component__button-first--inherited > div#wistia-szqqbsgphc-1_popover_container

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI assistant body.header-component__button-first--inherited > q-focus-sentinel > div
After AI assistant body.header-component__button-first--inherited > q-focus-sentinel > div
AI assistant, start div#qualified-multimodal-host > div
AI assistant, end div#qualified-multimodal-host > div

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.owl-wrap > div.h-leader__content > div.owl-nav > button.owl-prev div.owl-wrap > div.h-leader__content > div.owl-nav > button.owl-prev
div.owl-wrap > div.h-leader__content > div.owl-nav > button.owl-next div.owl-wrap > div.h-leader__content > div.owl-nav > button.owl-next
div.owl-wrap > div.h-leader__content > div.owl-dots > button.owl-dot div.owl-wrap > div.h-leader__content > div.owl-dots > button.owl-dot
div.owl-wrap > div.h-leader__content > div.owl-dots > button.owl-dot div.owl-wrap > div.h-leader__content > div.owl-dots > button.owl-dot
div.owl-wrap > div.h-leader__content > div.owl-dots > button.owl-dot div.owl-wrap > div.h-leader__content > div.owl-dots > button.owl-dot
div.owl-wrap > div.h-leader__content > div.owl-dots > button.owl-dot div.owl-wrap > div.h-leader__content > div.owl-dots > button.owl-dot
div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot
div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot
div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot
div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot
section.h-news > div#news-carousel > div.h-news-carousel__pagination > button.owl-dot section.h-news > div#news-carousel > div.h-news-carousel__pagination > button.owl-dot
section.h-news > div#news-carousel > div.h-news-carousel__pagination > button.owl-dot section.h-news > div#news-carousel > div.h-news-carousel__pagination > button.owl-dot
section.h-news > div#news-carousel > div.h-news-carousel__pagination > button.owl-dot section.h-news > div#news-carousel > div.h-news-carousel__pagination > button.owl-dot
section.h-news > div#news-carousel > div.h-news-carousel__pagination > button.owl-dot section.h-news > div#news-carousel > div.h-news-carousel__pagination > button.owl-dot
div.g-extra-wrapper > div.h-resources-carousel > div.h-resources-carousel__pagination > button.owl-dot div.g-extra-wrapper > div.h-resources-carousel > div.h-resources-carousel__pagination > button.owl-dot
div.g-extra-wrapper > div.h-resources-carousel > div.h-resources-carousel__pagination > button.owl-dot div.g-extra-wrapper > div.h-resources-carousel > div.h-resources-carousel__pagination > button.owl-dot
div.g-extra-wrapper > div.h-resources-carousel > div.h-resources-carousel__pagination > button.owl-dot div.g-extra-wrapper > div.h-resources-carousel > div.h-resources-carousel__pagination > button.owl-dot
div.g-extra-wrapper > div.h-resources-carousel > div.h-resources-carousel__pagination > button.owl-dot div.g-extra-wrapper > div.h-resources-carousel > div.h-resources-carousel__pagination > button.owl-dot
div.g-extra-wrapper > div.h-resources-carousel > div.h-resources-carousel__pagination > button.owl-dot div.g-extra-wrapper > div.h-resources-carousel > div.h-resources-carousel__pagination > button.owl-dot

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.footer__container > div.footer__badges > span.footer__badge > img div.footer__container > div.footer__badges > span.footer__badge > img
div.footer__container > div.footer__badges > span.footer__badge > img div.footer__container > div.footer__badges > span.footer__badge > img
div.footer__container > div.footer__badges > span.footer__badge > img div.footer__container > div.footer__badges > span.footer__badge > img
div.footer__container > div.footer__badges > span.footer__badge > img div.footer__container > div.footer__badges > span.footer__badge > img
div.footer__container > div.footer__badges > span.footer__badge > img div.footer__container > div.footer__badges > span.footer__badge > img
div.footer__container > div.footer__badges > span.footer__badge > img div.footer__container > div.footer__badges > span.footer__badge > img
div.footer__container > div.footer__badges > span.footer__badge > img div.footer__container > div.footer__badges > span.footer__badge > img

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.footer__container > div.footer__connect > div.footer__social > a.footer__social-link div.footer__container > div.footer__connect > div.footer__social > a.footer__social-link
div.footer__container > div.footer__connect > div.footer__social > a.footer__social-link div.footer__container > div.footer__connect > div.footer__social > a.footer__social-link
div.footer__container > div.footer__connect > div.footer__social > a.footer__social-link div.footer__container > div.footer__connect > div.footer__social > a.footer__social-link
div.footer__container > div.footer__connect > div.footer__social > a.footer__social-link div.footer__container > div.footer__connect > div.footer__social > a.footer__social-link
div.footer__container > div.footer__connect > div.footer__social > a.footer__social-link div.footer__container > div.footer__connect > div.footer__social > a.footer__social-link

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.

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
ACCEPT ALL div#cookiescript_toppart > div#cookiescript_rightpart > div#cookiescript_buttons > div#cookiescript_accept
REJECT ALL div#cookiescript_toppart > div#cookiescript_rightpart > div#cookiescript_buttons > div#cookiescript_reject

These are opportunities to improve the legibility of your content.

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
Recover and rollback with precision Keep operations resilient against modern t… div.g-extra-wrapper > div.h-set-apart__wrapper > div.h-set-apart__content-part-mob > ul.h-set-apart__content-list
Veeam Named Leader and Outperformer in the GigaOm Radar Report GET THE INSIGHTS… section.h-news-resources-wrapper > section.h-news > div#news-carousel > ul.h-news-carousel__cards
Economics of Cyber Extortion Insights from the frontline of ransomware negotia… section.h-resources > div.g-extra-wrapper > div.h-resources-carousel > ul.h-resources-carousel__cards

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
Recover and rollback with precision Keep operations resilient against modern t… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-set-apart__content-list-item
Unleash the value of data for AI Build end-to-end safe AI with a context-aware… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-set-apart__content-list-item
Understand data everywhere The Data Command Graph maps all your data—structure… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-set-apart__content-list-item
Secure data and AI Automated governance enforces least-privileges access, remo… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-set-apart__content-list-item
Recover and rollback with precision Keep operations resilient against modern t… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-set-apart__content-list-item
Unleash the value of data for AI Build end-to-end safe AI with a context-aware… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-set-apart__content-list-item
Understand data everywhere The Data Command Graph maps all your data—structure… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-set-apart__content-list-item
Secure data and AI Automated governance enforces least-privileges access, remo… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-set-apart__content-list-item
Veeam Named Leader and Outperformer in the GigaOm Radar Report GET THE INSIGHTS div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-news-carousel__slide
Veeam Acquires Securiti AI READ PRESS RELEASE div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-news-carousel__slide
Find out your organization's SaaS data protection strengths and gaps TAKE THE A… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-news-carousel__slide
Deploying Secure and Frictionless Backup READ THE FULL REPORT div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-news-carousel__slide
Veeam Named Leader and Outperformer in the GigaOm Radar Report GET THE INSIGHTS div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-news-carousel__slide
Veeam Acquires Securiti AI READ PRESS RELEASE div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-news-carousel__slide
Find out your organization's SaaS data protection strengths and gaps TAKE THE A… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-news-carousel__slide
Deploying Secure and Frictionless Backup READ THE FULL REPORT div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-news-carousel__slide
Economics of Cyber Extortion Insights from the frontline of ransomware negotia… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-resources-carousel__slide
be: Ready — Leadership Strategies for Data Resilience Actionable insight for t… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-resources-carousel__slide
CXO Executive Exchange Conversations that move industries and shape the future… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-resources-carousel__slide
Data Trust and Resilience Report 2026 Achieve higher data trust and faster rec… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-resources-carousel__slide
Wake Up! — Real Stories from Inside the Breach Go inside real-world breaches t… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-resources-carousel__slide
Economics of Cyber Extortion Insights from the frontline of ransomware negotia… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-resources-carousel__slide
be: Ready — Leadership Strategies for Data Resilience Actionable insight for t… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-resources-carousel__slide
CXO Executive Exchange Conversations that move industries and shape the future… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-resources-carousel__slide
Data Trust and Resilience Report 2026 Achieve higher data trust and faster rec… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-resources-carousel__slide
Wake Up! — Real Stories from Inside the Breach Go inside real-world breaches t… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-resources-carousel__slide
Economics of Cyber Extortion Insights from the frontline of ransomware negotia… div.owl-stage-outer > div.owl-stage > div.owl-item > li.h-resources-carousel__slide

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
div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot
div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot
div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot
div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot div.h-set-apart__content-part-mob > ul.h-set-apart__content-list > div.owl-dots > button.owl-dot

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
Data Trust and Resilience Report 2026 Achieve higher data trust and faster rec… div.owl-stage > div.owl-item > li.h-resources-carousel__slide > a.h-resources-carousel__card
○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
●`[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
●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.
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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 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.
○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.
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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
61 headings
PASS
61 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 Data Trust and Resilience Report 2026
  • H3 Introducing
  • H1 Agent Commander
  • H2 Detect AI risks. Protect AI systems. Undo AI mistakes.
  • H2 Data & AI TrustCONVERGEfor the Agentic Era
  • H2 Learn how data leaders and practitioners secure data, govern AI, and recover fast in the agentic era.
  • H3 May 12 | Online and On Demand
  • H2 Data Trust and Resilience Report 2026
  • H3 Introducing
  • H1 Agent Commander duplicate H1
  • H2 Detect AI risks. Protect AI systems. Undo AI mistakes.
  • H2 Data & AI TrustCONVERGEfor the Agentic Era
  • H2 Learn how data leaders and practitioners secure data, govern AI, and recover fast in the agentic era.
  • H3 May 12 | Online and On Demand
  • H2 Data Trust and Resilience Report 2026
  • H2 Accelerate safe AI at scale
  • H3 Fortify data, identity, & apps with Zero Trust Resilience
  • H3 Secure data, govern AI, and automate compliance
  • H3 Confidently use AI to multiply your productivity, not risk
  • H3 Response time matters
  • H3 Make cyber resilience a repeatable discipline, not a reaction
  • H2 Innovate at the speed of AI and reduce risk at the same time
  • H3 Understand data everywhere
  • H3 Secure data and AI
  • H3 Recover and rollback with precision
  • H3 Unleash the value of data for AI
  • H3 Understand data everywhere
  • H3 Secure data and AI
  • H3 Recover and rollback with precision
  • H3 Unleash the value of data for AI
  • H2 The risks shaping your business aren’t siloed anymore
  • H2 How resilient is the data your AI depends on?
  • H3 Trusted by 70% of the Global 2000 and 82% of the Fortune 500
  • H4 Over 550,000 customers trust Veeam
  • H2 Explore the latest news from Veeam
  • H3 Veeam Named Leader and Outperformer in the GigaOm Radar Report
  • H3 Veeam Acquires Securiti AI
  • H3 Find out your organization's SaaS data protection strengths and gaps
  • H3 Deploying Secure and Frictionless Backup
  • H3 Veeam Named Leader and Outperformer in the GigaOm Radar Report
  • H3 Veeam Acquires Securiti AI
  • H3 Find out your organization's SaaS data protection strengths and gaps
  • H3 Deploying Secure and Frictionless Backup
  • H2 The research, strategies, and stories redefining data leadership
  • H2 Data Trust and Resilience Report 2026
  • H2 Wake Up! — Real Stories from Inside the Breach
  • H2 Economics of Cyber Extortion
  • H2 be: Ready — Leadership Strategies for Data Resilience
  • H2 CXO Executive Exchange
  • H2 Economics of Cyber Extortion
  • H2 be: Ready — Leadership Strategies for Data Resilience
  • H2 CXO Executive Exchange
  • H2 Data Trust and Resilience Report 2026
  • H2 Wake Up! — Real Stories from Inside the Breach
  • H2 Economics of Cyber Extortion
  • H2 be: Ready — Leadership Strategies for Data Resilience
  • H2 CXO Executive Exchange
  • H2 Data Trust and Resilience Report 2026
  • H2 Wake Up! — Real Stories from Inside the Breach
  • H2 Economics of Cyber Extortion
  • H2 Let's build the foundation for safe AI at scale

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

Send Feedback