Skip to content
https://diagrams.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
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
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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 Present
✗ 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
No navigation patterns
FIX
No navigation patterns
Info::
1 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 1 <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
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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Lighthouse Accessibility Audits
Action
Score 70/100 — 9 failing, 19 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

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
Share with everyone Don't worry about licenses or platforms, it just works. P… div.container > div.row > div.col-lg-5 > ul.nav

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
Share with everyone Don't worry about licenses or platforms, it just works. div.col-lg-5 > ul.nav > li.nav-item > a#pills-one-code-features-tab
Powerful features Collaborate with shared cursors in real-time. draw.io has ev… div.col-lg-5 > ul.nav > li.nav-item > a#pills-two-code-features-tab
Privacy first Store your data wherever you want to. We cannot access your data. div.col-lg-5 > ul.nav > li.nav-item > a#pills-three-code-features-tab

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.js-form-message > div.input-group > div.input-group-append > button.btn div.js-form-message > div.input-group > div.input-group-append > button.btn

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
draw.io div#logoAndNav > nav.js-mega-menu > a.navbar-brand > span.u-header__navbar-brand-text
Bring your storage to our online tool, or save locally with the desktop app. div.row > div.col-lg-5 > div.mb-5 > p
Describe your diagram: div.container > div.row > div.col-lg-5 > p.small
Start div.row > div.col-lg-5 > div.mb-3 > a#startButton
Download div.row > div.col-lg-5 > div.mb-3 > a.btn
No login or registration required. Diagram generation uses OpenAI. div.container > div.row > div.col-lg-5 > p.small
Share with everyone a#pills-one-code-features-tab > div.media > div.media-body > h3.h6
Don't worry about licenses or platforms, it just works. a#pills-one-code-features-tab > div.media > div.media-body > p.mb-0
Collaborate with shared cursors in real-time. draw.io has everything you expect… a#pills-two-code-features-tab > div.media > div.media-body > p.mb-0
Store your data wherever you want to. We cannot access your data. a#pills-three-code-features-tab > div.media > div.media-body > p.mb-0
More features div.col-lg-7 > div.w-md-80 > p.mb-0 > a
Example diagrams & templates div.col-lg-7 > div.w-md-80 > p.mb-0 > a
Works with Google Drive and Google Workplace (G Suite). div.container > div.row > div.col-sm-6 > p
Google Drive div.row > div.col-sm-6 > p > a
Google Workplace div.row > div.col-sm-6 > p > a
Works with OneDrive and Sharepoint. Office 365 and Microsoft Teams apps provide… div.container > div.row > div.col-sm-6 > p
OneDrive and Sharepoint div.row > div.col-sm-6 > p > a
Office 365 div.row > div.col-sm-6 > p > a
Microsoft Teams div.row > div.col-sm-6 > p > a
Highest-rated Confluence app, delivered by us as draw.io. Also for Jira. div.container > div.row > div.col-sm-6 > p
Confluence app div.row > div.col-sm-6 > p > a
Jira div.row > div.col-sm-6 > p > a
Works with GitHub, GitLab and Dropbox for visual documentation in distributed t… div.container > div.row > div.col-sm-6 > p
GitHub div.row > div.col-sm-6 > p > a
GitLab div.row > div.col-sm-6 > p > a
Dropbox div.row > div.col-sm-6 > p > a
Download draw.io Desktop for offline use, or draw.io for VSCode.* div.container > div.row > div.col-sm-6 > p
draw.io Desktop div.row > div.col-sm-6 > p > a
draw.io for VSCode div.row > div.col-sm-6 > p > a
Embed and edit diagrams directly with the draw.io for Notion Chrome extension. div.container > div.row > div.col-sm-6 > p
draw.io for Notion Chrome extension div.row > div.col-sm-6 > p > a
See more div.container > div.text-center > div.mb-3 > a.btn
Start Now div.container > div.text-center > div.mb-3 > a.btn
* Third-party integration. main#content > div.container > div.text-center > p.small

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
OneDrive and Sharepoint div.row > div.col-sm-6 > p > a
Office 365 div.row > div.col-sm-6 > p > a
Microsoft Teams div.row > div.col-sm-6 > p > a
Confluence app div.row > div.col-sm-6 > p > a
Jira div.row > div.col-sm-6 > p > a
GitHub div.row > div.col-sm-6 > p > a
GitLab div.row > div.col-sm-6 > p > a
Dropbox div.row > div.col-sm-6 > p > a
draw.io for Notion Chrome extension div.row > div.col-sm-6 > p > a

These are opportunities to improve the legibility of your content.

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
Google Workplace and Google Drive div.col-sm-6 > div.media > div.media-body > h4.h6

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Tables and lists

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
Share with everyone Don't worry about licenses or platforms, it just works. div.row > div.col-lg-5 > ul.nav > li.nav-item
Powerful features Collaborate with shared cursors in real-time. draw.io has ev… div.row > div.col-lg-5 > ul.nav > li.nav-item
Privacy first Store your data wherever you want to. We cannot access your data. div.row > div.col-lg-5 > ul.nav > li.nav-item

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
draw.io div.u-header__section > div#logoAndNav > nav.js-mega-menu > a.navbar-brand
draw.io div.container > div.row > div.col-lg-4 > a.d-inline-flex
○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
●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.
●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
●Document has a `<title>` element
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 a valid value for its `[lang]` attribute
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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

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

A
Heading Hierarchy
15 headings, 1 skip(s)
PASS
15 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Security-first diagramming for teams.
  • H2 Diagram files created in 2005 will load in the app today
  • H3 Share with everyone
  • H4 Powerful features
  • H4 Privacy first
  • H2 Our range of draw.io branded integrations
  • H4 Google Workplace and Google Drive skipped
  • H4 Sharepoint and OneDrive
  • H4 Atlassian
  • H4 Git and Dropbox
  • H4 Desktop
  • H4 Notion
  • H4 Help and advice
  • H4 About us
  • H4 Search the site

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

A+
Alt Text Quality
All 17 images OK
PASS
All 17 images OK
Info::
17 image(s) with good alt text
17 images 17 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="diagramDescription">
Info::
2 control(s) properly labeled
3 controls
2 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputsearchSearch Frontaria-label
#signupSrEmailtextSearch sitearia-label
#diagramDescriptiontext(e.g. 5 tier sequence diagram to order pizza online)placeholder only

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

<input type="text" id="diagramDescription">

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

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 Security-first diagr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Diagram files create…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our range of draw.io…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Share with everyone21.00:13.0:1
#000000
#FFFFFF
Pass
title draw.io21.00:14.5:1
#000000
#FFFFFF
Pass
a Jump to21.00:14.5:1
#000000
#FFFFFF
Pass
a Help21.00:14.5:1
#000000
#FFFFFF
Pass
a Help21.00:14.5:1
#000000
#FFFFFF
Pass
span draw.io21.00:14.5:1
#000000
#FFFFFF
Pass
a Integrations21.00:14.5:1
#000000
#FFFFFF
Pass
a Utilities21.00:14.5:1
#000000
#FFFFFF
Pass
a Pricing21.00:14.5:1
#000000
#FFFFFF
Pass
a FAQ21.00:14.5:1
#000000
#FFFFFF
Pass
a Terms & Conditions21.00:14.5:1
#000000
#FFFFFF
Pass
a Privacy & Policy21.00:14.5:1
#000000
#FFFFFF
Pass
a Specialty21.00:14.5:1
#000000
#FFFFFF
Pass
a Status21.00:14.5:1
#000000
#FFFFFF
Pass
a Blog21.00:14.5:1
#000000
#FFFFFF
Pass
a Security21.00:14.5:1
#000000
#FFFFFF
Pass
span App Marketplace21.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.

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

Send Feedback