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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
D
Landmark Structure
Action
6 landmarks
FIX
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <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 (missing!) ASIDE "Open Cookie Preferences Modal" CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #0069ff
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 ModePartial Dark Mode
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::
2 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 2 <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
Heading Hierarchy
45 headings
REVIEW
45 headings
Info::
Single H1 present
Warning::
5 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H1 The Inference Cloud built for scale — without complexity or surprise costs.
  • H2 Gradient™ AI Inference Cloud
  • H2 (empty)
  • H2 Customers growing with DigitalOcean
  • H3 The cost of running ScraperAPI would be 250% more on AWS, as compared to DigitalOcean
  • H3 Empowering the Next Wave of AI Creators with fal and DigitalOcean
  • H3 It’s not only about the price, it’s also about proving stability, proving a quality level of support and understanding our business. These factors led us to continue to grow on DigitalOcean.
  • H3 Amorphous Data on DigitalOcean GPUs and Kubernetes
  • H3 We were previously on AWS but started migrating everything because we really love DigitalOcean in terms of cost and support. We saved a lot of money—we went from $120,000 to $30,000 [per month]
  • H3 How Servd Scaled Their Craft CMS Platform with DigitalOcean Kubernetes
  • H3 The VIP support has been excellent. If there’s an issue, it’s always engineers on the line, not somebody who is two steps removed from the people that know what’s going on.
  • H3 The cost of running ScraperAPI would be 250% more on AWS, as compared to DigitalOcean
  • H3 Empowering the Next Wave of AI Creators with fal and DigitalOcean
  • H3 It’s not only about the price, it’s also about proving stability, proving a quality level of support and understanding our business. These factors led us to continue to grow on DigitalOcean.
  • H3 Amorphous Data on DigitalOcean GPUs and Kubernetes
  • H3 We were previously on AWS but started migrating everything because we really love DigitalOcean in terms of cost and support. We saved a lot of money—we went from $120,000 to $30,000 [per month]
  • H3 How Servd Scaled Their Craft CMS Platform with DigitalOcean Kubernetes
  • H3 The VIP support has been excellent. If there’s an issue, it’s always engineers on the line, not somebody who is two steps removed from the people that know what’s going on.
  • H2 Persistent compute, high-throughput storage, scalable runtime environments—everything you need to go from “uhhh” to agent, fast.
  • H2 A unified inference cloud to build full-stack AI apps
  • H2 Stay on budget and grow your business
  • H2 Frustration-free support from real people
  • H2 Delight your customers by building on a reliable platform
  • H2 Dive in
  • H3 Get started with DigitalOcean’s Linux-based virtual machines
  • H3 How To Install and Use Docker on Ubuntu
  • H3 Run large language models like Ollama on H100 GPUs
  • H3 Build a Slack AI Chatbot with DigitalOcean Gradient Platform
  • H3 How to choose a cloud service provider
  • H3 Learn about open source AI platforms
  • H2 Get started for free
  • H2 Company
  • H2 Products
  • H2 Resources
  • H2 Solutions
  • H2 Contact
  • H2 Company
  • H2 Products
  • H2 Resources
  • H2 Solutions
  • H2 Contact

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 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 Missing
✓ Multiple Sizes Present
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 The Inference Cloud built for scale — …
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Gradient™ AI Inference Cloud
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Customers growing with DigitalOcean
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Persistent compute, high-throughput stor…
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 A unified inference cloud to build full-…
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Stay on budget and grow your business
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Frustration-free support from real peopl…
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Delight your customers by building on a …
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Dive in
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get started for free
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Company
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Products
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Resources
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Solutions
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Contact
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Company
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Products
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Resources
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Solutions
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Contact
1.27:1
#000000
on
#031B4E
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The Inference Cloud …1.27:13.0:1
#000000
#031B4E
Fail
h2 Gradient™ AI Infer…1.27:13.0:1
#000000
#031B4E
Fail
h2 Customers growing wi…1.27:13.0:1
#000000
#031B4E
Fail
h2 Persistent compute, …1.27:13.0:1
#000000
#031B4E
Fail
h2 A unified inference …1.27:13.0:1
#000000
#031B4E
Fail
h2 Stay on budget and g…1.27:13.0:1
#000000
#031B4E
Fail
h2 Frustration-free sup…1.27:13.0:1
#000000
#031B4E
Fail
h2 Delight your custome…1.27:13.0:1
#000000
#031B4E
Fail
h2 Dive in1.27:13.0:1
#000000
#031B4E
Fail
h2 Get started for free1.27:13.0:1
#000000
#031B4E
Fail
h2 Company1.27:13.0:1
#000000
#031B4E
Fail
h2 Products1.27:13.0:1
#000000
#031B4E
Fail
h2 Resources1.27:13.0:1
#000000
#031B4E
Fail
h2 Solutions1.27:13.0:1
#000000
#031B4E
Fail
h2 Contact1.27:13.0:1
#000000
#031B4E
Fail
h2 Company1.27:13.0:1
#000000
#031B4E
Fail
h2 Products1.27:13.0:1
#000000
#031B4E
Fail
h2 Resources1.27:13.0:1
#000000
#031B4E
Fail
h2 Solutions1.27:13.0:1
#000000
#031B4E
Fail
h2 Contact1.27:13.0:1
#000000
#031B4E
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.

A+
Alt Text Quality
All 43 images OK
PASS
All 43 images OK
Info::
5 decorative image(s) correctly marked
Info::
38 image(s) with good alt text
43 images 38 good alt text 5 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
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 28 passed
PASS
90

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Zoltan Bettenbuk CTO, ScraperAPI The cost of running ScraperAPI would be 250%… div#customers-growing-with-digitalocean > div.Sectionstyles__StyledSectionInner-sc-4l5hhw-1 > div.pages__StyledCustomerMarqueeContainer-sc-a481e4cd-3 > div.pages__StyledCustomerCardsContainer-sc-a481e4cd-2

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.Gridstyles-sc-isu2n3-0 > div.CarouselVideostyles__StyledCarouselNavWrapper-sc-1aj5b52-1 > div.CarouselVideostyles__StyledCarouselNav-sc-1aj5b52-2 > button.ButtonCirclestyles-sc-17yid1o-0 div.Gridstyles-sc-isu2n3-0 > div.CarouselVideostyles__StyledCarouselNavWrapper-sc-1aj5b52-1 > div.CarouselVideostyles__StyledCarouselNav-sc-1aj5b52-2 > button.ButtonCirclestyles-sc-17yid1o-0
div.Gridstyles-sc-isu2n3-0 > div.CarouselVideostyles__StyledCarouselNavWrapper-sc-1aj5b52-1 > div.CarouselVideostyles__StyledCarouselNav-sc-1aj5b52-2 > button.ButtonCirclestyles-sc-17yid1o-0 div.Gridstyles-sc-isu2n3-0 > div.CarouselVideostyles__StyledCarouselNavWrapper-sc-1aj5b52-1 > div.CarouselVideostyles__StyledCarouselNav-sc-1aj5b52-2 > button.ButtonCirclestyles-sc-17yid1o-0

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○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
●`[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 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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 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
○`<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>`.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback