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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗
Icons 2 icon(s)
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::
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 1 <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.
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

B
Favicon & Branding
5 icon(s) detected
REVIEW
5 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
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 One platform to build, scale, and unify …
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
32px · bottom of viewport
h2 The next generation of search
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Easy to integrate
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nothing good is built alone
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Join the community
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Search
2.73:1
#000000
on
#7D2E9A
needs 3.0:1 (large text)
19px · above the fold
h3 Discover
1.61:1
#000000
on
#3B1581
needs 3.0:1 (large text)
19px · mid-page
h3 Ask
1.30:1
#000000
on
#2B0561
needs 3.0:1 (large text)
19px · mid-page
h3 Cloud
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Product updates
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
19px · bottom of viewport
h3 By stage
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
19px · bottom of viewport
h3 By business model
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
19px · bottom of viewport
h3 By use case
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Customers
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Learn more
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Resources
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Integrations
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Lightning fast
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Plug-n-play
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ultra relevant
1.23:1
#000000
on
#260158
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 One platform to buil…1.23:13.0:1
#000000
#260158
Fail
h2 The next generation …1.23:13.0:1
#000000
#260158
Fail
h2 Easy to integrate1.23:13.0:1
#000000
#260158
Fail
h2 Nothing good is buil…1.23:13.0:1
#000000
#260158
Fail
h2 Join the community1.23:13.0:1
#000000
#260158
Fail
h3 Search2.73:13.0:1
#000000
#7D2E9A
Fail
h3 Discover1.61:13.0:1
#000000
#3B1581
Fail
h3 Ask1.30:13.0:1
#000000
#2B0561
Fail
h3 Cloud1.23:13.0:1
#000000
#260158
Fail
h3 Product updates1.23:13.0:1
#000000
#260158
Fail
h3 By stage1.23:13.0:1
#000000
#260158
Fail
h3 By business model1.23:13.0:1
#000000
#260158
Fail
h3 By use case1.23:13.0:1
#000000
#260158
Fail
h3 Customers1.23:13.0:1
#000000
#260158
Fail
h3 Learn more1.23:13.0:1
#000000
#260158
Fail
h3 Resources1.23:13.0:1
#000000
#260158
Fail
h3 Integrations1.23:13.0:1
#000000
#260158
Fail
h3 Lightning fast1.23:13.0:1
#000000
#260158
Fail
h3 Plug-n-play1.23:13.0:1
#000000
#260158
Fail
h3 Ultra relevant1.23:13.0:1
#000000
#260158
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.

B
Lighthouse Accessibility Audits
Score 83/100 — 5 failing, 23 passed
REVIEW
83

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.

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
header.sticky > div.mx-auto > div.ml-auto > button.ml-2 header.sticky > div.mx-auto > div.ml-auto > button.ml-2

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.

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
Accept All div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn

These are opportunities to improve the legibility of your content.

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
Full-text search Leverage reliable and performant search with features like ge… div.animation-showing-rest-of-the-page > section#38 > div.mx-auto > ul.grid
Full-text search Leverage reliable and performant search with features like ge… section#38 > div.mx-auto > ul.grid > ul.transition-200

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

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Apps div.lg:max-w-[385px] > div > div.mx-auto > button.flex
ecomm div.lg:max-w-[385px] > div > div.mx-auto > button.flex
Media div.lg:max-w-[385px] > div > div.mx-auto > button.flex
Enterprise div.lg:max-w-[385px] > div > div.mx-auto > button.flex
○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
●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
●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
●Links are distinguishable without relying on color.
●Links have a discernible name
●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
○`[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
○`<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
○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.
○Identical links have the same purpose.
○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
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
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 "Main" MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
43 headings
PASS
43 headings
Info::
Single H1 present
  • H3 Search
  • H3 Discover
  • H3 Ask
  • H3 Cloud
  • H3 Product updates
  • H3 By stage
  • H3 By business model
  • H3 By use case
  • H3 Customers
  • H3 Learn more
  • H3 Resources
  • H3 Integrations
  • H1 One platform to build, scale, and unify search and AI retrieval
  • H2 The next generation of search
  • H3 Lightning fast
  • H3 Plug-n-play
  • H3 Ultra relevant
  • H3 Apps & sites
  • H3 Full-text search
  • H3 Semantic search
  • H3 Hybrid search
  • H3 Multi-modal search
  • H3 Filtering, faceting and sorting
  • H3 Vector storage
  • H3 Federated search
  • H3 Search analytics
  • H3 Geosearch
  • H3 Don't take our word for it
  • H4 CarbonGraph consolidated its search by migrating to Meilisearch from Pinecone
  • H4 Scaling to billions: How Agora elevates e-commerce search with Meilisearch AI
  • H4 Meilisearch is a partner of choice for OCTO Technology
  • H4 Qogita simplifies B2B trade with Meilisearch Cloud
  • H4 HitPay streamlines customers’ search capabilities
  • H2 Easy to integrate
  • H2 Nothing good is built alone
  • H3 0
  • H3 0
  • H3 0
  • H3 0
  • H2 Join the community
  • H3 GitHub
  • H3 Discord
  • H3 Roadmap
A
Alt Text Quality
5 of 120 images have issues
PASS
5 of 120 images have issues
Warning::
5 image(s) with generic alt text
Info::
1 decorative image(s) correctly marked
Info::
114 image(s) with good alt text
120 images 114 good alt text 1 decorative 5 generic
IssueCount
generic5 image(s)
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputsearchnone
emailemail(Enter your email)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="email" name="email">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback