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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
2
REVIEW
7
PASS
4
INFO
0
Checks
13
4 PASS 7 REVIEW 2 FIX
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::
3 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 3 <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
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
2 of 3 <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" 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

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::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Page not found - PlanetScale ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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 Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: PlanetScale
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name PlanetScale ✓192×192 icon ✓512×512 icon ✓Start URL https://planetscale.com ✓Display Mode ✗
Name PlanetScale Background Color #111111 Icons 2 icon(s)
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #111111 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA
title PlanetScale - the world’s fastest and …
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · top of page (header area)
span Introducing Database Traffic Control™:…
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · top of page (header area)
a Learn more
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · top of page (header area)
a Log in
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The world’s fastes…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Company20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Product20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Resources20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Courses20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Open source20.12:13.0:1
#000000
#FAFAFA
Pass
title PlanetScale - the wo…1.11:14.5:1
#000000
#111111
Fail
span Introducing Database…1.11:14.5:1
#000000
#111111
Fail
a Learn more1.11:14.5:1
#000000
#111111
Fail
a Log in1.11:14.5:1
#000000
#111111
Fail
a Get started20.12:14.5:1
#000000
#FAFAFA
Pass
a Get in touch20.12:14.5:1
#000000
#FAFAFA
Pass
button Platform20.12:14.5:1
#000000
#FAFAFA
Pass
span ▾20.12:14.5:1
#000000
#FAFAFA
Pass
button Resources20.12:14.5:1
#000000
#FAFAFA
Pass
span ▾20.12:14.5:1
#000000
#FAFAFA
Pass
a Documentation20.12:14.5:1
#000000
#FAFAFA
Pass
a Pricing20.12:14.5:1
#000000
#FAFAFA
Pass
a Contact20.12:14.5:1
#000000
#FAFAFA
Pass
summary Navigation20.12:14.5:1
#000000
#FAFAFA
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+
Heading Hierarchy
11 headings
PASS
11 headings
Info::
Single H1 present
  • H1 The world’s fastest and most scalable cloud databases
  • H2 Performance
  • H2 Uptime
  • H2 Cost
  • H2 Security
  • H2 Features
  • H2 Company
  • H2 Product
  • H2 Resources
  • H2 Courses
  • H2 Open source
A+
Alt Text Quality
All 1 images OK
PASS
All 1 images OK
Info::
1 image(s) with good alt text
1 images 1 good alt text
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 93/100 — 2 failing, 26 passed
PASS
93

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
Get in touch div.grid > div.group > div.flex > a.btn

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
fastest databases div.flex > div > p > a
NVMe drives div.flex > div > p > a
deployment options div.flex > div > p > a
PlanetScale Managed div.flex > div > p > a
Tier 0 databases div.flex > div > p > a
Vitess div.border > div#headlessui-tabs-panel-:R3a355: > p > a
scale horizontally through explicit sharding div.border > div#headlessui-tabs-panel-:R3a355: > p > a
PlanetScale Metal div.mt-3 > div > p > a
Benchmarking page div > figure > figcaption > a
SLA commitment div.mt-3 > div > p > a
status page div.mt-3 > div > p > a
reach out to us div.mt-3 > div > p > a
PlanetScale Managed div > ul.my-0 > li > a
realize additional savings div > ul.my-0 > li > a
security documentation div.mt-3 > div > p > a
Trust Center div.mt-3 > div > p > a
and more div.mt-3 > div > p > a
vector data div > ul.my-0 > li > a
Roll back div > ul.my-0 > li > a
with Insights div > ul.my-0 > li > a
explicit sharding workflows div > ul.my-0 > li > a
and more div > ul.my-0 > li > a
best-in-class support div > ul.my-0 > li > a

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]`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.
●ARIA attributes are used as specified for the element's role
●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 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.
●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.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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.
○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.
○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