Skip to content
https://www.turso.tech

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Info::
favicon.ico present at site root
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'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
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
No navigation patterns
FIX
No navigation patterns
Info::
1 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 1 <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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 "Global" MAIN (missing!) 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

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
Heading Hierarchy
34 headings
REVIEW
34 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Databases Everywhere
  • H2 Why Agents Need a New Database
  • H3 Turso
  • H4 Vector Search
  • H4 Async Design
  • H4 Concurrent Writes
  • H4 Browser + Persistence
  • H4 SQLite Compatible
  • H4 Open Contribution
  • H3 Turso Cloud
  • H4 Vector Search
  • H4 Replication & Sync
  • H4 Branching
  • H4 Analytics
  • H4 Team Access
  • H4 Fully Managed
  • H2 Don't just take our word for it
  • H2 Turso is the Database for Modern Applications
  • H3 AI Agents
  • H3 Mobile & IoT
  • H3 Private by Design
  • H3 Turso SDKs
  • H3 Cloud SDKs
  • H2 Join the Community
  • H3 Contribute
  • H4 Contribute Code
  • H4 Report Issues
  • H4 Documentation
  • H4 Show Support
  • H3 Discord
  • H4 Community Support
  • H4 Share Ideas
  • H4 Show Your Work
  • H4 Stay Updated

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
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: This page could not be found. ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA
h2 Databases Everywhere
1.76:1
#000000
on
#283945
needs 3.0:1 (large text)
24px · mid-page
h2 Why Agents Need a New Database
1.76:1
#000000
on
#283945
needs 3.0:1 (large text)
24px · mid-page
h2 Don't just take our word for it
1.76:1
#000000
on
#283945
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Turso is the Database for Modern Applica…
1.76:1
#000000
on
#283945
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Join the Community
1.76:1
#000000
on
#283945
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Turso
1.76:1
#000000
on
#283945
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Turso Cloud
1.76:1
#000000
on
#283945
needs 3.0:1 (large text)
19px · bottom of viewport
h3 AI Agents
1.76:1
#000000
on
#283945
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Mobile & IoT
1.76:1
#000000
on
#283945
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Private by Design
1.76:1
#000000
on
#283945
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Turso SDKs
1.76:1
#000000
on
#283945
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cloud SDKs
1.76:1
#000000
on
#283945
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Contribute
1.76:1
#000000
on
#283945
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Discord
1.76:1
#000000
on
#283945
needs 3.0:1 (large text)
19px · bottom of viewport
a Read the announcement
1.76:1
#000000
on
#283945
needs 4.5:1 (normal text)
16px · top of page (header area)
span Turso
1.76:1
#000000
on
#283945
needs 4.5:1 (normal text)
16px · top of page (header area)
button Get Started
1.76:1
#000000
on
#283945
needs 4.5:1 (normal text)
16px · above the fold
span Open main menu
1.76:1
#000000
on
#283945
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Databases Everywhere1.76:13.0:1
#000000
#283945
Fail
h2 Why Agents Need a Ne…1.76:13.0:1
#000000
#283945
Fail
h2 Don't just take our …1.76:13.0:1
#000000
#283945
Fail
h2 Turso is the Databas…1.76:13.0:1
#000000
#283945
Fail
h2 Join the Community1.76:13.0:1
#000000
#283945
Fail
h3 Turso1.76:13.0:1
#000000
#283945
Fail
h3 Turso Cloud1.76:13.0:1
#000000
#283945
Fail
h3 AI Agents1.76:13.0:1
#000000
#283945
Fail
h3 Mobile & IoT1.76:13.0:1
#000000
#283945
Fail
h3 Private by Design1.76:13.0:1
#000000
#283945
Fail
h3 Turso SDKs1.76:13.0:1
#000000
#283945
Fail
h3 Cloud SDKs1.76:13.0:1
#000000
#283945
Fail
h3 Contribute1.76:13.0:1
#000000
#283945
Fail
h3 Discord1.76:13.0:1
#000000
#283945
Fail
title Turso - Databases Ev…15.69:14.5:1
#000000
#4FF8D2
Pass
p Turso now supports c…15.69:14.5:1
#000000
#4FF8D2
Pass
a Read the announcemen…1.76:14.5:1
#000000
#283945
Fail
span Turso1.76:14.5:1
#000000
#283945
Fail
button Get Started1.76:14.5:1
#000000
#283945
Fail
span Open main menu1.76:14.5:1
#000000
#283945
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 6 images OK
PASS
All 6 images OK
Info::
6 image(s) with good alt text
6 images 6 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 95/100 — 2 failing, 25 passed
PASS
95

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
BETA div.rounded-2xl > div.p-6 > div.inline-flex > span.rounded-full
BETA div.grid > div > div.p-6 > span.rounded-full
Read Manual div.grid > div > div.p-6 > a.rounded-full
OPEN SOURCE div.grid > div.rounded-2xl > div.p-6 > span.rounded-full
Fork Repository div.grid > div.rounded-2xl > div.p-6 > a.rounded-full

These are opportunities to improve the legibility of your content.

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.__variable_f367f3 html.__variable_f367f3

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
●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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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 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
○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.
○No element has a `[tabindex]` value greater than 0
○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.
○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