Skip to content
https://www.dagster.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
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::
6 navigation landmark(s) detected
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 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
10 landmarks
REVIEW
10 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
1 of 6 <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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
A+
Heading Hierarchy
36 headings
PASS
36 headings
Info::
Single H1 present
  • H1 Your platform for AI and data pipelines.
  • H2 Trusted by teams building modern data platforms, worldwide
  • H2 Battle tested data orchestration
  • H3 ETL & ELT Pipelines
  • H3 Data Transformation
  • H3 AI & ML Workflows
  • H2 Integrated observability
  • H3 Data Catalog & Lineage
  • H3 Monitoring & Alerting
  • H3 Realtime Health Metrics
  • H2 Activate your data with Compass
  • H3 Data-driven Decisions in Seconds
  • H3 Unlock the Power of Your Warehouse
  • H3 Governed by the Data Team
  • H2 Enterprise ready
  • H3 Roles & permissions
  • H3 SOC 2 Type II, HIPAA and beyond
  • H3 Flexible deployment options
  • H3 Multi-tenant instances
  • H3 Audit logs and retention policies
  • H3 Enterprise support
  • H2 Ship data and AI products faster.
  • H2 Trusted by data teams.Built for scale. Ready for you.
  • H2 New and noteworthy
  • H3 Multi-Tenancy for Modern Data Platforms
  • H3 Deep Dive: Building a Cross-Workspace Control Plane for Databricks
  • H3 Dagster Running Dagster: How We Use Compass for AI Analytics
  • H3 Monorepos, the hub-and-spoke model, and Copybara
  • H3 Making Dagster Easier to Contribute to in an AI-Driven World
  • H3 DataOps with Dagster: A Practical Guide to Building a Reliable Data Platform
  • H3 How Magenta Telekom Built the Unsinkable Data Platform
  • H3 Scaling FinTech: How smava achieved zero downtime with Dagster
  • H3 Zero Incidents, Maximum Velocity: How HIVED achieved 99.9% pipeline reliability with Dagster
  • H3 Modernize Your Data Platform for the Age of AI
  • H3 Download the eBook on How to Scale Data Teams
  • H3 Download the eBook Primer on How to Build Data Platforms
A+
Alt Text Quality
All 133 images OK
PASS
All 133 images OK
Info::
50 decorative image(s) correctly marked
Info::
83 image(s) with good alt text
133 images 83 good alt text 50 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#osano-cm-dialog-toggle--category_MARKETINGcheckboxnone
#osano-cm-dialog-toggle--category_PERSONALIZATIONcheckboxnone
#osano-cm-dialog-toggle--category_ANALYTICScheckboxnone
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 Your platform for AI…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trusted by teams bui…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Battle tested data o…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Integrated observabi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Enterprise ready21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ship data and AI pro…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trusted by data team…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Built for scale.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ready for you.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 New and noteworthy21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ETL & ELT Pipelines21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Data Transformation21.00:13.0:1
#000000
#FFFFFF
Pass
h3 AI & ML Workflows21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Data Catalog & Linea…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Monitoring & Alertin…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Realtime Health Metr…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Unlock the Power of …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Governed by the Data…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Roles & permissions21.00:13.0:1
#000000
#FFFFFF
Pass
h3 SOC 2 Type II, HIPAA…21.00:13.0: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
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 28 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 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
div.padding-global > div.container-medium > div > div#fs_cmssort_button div.padding-global > div.container-medium > div > div#fs_cmssort_button

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
Targeted Advertising ul#osano-cm-dialog-toggle-group > li.osano-cm-list__list-item > label.osano-cm-list-item__toggle > span.osano-cm-toggle__label
Personalization ul#osano-cm-dialog-toggle-group > li.osano-cm-list__list-item > label.osano-cm-list-item__toggle > span.osano-cm-toggle__label
Analytics ul#osano-cm-dialog-toggle-group > li.osano-cm-list__list-item > label.osano-cm-list-item__toggle > span.osano-cm-toggle__label

These are opportunities to improve the legibility of your content.

○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
●Image elements have `[alt]` attributes
●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
●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
●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
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○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.
○Elements with visible text labels have matching accessible names.
○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