Skip to content
https://supabase.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
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::
2 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 2 <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
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
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.
Info::
No banner (header) landmark
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 (missing!) NAV 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 Supabase | The Postgres Development Platform. ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
24 icon(s) detected
REVIEW
24 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 Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Supabase
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Supabase ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓
Name Supabase Display Mode standalone Theme Color #1C1C1C Background Color #1C1C1C Icons 6 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 #1e1e1e ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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
h2 Postgres Database
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · mid-page
h2 Authentication
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Edge Functions
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Storage
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Realtime
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Vector
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Data APIs
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Open source from day one
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Footer
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Start building in seconds
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 without leaving the dashboard
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Join the community
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
title Supabase | The Postgres Development Plat…
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · top of page (header area)
button Product
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · top of page (header area)
button Developers
1.12:1
#000000
on
#121212
needs 4.5:1 (normal text)
16px · top of page (header area)
button Solutions
1.12:1
#000000
on
#121212
needs 4.5:1 (normal text)
16px · top of page (header area)
p Pricing
1.12:1
#000000
on
#121212
needs 4.5:1 (normal text)
16px · above the fold
p Docs
1.12:1
#000000
on
#121212
needs 4.5:1 (normal text)
16px · above the fold
p Blog
1.12:1
#000000
on
#121212
needs 4.5:1 (normal text)
16px · above the fold
span 100.1K
1.12:1
#000000
on
#121212
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Postgres Database1.12:13.0:1
#000000
#121212
Fail
h2 Authentication1.66:13.0:1
#000000
#333333
Fail
h2 Edge Functions1.66:13.0:1
#000000
#333333
Fail
h2 Storage1.66:13.0:1
#000000
#333333
Fail
h2 Realtime1.66:13.0:1
#000000
#333333
Fail
h2 Vector1.66:13.0:1
#000000
#333333
Fail
h2 Data APIs1.66:13.0:1
#000000
#333333
Fail
h2 Open source from day…1.66:13.0:1
#000000
#333333
Fail
h2 Footer1.66:13.0:1
#000000
#333333
Fail
h3 Start building in se…1.66:13.0:1
#000000
#333333
Fail
h3 without leaving the …1.66:13.0:1
#000000
#333333
Fail
h3 Join the community1.66:13.0:1
#000000
#333333
Fail
title Supabase | The Postg…1.11:14.5:1
#000000
#111111
Fail
button Product1.11:14.5:1
#000000
#111111
Fail
button Developers1.12:14.5:1
#000000
#121212
Fail
button Solutions1.12:14.5:1
#000000
#121212
Fail
p Pricing1.12:14.5:1
#000000
#121212
Fail
p Docs1.12:14.5:1
#000000
#121212
Fail
p Blog1.12:14.5:1
#000000
#121212
Fail
span 100.1K1.12:14.5:1
#000000
#121212
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
Heading Hierarchy
33 headings, 1 skip(s)
PASS
33 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Build in a weekendScale to millions
  • H2 Postgres Database
  • H2 Authentication
  • H2 Edge Functions
  • H2 Storage
  • H2 Realtime
  • H2 Vector
  • H2 Data APIs
  • H3 Trusted by the world’s most innovative companies.
  • H3 Start building in seconds
  • H4 Stripe Subscriptions Starter
  • H4 Next.js Starter
  • H4 AI Chatbot
  • H4 LangChain + Next.js Starter
  • H4 Flutter User Management
  • H4 Expo React Native Starter
  • H4 Stripe Subscriptions Starter
  • H4 Next.js Starter
  • H4 AI Chatbot
  • H4 LangChain + Next.js Starter
  • H4 Flutter User Management
  • H4 Expo React Native Starter
  • H3 Stay productive and manage your app without leaving the dashboard
  • H3 Join the community
  • H2 Open source from day one
  • H2 Build in a weekend, scale to millions
  • H2 Footer
  • H6 Product skipped
  • H6 Solutions
  • H6 Resources
  • H6 Developers
  • H6 Community
  • H6 Company

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 158 images OK
PASS
All 158 images OK
Info::
2 decorative image(s) correctly marked
Info::
156 image(s) with good alt text
158 images 156 good alt text 2 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputemailEmail for newsletteraria-label
A
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 26 passed
PASS
92

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.

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
Product div.mt-12 > div.grid > div > h6.text-foreground

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#frameworks > div.relative > div.grid > a.transition-opacity div#frameworks > div.relative > div.grid > a.transition-opacity
div#frameworks > div.relative > div.grid > a.transition-opacity div#frameworks > div.relative > div.grid > a.transition-opacity
div#frameworks > div.relative > div.grid > a.transition-opacity div#frameworks > div.relative > div.grid > a.transition-opacity
div#frameworks > div.relative > div.grid > a.transition-opacity div#frameworks > div.relative > div.grid > a.transition-opacity
div#frameworks > div.relative > div.grid > a.transition-opacity div#frameworks > div.relative > div.grid > a.transition-opacity
div#frameworks > div.relative > div.grid > a.transition-opacity div#frameworks > div.relative > div.grid > a.transition-opacity
div#frameworks > div.relative > div.grid > a.transition-opacity div#frameworks > div.relative > div.grid > a.transition-opacity
div#frameworks > div.relative > div.grid > a.transition-opacity div#frameworks > div.relative > div.grid > a.transition-opacity
div#frameworks > div.relative > div.grid > a.transition-opacity div#frameworks > div.relative > div.grid > a.transition-opacity
div#frameworks > div.relative > div.grid > a.transition-opacity div#frameworks > div.relative > div.grid > a.transition-opacity

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
We use cookies to collect data and improve our services. Learn more • Privacy … body > div#__next > section > ol.toaster

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
●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
●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
●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
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
○`[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 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.
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback