Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

19 PASS 2 REVIEW 3 FIX

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: #00a9e5

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.

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 ✗

Tap Target Adequacy

Action

6 tap target(s) too small or too close together

REVIEW

6 tap target(s) too small or too close together

6 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Elastic logo ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

No <nav> landmark found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

25 headings

PASS

25 headings

Single H1 present

H1 Better retrieval. Better answers.
H2 Elastic 9.4 is now generally available!
H2 Prometheus, minus the complexity — and 30x faster
H2 Cross-project search: Query isolated projects in-place
H2 Elastic Cloud Hosted is now FedRAMP® High Authorized
H2 Elastic Workflows: Native automation, no SOAR required
H2 Elastic Security XDR: #1 rated, zero endpoint fees
H2 Trusted by 50% of the Fortune 500 to drive innovation
H2 The Elasticsearch Platform
H2 Search
H2 Security
H2 Observability
H2 Agentic AI
H3 Want results like these?Try Elastic.
H4 Launch and scale faster with Elastic
H2 Get started now
H2 Three paths. Zero friction.
H2 Option #1
H3 Try locally
H2 Option #2
H3 Free cloud trial
H2 Option #3
H3 Talk to an expert
H3 Discover everything you can do with Elastic
H3 Ready to put your data to work?

A+

Heading Text Quality

All 25 heading(s) have substantive, well-formed text

PASS

All 25 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 26 images OK

PASS

All 26 images OK

6 decorative image(s) correctly marked

20 image(s) with good alt text

26 images 20 good alt text 6 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

1 issue(s) across 99 links and 6 buttons

PASS

1 issue(s) across 99 links and 6 buttons

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.Hamburger_hamburger__pTXMy (#280 on page)

99 link(s) with descriptive text

99 links

0 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/whats-new	Elastic 9.4 is now generally a…	img no alt	Add alt attribute to the image
/blog/cross-project-search-serverless-te…	Cross-project search: Query is…	img no alt	Add alt attribute to the image
/blog/elastic-cloud-hosted-fedramp-high-…	Elastic Cloud Hosted is now Fe…	img no alt	Add alt attribute to the image
<button>	(empty)	empty	Add button text or aria-label

104 links and buttons have descriptive text

Icon-only buttons need an aria-label so screen readers can announce them.

button.Hamburger_hamburger__pTXMy (#280 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

A+

Iframe Accessibility

All 5 iframe(s) have descriptive titles

PASS

All 5 iframe(s) have descriptive titles

All 5 iframe(s) have title attributes

A+

Mobile-Readable Font Sizes

All 134 visible text node(s) render at >= 12 CSS pixels

PASS

All 134 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

Favicon & Branding

7 icon(s) detected

PASS

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Elastic.co

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Elastic.co ✓192×192 icon ✓512×512 icon ✓Start URL /?source=pwa ✓Display Mode standalone ✓

Name Elastic.co Display Mode standalone Theme Color #00a9e5 Background Color #000 Icons 3 icon(s)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

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 Better retrieval. Be…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Elastic 9.4 is now g…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Prometheus, minus th…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Cross-project search…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Elastic Cloud Hosted…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 High Authorized	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Elastic Workflows: N…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Elastic Security XDR…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Trusted by 50% of th…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The Elasticsearch Pl…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Search	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Security	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Observability	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Agentic AI	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Get started now	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Three paths.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Option #1	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Option #2	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Option #3	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Want results like th…	21.00:1	3.0:1	#000000	#FFFFFF	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.

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 30 passed

PASS

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.Container_container__CBaVM > div.Navigation_navigation-actions__0Xm94 > div.SearchInput_search-input__yoymL > button.SearchInput_search-input-button__Yg0h2 `div.Container_container__CBaVM > div.Navigation_navigation-actions__0Xm94 > div.SearchInput_search-input__yoymL > button.SearchInput_search-input-button__Yg0h2`
div.Container_container__CBaVM > div.Navigation_navigation-actions__0Xm94 > div > button.Hamburger_hamburger__pTXMy `div.Container_container__CBaVM > div.Navigation_navigation-actions__0Xm94 > div > button.Hamburger_hamburger__pTXMy`

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.

Best practices

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 slide 1 `div.Carousel_carousel__agjUp > div.Carousel_carousel-controls__qHG1F > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `div.Carousel_carousel__agjUp > div.Carousel_carousel-controls__qHG1F > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `div.Carousel_carousel__agjUp > div.Carousel_carousel-controls__qHG1F > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 4 `div.Carousel_carousel__agjUp > div.Carousel_carousel-controls__qHG1F > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 5 `div.Carousel_carousel__agjUp > div.Carousel_carousel-controls__qHG1F > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 6 `div.Carousel_carousel__agjUp > div.Carousel_carousel-controls__qHG1F > div.swiper-pagination > span.swiper-pagination-bullet`

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

●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

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

●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

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

●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

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

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

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