Skip to content
https://www.databricks.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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
Favicon & Branding
Action
17 icon(s) detected
REVIEW
17 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 15 fail WCAG AA
REVIEW

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

5 pass 15 fail WCAG AA
h1 The
1.25:1
#000000
on
#0B2026
needs 3.0:1 (large text)
32px · bottom of viewport
h1 your
1.25:1
#000000
on
#0B2026
needs 3.0:1 (large text)
32px · bottom of viewport
h1 AI agents deserve
1.25:1
#000000
on
#0B2026
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Build and run apps, agents
1.25:1
#000000
on
#0B2026
needs 3.0:1 (large text)
24px · bottom of viewport
h2 and AI on your data
1.25:1
#000000
on
#0B2026
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How innovators win with data and AI
1.25:1
#000000
on
#0B2026
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Recognized for innovation in data and AI
1.25:1
#000000
on
#0B2026
needs 3.0:1 (large text)
24px · bottom of viewport
h2 In the spotlight
1.25:1
#000000
on
#0B2026
needs 3.0:1 (large text)
24px · bottom of viewport
h3 The Databricks Platform
1.25:1
#000000
on
#0B2026
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Modern applications need a lakebase
1.25:1
#000000
on
#0B2026
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Build AI agents that work in the real wo…
1.25:1
#000000
on
#0B2026
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Intelligent analytics for all
1.25:1
#000000
on
#0B2026
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Govern data and AI on one platform
1.25:1
#000000
on
#0B2026
needs 3.0:1 (large text)
19px · bottom of viewport
h3 The best warehouse is still a lakehouse
1.25:1
#000000
on
#0B2026
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Build better data pipelines faster
1.25:1
#000000
on
#0B2026
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The1.25:13.0:1
#000000
#0B2026
Fail
h1 your1.25:13.0:1
#000000
#0B2026
Fail
h1 AI agents deserve1.25:13.0:1
#000000
#0B2026
Fail
h2 Build and run apps, …1.25:13.0:1
#000000
#0B2026
Fail
h2 and AI on your data1.25:13.0:1
#000000
#0B2026
Fail
h2 How innovators win w…1.25:13.0:1
#000000
#0B2026
Fail
h2 Recognized for innov…1.25:13.0:1
#000000
#0B2026
Fail
h2 In the spotlight1.25:13.0:1
#000000
#0B2026
Fail
h3 The Databricks Platf…1.25:13.0:1
#000000
#0B2026
Fail
h3 Modern applications …1.25:13.0:1
#000000
#0B2026
Fail
h3 Build AI agents that…1.25:13.0:1
#000000
#0B2026
Fail
h3 Intelligent analytic…1.25:13.0:1
#000000
#0B2026
Fail
h3 Govern data and AI o…1.25:13.0:1
#000000
#0B2026
Fail
h3 The best warehouse i…1.25:13.0:1
#000000
#0B2026
Fail
h3 Build better data pi…1.25:13.0:1
#000000
#0B2026
Fail
title Databricks: Leading …21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main content21.00:14.5:1
#000000
#FFFFFF
Pass
a Login21.00:14.5:1
#000000
#FFFFFF
Pass
button Why Databricks21.00:14.5:1
#000000
#FFFFFF
Pass
span Discover21.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.

A+
Landmark Structure
3 landmarks
PASS
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV "Main Navigation" MAIN CONTENTINFO footer
A+
Heading Hierarchy
16 headings
PASS
16 headings
Info::
Single H1 present
  • H1 The database your AI agents deserve
  • H2 Build and run apps, agents and AI on your data
  • H3 The Databricks Platform
  • H3 Modern applications need a lakebase
  • H3 Build AI agents that work in the real world
  • H3 Intelligent analytics for all
  • H3 Govern data and AI on one platform
  • H3 The best warehouse is still a lakehouse
  • H3 Build better data pipelines faster
  • H4 Lakebase
  • H4 Genie
  • H4 Agent Bricks
  • H4 Lakehouse
  • H2 How innovators win with data and AI
  • H2 Recognized for innovation in data and AI
  • H2 In the spotlight
A+
Alt Text Quality
All 27 images OK
PASS
All 27 images OK
Info::
21 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
27 images 6 good alt text 21 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Databricks
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Databricks ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name Databricks Display Mode standalone Icons 8 icon(s)
A
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 27 passed
PASS
92

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 parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Navigate between customer stories div.new-row-item > div.large-step-slider > div.flex > div.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.

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
See Careers div.inner-wrapper > div.rich-text-body > p > a
at Databricks div.inner-wrapper > div.rich-text-body > p > a

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
173B transactions Mastercard tackles AI governance Watch the video div.swiper-wrapper > div#carousel_item-step-1_heading > div > a.group-arrow-exclude-hover
Leader in the Gartner® Magic Quadrant™ for Data Science and Machine Learning 
 … div.w-full > div.flex > div.w-full > a.bg-navy-600
Databricks has been recognized by G2 as a leader across key categories for Wint… div.w-full > div.flex > div.w-full > a.bg-navy-800
REPORT Key findings in multi-agent systems, AI use cases, evaluations and more … div.contents > section > div.grid > a.variant-spotlight
VIRTUAL EVENT Learn how to create and deploy apps on Databricks. Join us on May… div.contents > section > div.grid > a.variant-spotlight
JUNE 15–18 / SAN FRANCISCO The must-attend event for data and AI professionals … div.contents > section > div.grid > a.variant-spotlight
RESEARCH REPORT AI agents need a new martech model — a blueprint for what’s nex… div.contents > section > div.grid > a.variant-spotlight
○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]`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.
●`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
●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
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○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.
○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.

Send Feedback