Skip to content
https://docker.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Heading Hierarchy
Action
49 headings, 6 skip(s)
FIX
49 headings, 6 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.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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 A safer container ecosystem, for everyone
  • H2 Near-zero CVE images, now accessible to everyone
  • H4 Apache 2.0 freedom skipped
  • H4 Minimal and distroless images
  • H4 Up to 95% CVE reduction
  • H4 Extended Lifecycle Support for long-term protection
  • H4 Start secure, customize easily
  • H4 1000+ images and applications
  • H2 The easiest, most secure way to run MCP for your LLMs
  • H4 All your MCP tools in one place skipped
  • H4 Launch-ready MCP servers + clients
  • H4 Security you don’t have to think about
  • H2 Your full agentic stack. Just one command away.
  • H4 Compose for agents skipped
  • H4 Deploy anywhere
  • H4 Security out of the box
  • H2 The simplest way to build and run software. Anywhere.
  • H4 Everything you need to build locally skipped
  • H4 Security built in, confidence by default
  • H4 Start from trusted content
  • H2 Frictionless for devs, secure for teams, a joy for everyone
  • H2 Security and speed are not a paradox anymore
  • H4 Five pillars of supply chain security skipped
  • H4 Run Helm charts, hardened by Docker
  • H4 Join the move to a safer container ecosystem
  • H2 Get access to industry-leading CVE remediation SLA
  • H2 Accelerate every workflow. From apps to agents.
  • H4 Build once, run anywhere skipped
  • H4 Containers + MCP: better together
  • H4 From client to server: the new kinds
  • H2 Share AI agents just like you share containers.
  • H2 Where developers build, share, and run secure software
  • H2 14M+
  • H2 11B+
  • H2 24M+
  • H2 Build better, together
  • H2 Products
  • H2 Features
  • H2 Developers
  • H2 Pricing
  • H2 Company
  • H2 Languages
  • H2 Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Functional Cookies
  • H4 Strictly Necessary Cookies
  • H4 Performance Cookies
  • H4 Targeting Cookies
  • H3 Cookie List

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

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

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

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

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

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

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
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
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 Page not found | Docker ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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 Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 89/100 — 4 failing, 26 passed
REVIEW
89

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.

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
MCP div.wp-block-ponyo-boone > div.wp-block-ponyo-tatiana > a.wp-block-ponyo-tab > div.tab-text
Agents div.wp-block-ponyo-boone > div.wp-block-ponyo-tatiana > a.wp-block-ponyo-tab > div.tab-text
Containers div.wp-block-ponyo-boone > div.wp-block-ponyo-tatiana > a.wp-block-ponyo-tab > div.tab-text
Cookies Settings div.container > div.wp-block-ponyo-franklin > div.wp-block-ponyo-foster > button#ot-sdk-btn

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
Apache 2.0 freedom div.wp-block-ponyo-erika > div.container > div.copy-container > h4.wp-block-ponyo-heading
Five pillars of supply chain security div.wp-block-ponyo-erika > div.container > div.copy-container > h4.wp-block-ponyo-heading
Build once, run anywhere div.wp-block-ponyo-erika > div.container > div.copy-container > h4.wp-block-ponyo-heading

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.wp-block-group > header.site-header > div.wp-block-group > a.logo div.wp-block-group > header.site-header > div.wp-block-group > a.logo
div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a
div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a
div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a
div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a
div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a
div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a div.wp-block-ponyo-newsletter-social > ul.social-wrap > li > a

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.

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
Products Products Overview Docker Desktop Docker Hub Docker Scout Docker Build … div.wp-block-ponyo-freddie > div.menu-container > div.wp-block-ponyo-faith > ul
Features Command Line Interface IDE Extensions Container Runtime Docker Extensi… div.wp-block-ponyo-freddie > div.menu-container > div.wp-block-ponyo-faith > ul
Developers Documentation Getting Started Trainings Extensions SDK Community Ope… div.wp-block-ponyo-freddie > div.menu-container > div.wp-block-ponyo-faith > ul
Pricing Personal Pro Team Business Premium Support and TAM Pricing FAQ Contact … div.wp-block-ponyo-freddie > div.menu-container > div.wp-block-ponyo-faith > ul
Company About Us What is a Container Blog Why Docker Trust Customer Success Par… div.wp-block-ponyo-freddie > div.menu-container > div.wp-block-ponyo-faith > ul
Languages English 日本語 div.wp-block-ponyo-freddie > div.menu-container > div.wp-block-ponyo-faith > ul

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

○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
●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.
●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
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●`[lang]` attributes have a valid value
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○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
○`<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
○Links are distinguishable without relying on color.
○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.
○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.
○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.
A+
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Ponyo Menu" MAIN CONTENTINFO footer
A+
Alt Text Quality
All 29 images OK
PASS
All 29 images OK
Info::
5 decorative image(s) correctly marked
Info::
24 image(s) with good alt text
29 images 24 good alt text 5 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 10 controls have issues
PASS
1 of 10 controls have issues
Critical::
1 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-100000">
Info::
9 control(s) properly labeled
10 controls
9 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#wp-block-search__input-1searchSearchfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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

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 A safer container ec…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Near-zero CVE images…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The easiest, most se…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your full agentic st…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The simplest way to …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Frictionless for dev…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Security and speed a…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get access to indust…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Accelerate every wor…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Share AI agents just…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Where developers bui…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 14M+21.00:13.0:1
#000000
#FFFFFF
Pass
h2 11B+21.00:13.0:1
#000000
#FFFFFF
Pass
h2 24M+21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Build better, togeth…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Products21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Features21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Developers21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Pricing21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Company21.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.

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

Send Feedback