Browse & Analyze

Browse recent website audits and performance trends

Explore technology stacks detected across the web

Side-by-side technology comparisons and market share

Curated technology stacks and the sites that use them

Editorial deep-dives on the state of web performance

Browse and download favicons from analyzed websites

Learn

Common questions about BeaverCheck scores and checks

How we calculate scores across 100+ checks

The story behind BeaverCheck and the team

Practical guides to fix common web performance issues

Migration Guides

Step-by-step guides for moving between web technologies

Definitions for performance, SEO, and web platform terms

Contrast Checker

Check WCAG color contrast ratios between any two colors

Inspect HTTP response headers for any URL

Analyze SSL/TLS certificate details and chain

Look up DNS records for any domain

Redirect Checker

Trace the full redirect chain for any URL

Real-user INP and Core Web Vitals from Google's Chrome UX Report.

RESTful API for programmatic website audits

Embed an auto-updating health score badge on your site

https://www.algolia.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

37

GRADE

F

FIX

10

REVIEW

1

PASS

2

INFO

0

Checks

13

2 PASS 1 REVIEW 10 FIX

D

Landmark Structure

Action

6 landmarks

FIX

6 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

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

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

F

Heading Hierarchy

Action

69 headings, 4 skip(s)

FIX

69 headings, 4 skip(s)

Single H1 present

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

2 empty heading(s)

Empty headings appear in the document outline but provide no information.

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

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

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F

Alt Text Quality

Action

24 of 135 images have issues

FIX

24 of 135 images have issues

24 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

20 image-in-link without alt text

An image inside a link with no alt creates an empty link.

79 decorative image(s) correctly marked

32 image(s) with good alt text

135 images 32 good alt text 79 decorative 24 missing

Issue	Count
missing	24 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F

Link & Button Quality

Action

22 issue(s) across 282 links and 46 buttons

FIX

22 issue(s) across 282 links and 46 buttons

4 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: #; #; https://www.algolia.com/lp/algolia-forrester-tei-report-2026;

11 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /products/ai-search ("Learn more"); /products/ai/generative-experiences ("Learn more"); /products/ai/agent-studio ("Learn more"); http://docsearch.algolia.com ("Learn more"); /products/ai-search ("Learn more"); /products/features/neuralsearch ("Learn more"); /products/features/analytics ("Learn more"); /products/features/personalization ("Learn more"); /products/features/ai-ranking ("Learn more"); /distributed-secure/security-compliance ("Learn more") (+1 more)

28 image-only link(s) without alt text

7 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://dashboard.algolia.com/users/sign_up; https://dashboard.algolia.com/users/sign_up; https://www.algolia.com/developers; https://www.algolia.com/customers; /policies/anti-modern-slavery-statement; https://www.algolia.com/policies/cookies/; https://www.onetrust.com/products/cookie-consent/

7 button(s) with no accessible text

232 link(s) with descriptive text

282 links

4 empty

11 generic text

7 new tab

7 empty buttons

Element	Text	Issue	Suggested Fix
https://dashboard.algolia.com/users/sign…	Login	img no alt	Add alt attribute to the image
https://dashboard.algolia.com/users/sign…	Logout	img no alt	Add alt attribute to the image
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
/about	Company	img no alt	Add alt attribute to the image
https://partners.algolia.com/	Partners	img no alt	Add alt attribute to the image
https://support.algolia.com/	Support	img no alt	Add alt attribute to the image
https://dashboard.algolia.com/users/sign…	Login	img no alt	Add alt attribute to the image
https://dashboard.algolia.com/users/sign…	Logout	img no alt	Add alt attribute to the image
https://dashboard.algolia.com/users/sign…	Get started	new tab	Add '(opens in new tab)' to text
https://dashboard.algolia.com/users/sign…	Get started	new tab	Add '(opens in new tab)' to text
/products/ai-search	AI Searchproducts > ai search …	img no alt	Add alt attribute to the image
/events	Events - Webinars, conferences…	img no alt	Add alt attribute to the image
/distributed-secure/security-compliance/…	Security Measures \| Algoliadis…	img no alt	Add alt attribute to the image
/distributed-secure/security-compliance	Learn all about security & com…	img no alt	Add alt attribute to the image
/resources/asset/ebook-understanding-ai-…	Understanding Al transparencyR…	img no alt	Add alt attribute to the image
/distributed-secure/global-infrastructur…	Infrastructure for search spee…	img no alt	Add alt attribute to the image
/products/features/crawler	Web Crawlerproducts > features…	img no alt	Add alt attribute to the image
/doc/ui-libraries/autocomplete/solutions…	Creating an advanced federated…	img no alt	Add alt attribute to the image
/products/features/personalization	Personalizationproducts > feat…	img no alt	Add alt attribute to the image
/products/features/search-relevance-rule…	Rulesproducts > features > sea…	img no alt	Add alt attribute to the image
/products/features/ab-testing	A/B testingproducts > features…	img no alt	Add alt attribute to the image
/products/features/search-autocomplete	Autocompleteproducts > feature…	img no alt	Add alt attribute to the image
/industries/ecommerce	Ecommerceindustries > ecommerc…	img no alt	Add alt attribute to the image
/industries/saas	SaaSindustries > saas …	img no alt	Add alt attribute to the image
/industries/marketplaces	Marketplacesindustries > marke…	img no alt	Add alt attribute to the image
/industries/ecommerce/digital-merchandis…	Digital Merchandisingindustrie…	img no alt	Add alt attribute to the image
/industries/media	Mediaindustries > media …	img no alt	Add alt attribute to the image
/industries/b2b-ecommerce	B2B Ecommerceindustries > b2b …	img no alt	Add alt attribute to the image
/industries/startups	Startupsindustries > startups …	img no alt	Add alt attribute to the image
/use-cases/voice-search	Voice Searchuse cases > voice …	img no alt	Add alt attribute to the image
/products/ai-search	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Ai Search
/products/ai/generative-experiences	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Generative Experiences
/products/ai/agent-studio	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Agent Studio
http://docsearch.algolia.com	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Docsearch.Algolia.Com
https://www.algolia.com/lp/algolia-forre…	(empty)	empty	Add link text or aria-label
/products/ai-search	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Ai Search
	(empty)	empty	Add link text or aria-label
/products/features/neuralsearch	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Neuralsearch
/products/features/analytics	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Analytics
/products/features/personalization	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Personalization
/products/features/ai-ranking	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Ai Ranking
https://www.algolia.com/developers	View developer hub	new tab	Add '(opens in new tab)' to text
https://www.algolia.com/customers	View all customer stories	new tab	Add '(opens in new tab)' to text
/distributed-secure/security-compliance	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Security Compliance
/policies/anti-modern-slavery-statement	Anti-Modern Slavery Statement	new tab	Add '(opens in new tab)' to text
/lp/subscription-newsletter	Get the latest in AI search - …	img no alt	Add alt attribute to the image
javascript:void(0);	here	generic text	Replace with descriptive text
Before: here Suggested: Javascript:Void(0);
https://www.algolia.com/policies/cookies…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

271 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

#; #; https://www.algolia.com/lp/algolia-forrester-tei-report-2026;

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

/products/ai-search ("Learn more"); /products/ai/generative-experiences ("Learn more"); /products/ai/agent-studio ("Learn more"); http://docsearch.algolia.com ("Learn more"); /products/ai-search ("Learn more"); /products/features/neuralsearch ("Learn more"); /products/features/analytics ("Learn more"); /products/features/personalization ("Learn more"); /products/features/ai-ranking ("Learn more"); /distributed-secure/security-compliance ("Learn more") (+1 more)

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://dashboard.algolia.com/users/sign_up; https://dashboard.algolia.com/users/sign_up; https://www.algolia.com/developers; https://www.algolia.com/customers; /policies/anti-modern-slavery-statement; https://www.algolia.com/policies/cookies/; https://www.onetrust.com/products/cookie-consent/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

D

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

F

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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 Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

Web Manifest

Action

Not found

FIX

Not found

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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #003dff

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

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

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 ✗

C

Lighthouse Accessibility Audits

Action

Score 75/100 — 8 failing, 25 passed

REVIEW

75

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
div.dark > header#main-header > div.header__middle-bar > button#toggleMobileNav `div.dark > header#main-header > div.header__middle-bar > button#toggleMobileNav`
div#filter-container > div.w-4/5 > div.block > button#close-filters `div#filter-container > div.w-4/5 > div.block > button#close-filters`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#refinements-container > div#mobile-refinements > div#other-types-btn > img.inline-block `div#refinements-container > div#mobile-refinements > div#other-types-btn > img.inline-block`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`
li.ais-InfiniteHits-item > a.hit > div.block > img.w-full `li.ais-InfiniteHits-item > a.hit > div.block > img.w-full`

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.teaser > div.cmp-teaser > div.cmp-teaser__image > a `div.teaser > div.cmp-teaser > div.cmp-teaser__image > a`
div#teaser-container > div.customer_card_section > div.teaser-with-cta > a `div#teaser-container > div.customer_card_section > div.teaser-with-cta > a`

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.

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
The Total Economic Impact of Algolia `div.teaser > div.cmp-teaser > div.cmp-teaser__content > h5.cmp-teaser__title`
Quickly surface the right content `div.customer_card_section > div.teaser-with-cta > div.cmp-teaser__content > h4.text-[21px]`
BSI C5 `div.h-full > div.flex > div.flex > h4.text-[14px]`
div.footer_items > div.flex-1 > div > h4.font-inter `div.footer_items > div.flex-1 > div > h4.font-inter`

These are opportunities to improve keyboard navigation in your application.

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
Careers Contact Us About Algolia Anti-Modern Slavery Statement `div.footer_items > div.flex-1 > div > ul.m-0`
Get the latest in AI search - straight to your inbox. `div.footer_items > div.flex-none > div.mt-10 > ul.m-0`

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`
head > meta `head > meta`

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to persona 1 `div.w-full > div.relative > div.agentic-hero-dots > button.agentic-hero-dot`
Go to persona 2 `div.w-full > div.relative > div.agentic-hero-dots > button.agentic-hero-dot`
Cookie settings `div.flex > ul.m-0 > li > button#ot-sdk-btn`
Trust Center `div.flex > ul.m-0 > li > a.block`
Privacy Policy `div.flex > ul.m-0 > li > a.block`
Terms of service `div.flex > ul.m-0 > li > a.block`
Acceptable Use Policy `div.flex > ul.m-0 > li > a.block`

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
✕ Thanks for visiting! 👋 I can help answer any questions about Algolia. `body.font-inter > div#af-preopen-hook-fea6a095-e400-47fa-a726-8d6103a5c134 > div.af-preopen-hook__bubble`

○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

●Form elements have associated labels

●`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

●Background and foreground colors have a sufficient contrast ratio

●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.

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●All heading elements contain content.

●Identical links have the same purpose.

○`[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

○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

○Tables have different content in the summary attribute and `<caption>`.

○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

Form Accessibility

1 of 9 controls have issues

PASS

1 of 9 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="search" id="autocomplete-0-input">

8 control(s) properly labeled

9 controls

8 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#ot-group-id-C0004	checkbox	Targeting Cookies	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
#autocomplete-0-input	search	(Search…)	placeholder only

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

<input type="search" id="autocomplete-0-input">

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

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Agentic. Generative.…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Learn	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Use Case	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Framework	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Programming Language	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Integrations	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 AI Search	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Events - Webinars, c…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Security Measures \| …	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Learn all about secu…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Understanding Al tra…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Infrastructure for s…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Web Crawler	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Creating an advanced…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Personalization	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Rules	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 A/B testing	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Autocomplete	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Ecommerce	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 SaaS	19.43:1	3.0:1	#000000	#F6F6F6	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.

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

Send Feedback