Skip to content
https://mysql.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
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.

F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <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
7 headings
REVIEW
7 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 MySQL HeatWave
  • H2 MySQL AI
  • H2 MySQL Enterprise Edition
  • H2 MySQL for OEM/ISV
  • H2 MySQL Cluster CGE
  • H2 Free Webinars
  • H2 White Papers

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

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

18 pass 2 fail WCAG AA 6 pass AA only
h2 Free Webinars
2.59:1
#000000
on
#893428
needs 3.0:1 (large text)
24px · bottom of viewport
h2 White Papers
2.59:1
#000000
on
#893428
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Free Webinars2.59:13.0:1
#000000
#893428
Fail
h2 White Papers2.59:13.0:1
#000000
#893428
Fail
title MySQL7.37:14.5:1
#000000
#999999
Pass
a Skip to Main Content7.37:14.5:1
#000000
#999999
Pass
div The world's most pop…4.52:14.5:1
#000000
#6B767F
Pass
b Contact MySQL3.47:13.0:1
#000000
#536572
Pass
a Login7.37:14.5:1
#000000
#999999
Pass
a Register7.37:14.5:1
#000000
#999999
Pass
a MySQL.com7.37:14.5:1
#000000
#999999
Pass
a Downloads7.28:14.5:1
#000000
#989898
Pass
a Documentation7.19:14.5:1
#000000
#979797
Pass
a Developer Zone7.01:14.5:1
#000000
#959595
Pass
a Developer Zone6.75:14.5:1
#000000
#929292
Pass
a Documentation6.33:14.5:1
#000000
#8D8D8D
Pass
a Downloads5.69:14.5:1
#000000
#858585
Pass
a MySQL.com5.03:14.5:1
#000000
#7C7C7C
Pass
a Products7.37:14.5:1
#000000
#999999
Pass
a Services7.37:14.5:1
#000000
#999999
Pass
a Partners7.37:14.5:1
#000000
#999999
Pass
a Customers7.37:14.5:1
#000000
#999999
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.

B
Lighthouse Accessibility Audits
Score 80/100 — 6 failing, 27 passed
REVIEW
80

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
MySQL HeatWave div.col-1-of-2 > div.fp-product > h2 > a
MySQL AI div.col-1-of-2 > div.fp-product > h2 > a
MySQL Enterprise Edition div.col-1-of-2 > div.fp-product > h2 > a
MySQL for OEM/ISV div.col-1-of-2 > div.fp-product > h2 > a
MySQL Cluster CGE div.col-1-of-2 > div.fp-product > h2 > a
Q&A with MySQL Experts Tuesday, May 12, 2026 div.rw > div.col-1-of-2 > ul > li
MySQL Global Forum – Built on 30 Years of Innovation On-Demand div.rw > div.col-1-of-2 > ul > li
MySQL Enterprise Edition: Onboarding and Latest Innovation Highlights On-Demand div.rw > div.col-1-of-2 > ul > li
Accept all div.mainContent > div > div.pdynamicbutton > a.call
Decline all div.mainContent > div > div.pdynamicbutton > a.required
Powered by div > div.footer > div.left > label

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
More Countries » div#footer-bottom > div.footer-contact > div#footer-contact-numbers > a.darker-blue
privacy policy div.mainContent > div > div#cookieConsentDescription > a

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Menu ... Products   |- MySQL HeatWave   |- MySQL Enterprise Edition   |- MySQL … div#footer-links > div#site-footer-links > div#footer-nav > select#footer-select

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#banners > div#fp-banner4 > div#fp-banner-image4 > a.fp-banner-link div#banners > div#fp-banner4 > div#fp-banner-image4 > a.fp-banner-link
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot1 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot1
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot2 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot2
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot3 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot3
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot4 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot4
div.fp-logo-container > div#fp-logos > div > a.fp-logo-youtube div.fp-logo-container > div#fp-logos > div > a.fp-logo-youtube
div.fp-logo-container > div#fp-logos > div > a.fp-logo-paypal div.fp-logo-container > div#fp-logos > div > a.fp-logo-paypal
div.fp-logo-container > div#fp-logos > div > a.fp-logo-linkedin div.fp-logo-container > div#fp-logos > div > a.fp-logo-linkedin
div.fp-logo-container > div#fp-logos > div > a.fp-logo-facebook div.fp-logo-container > div#fp-logos > div > a.fp-logo-facebook
div.fp-logo-container > div#fp-logos > div > a.fp-logo-twitter div.fp-logo-container > div#fp-logos > div > a.fp-logo-twitter
div.fp-logo-container > div#fp-logos > div > a.fp-logo-ebay div.fp-logo-container > div#fp-logos > div > a.fp-logo-ebay
div.fp-logo-container > div#fp-logos > div > a.fp-logo-cisco div.fp-logo-container > div#fp-logos > div > a.fp-logo-cisco
div.fp-logo-container > div#fp-logos > div > a.fp-logo-verizon div.fp-logo-container > div#fp-logos > div > a.fp-logo-verizon
div.fp-logo-container > div#fp-logos > div > a.fp-logo-uber div.fp-logo-container > div#fp-logos > div > a.fp-logo-uber
div.fp-logo-container > div#fp-logos > div > a.fp-logo-shopify div.fp-logo-container > div#fp-logos > div > a.fp-logo-shopify
div.fp-logo-container > div#fp-logos > div > a.fp-logo-netflix div.fp-logo-container > div#fp-logos > div > a.fp-logo-netflix
div.fp-logo-container > div#fp-logos > div > a.fp-logo-github div.fp-logo-container > div#fp-logos > div > a.fp-logo-github
div.fp-logo-container > div#fp-logos > div > a.fp-logo-walmart div.fp-logo-container > div#fp-logos > div > a.fp-logo-walmart
div.fp-logo-container > div#fp-logos > div > a.fp-logo-booking div.fp-logo-container > div#fp-logos > div > a.fp-logo-booking
div.fp-logo-container > div#fp-logos > div > a.fp-logo-zappos div.fp-logo-container > div#fp-logos > div > a.fp-logo-zappos
div.fp-logo-container > div#fp-logos > div > a.fp-logo-bankamer div.fp-logo-container > div#fp-logos > div > a.fp-logo-bankamer
div.fp-logo-container > div#fp-logos > div > a.fp-logo-flipkart div.fp-logo-container > div#fp-logos > div > a.fp-logo-flipkart
div.fp-logo-container > div#fp-logos > div > a.fp-logo-paytm div.fp-logo-container > div#fp-logos > div > a.fp-logo-paytm
div.fp-logo-container > div#fp-logos > div > a.fp-logo-alibaba div.fp-logo-container > div#fp-logos > div > a.fp-logo-alibaba
div.fp-logo-container > div#fp-logos > div > a.fp-logo-wechat div.fp-logo-container > div#fp-logos > div > a.fp-logo-wechat
div.fp-logo-container > div#fp-logos > div > a.fp-logo-tencent div.fp-logo-container > div#fp-logos > div > a.fp-logo-tencent
div.fp-logo-container > div#fp-logos > div > a.fp-logo-taobao div.fp-logo-container > div#fp-logos > div > a.fp-logo-taobao
div.fp-logo-container > div#fp-logos > div > a.fp-logo-airbnb div.fp-logo-container > div#fp-logos > div > a.fp-logo-airbnb
div.fp-logo-container > div#fp-logos > div > a.fp-logo-toyota div.fp-logo-container > div#fp-logos > div > a.fp-logo-toyota

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
Start chat body.no-sidebar > div.ochat_slideout > ul.ochat_slidew2

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

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.no-sidebar > div#pop-div2014185780280426152 > div#pop-div3024974372408668077 > div#pop-frame0034404405713043484 body.no-sidebar > div#pop-div2014185780280426152 > div#pop-div3024974372408668077 > div#pop-frame0034404405713043484

These are opportunities to improve keyboard navigation in your application.

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.
`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
`<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
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Skip links are focusable.
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
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
Buttons have an accessible name
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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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.
`<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
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Contact/Login Navigation" MAIN ASIDE "Open Cookie Preferences Modal" CONTENTINFO footer
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
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="footer-select">
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#l1-search-inputsearchSearcharia-label
#l1-search-inputsearchSearcharia-label
#footer-selectselect(none)none

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

<select id="footer-select">

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
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title MySQL :: Page Not Found Custom Styling Navigation Homepage Link Search Form
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: https://labs.mysql.com/common/css/print-20250803.min.css
Print Stylesheet Print Optimized
Print stylesheet https://labs.mysql.com/common/css/print-20250803.min.css Inline @media print Not detected
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback