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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title Page not found - Brevo ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
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.
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 22 passed
REVIEW
85

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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Scroll left div.dist_marketing-container__H_Hue > section > section.dist_marketing-interactive-slider__container__aHdpr > button.marketing-typo_text-inter-2-medium

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Small Business div.dist_marketing-input-box__XlG9m > div.dist_marketing-input-dropdown__XaMql > div.dist_marketing-dropdown-root__9vHIg > div.dist_marketing-dropdown-control__pGdxd

These are opportunities to improve the usage of ARIA in your application which 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
Sales Assistant div.dist_marketing-media-text-slider__slide___fLn7 > div.dist_marketing-media-text-slider__slide-wrapper__n3Sjp > div.dist_marketing-media-text-slider__slide__heading__PrGuU > h3.marketing-heading-6
Instantly enrich contacts and accounts, automate deal creation, and send sales … div.dist_marketing-media-text-slider__slides__a4_je > div.dist_marketing-media-text-slider__slide___fLn7 > div.dist_marketing-media-text-slider__slide-wrapper__n3Sjp > span.marketing-typo_text-inter-3-regular
Discover Aura AI div.dist_marketing-media-text-slider__slide___fLn7 > div.dist_marketing-media-text-slider__slide-wrapper__n3Sjp > a.marketing-typo_text-inter-2-medium > span.dist_marketing-btn-label__Qr6VO

These are opportunities to improve the legibility of your content.

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
Clear selection div.dist_marketing-input-dropdown__XaMql > div.dist_marketing-dropdown-root__9vHIg > div.dist_marketing-dropdown-control__pGdxd > button.dist_marketing-dropdown-input__cross__unQAp

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
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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
○`<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
○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.
○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
10 landmarks
PASS
10 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 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
31 headings
PASS
31 headings
Info::
Single H1 present
  • H1 Turn Every EmailSMSOrderInteractioninto a Lifetime Customer
  • H2 Join 600,000+ customers around the world who trust Brevo
  • H3 Grow your business easily
  • H3 Built to scale with you
  • H3 Accelerate with AI
  • H2 Engage your audience your way
  • H3 Email marketing
  • H3 SMS marketing
  • H3 WhatsApp campaigns
  • H3 Push notifications
  • H3 Loyalty
  • H3 Mobile Wallet
  • H3 Transactional messaging
  • H3 VoIP Phone
  • H3 Live chat
  • H3 Chatbot
  • H3 Meetings
  • H2 AI agents that work with you, and for you
  • H3 Marketing Agent
  • H3 Sales Assistant
  • H3 Data Analyst
  • H3 Conversations Agent
  • H2 Built for every business — from the first send to enterprise
  • H3 Powerful tools, simple setup
  • H2 Recognized as an industry leader
  • H2 Real stories, real success
  • H3 Adbloom grows revenue by $1M/year
  • H3 Buffalo Grill achieves 47% repeat restaurant visits
  • H3 Suntransfers drives 40% revenue growth with Brevo
  • H2 Brevo connects to the tools you already use
  • H2 Ready to grow with Brevo?
A+
Alt Text Quality
1 of 100 images have issues
PASS
1 of 100 images have issues
Warning::
1 image(s) with generic alt text
Info::
18 decorative image(s) correctly marked
Info::
81 image(s) with good alt text
100 images 81 good alt text 18 decorative 1 generic
IssueCount
generic1 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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)
ElementRatioRequiredFGBGResult
h2 Join 600,000+ custom…18.09:13.0:1
#000000
#C0FFA5
Pass
h2 Engage your audience…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 AI agents that work …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Built for every busi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Recognized as an ind…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Real stories, real s…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Brevo connects to th…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ready to grow with B…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Grow your business e…18.09:13.0:1
#000000
#C0FFA5
Pass
h3 Built to scale with …18.09:13.0:1
#000000
#C0FFA5
Pass
h3 Accelerate with AI18.09:13.0:1
#000000
#C0FFA5
Pass
h3 Email marketing21.00:13.0:1
#000000
#FFFFFF
Pass
h3 SMS marketing21.00:13.0:1
#000000
#FFFFFF
Pass
h3 WhatsApp campaigns21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Push notifications21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Loyalty21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Mobile Wallet21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Transactional messag…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 VoIP Phone21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Live chat21.00:13.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.

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

Send Feedback