Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.F404 Error PageActionHTTP 404, bare pageFIX
FFavicon & BrandingAction2 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BHeading Hierarchy24 headings, 1 skip(s)REVIEW
- H1 Rewrite the rules of customer engagement with AI
- H2 MADE TO SCALE WITH COMPANIES OF ALL SIZES
- H2 When technology moves fast, marketers move faster
- H4 Braze Data Platform skipped
- H3 Bring your data together, then put it to work
- H4 BrazeAI™
- H3 Add BrazeAI™ to your dream team
- H3 Put AI decisioning behind every move
- H4 Cross-channel
- H3 Make every interaction feel human
- H2 The only customer engagement platform you’ll ever need
- H2 Understand your audience with Segment Builder
- H2 Understand your audience with Segment Builder
- H2 Your brand has a message, how you deliver it matters.
- H2 See our industry and customer recognitions.
- H1 Forrester duplicate H1
- H2 Check out the resources.
- H3 From efficiency to effectiveness: How AI is transforming customer engagement
- H3 AI-Powered Customer Engagement: A Braze Playbook
- H3 Braze Inspiration Guide
- H3 2026 Global Customer Engagement Review
- H3 Know your customer: Enhancing relevance with AI-powered experimentation
- H3 How to Build an AI Marketing Strategy
- H2 It’s time to be a better marketer
A page should have only one H1. Multiple H1s dilute the document outline.
Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.
Learn more ▾ ▴
HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.
Source: WCAG 2.4.6 / Google Search Central
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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
CLink & Button QualityAction4 issue(s) across 156 links and 34 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| /product | Learn More | generic text | Replace with descriptive text |
Before: Learn More Suggested: Product | |||
| /customers/pizza-hut-case-study | "We’ve been really impressed… | img no alt | Add alt attribute to the image |
| /customers/bees-case-study | With Braze, we’ve been able … | img no alt | Add alt attribute to the image |
| /customers/virgin-red-case-study | We brought in Braze to level u… | img no alt | Add alt attribute to the image |
| /customers/hugosave-case-study | Braze is a very important part… | img no alt | Add alt attribute to the image |
| /resources/webinars-and-events/relevance… | WebinarKnow your customer: Enh… | img no alt | Add alt attribute to the image |
| <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 |
Generic link text like 'click here' doesn't describe the destination.
/product ("Learn More")
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
Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.
a[href="/customers/pizza-hut-case-study"]; a[href="/customers/bees-case-study"]; a[href="/customers/virgin-red-case-study"]; a[href="/customers/hugosave-case-study"]; a[href="/resources/webinars-and-events/relevance-ai-experimentation"]
Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.
Source: WCAG 2.1 SC 2.4.4
Icon-only buttons need an aria-label so screen readers can announce them.
button.bg-play-button (#758 on page); button.flex (#1120 on page); button.flex (#1123 on page)
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
CColor Contrast (Screenshot)Action20 text elements analyzed, 18 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
1 contrast failures on background images/gradients
These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Forrester | 2.26:1 | 3.0:1 | #000000 | #793110 | Fail |
| h2 MADE TO SCALE WITH C… | 2.26:1 | 3.0:1 | #000000 | #793110 | Fail |
| h2 Understand your audi… | 2.26:1 | 3.0:1 | #000000 | #793110 | Fail |
| h2 Understand your audi… | 2.26:1 | 3.0:1 | #000000 | #793110 | Fail |
| h3 Put AI decisioning b… | 2.26:1 | 3.0:1 | #000000 | #793110 | Fail |
| h3 From efficiency to e… | 2.26:1 | 3.0:1 | #000000 | #793110 | Fail |
| h3 AI-Powered Customer … | 2.26:1 | 3.0:1 | #000000 | #793110 | Fail |
| h3 Braze Inspiration Gu… | 2.26:1 | 3.0:1 | #000000 | #793110 | Fail |
| h3 2026 Global Customer… | 2.26:1 | 3.0:1 | #000000 | #793110 | Fail |
| h3 Know your customer: … | 2.26:1 | 3.0:1 | #000000 | #793110 | Fail |
| h3 How to Build an AI M… | 2.26:1 | 3.0:1 | #000000 | #793110 | Fail |
| title Braze Customer Engag… | 5.24:1 | 4.5:1 | #000000 | #7F7F7F | Pass |
| a Why Braze? | 5.24:1 | 4.5:1 | #000000 | #7F7F7F | Pass |
| button Product | 3.88:1 | 4.5:1 | #000000 | #7F645B | Fail |
| button Back | 3.18:1 | 4.5:1 | #000000 | #7F523E | Fail |
| span The Braze Platform | 3.17:1 | 4.5:1 | #000000 | #7F5239 | Fail |
| span All your data, chann… | 3.16:1 | 4.5:1 | #000000 | #7F5234 | Fail |
| a View the platform | 3.15:1 | 4.5:1 | #000000 | #7F5230 | Fail |
| span BrazeAl™ | 3.14:1 | 4.5:1 | #000000 | #7F522B | Fail |
| span UPDATES | 3.14:1 | 4.5:1 | #000000 | #7F5226 | 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.
ALandmark Structure6 landmarksPASS
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
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+Alt Text QualityAll 71 images OKPASS
| Issue | Count |
|---|---|
| too long | 1 image(s) |
A+Form AccessibilityNo form controlsPASS
ALighthouse Accessibility AuditsScore 92/100 — 4 failing, 25 passedPASS
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
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
AI assistant body.__variable_97c7bb > q-focus-sentinel > div |
After AI assistant body.__variable_97c7bb > q-focus-sentinel > div |
AI assistant, start div#qualified-multimodal-host > div |
AI assistant, end div#qualified-multimodal-host > div |
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Braze Data Platform div.flex > div.flex > div.text-black > h4 |
These are opportunities to improve keyboard navigation in your application.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Go to slide 1 div.flex > div.w-full > div.flex > button.relative |
Go to slide 2 div.flex > div.w-full > div.flex > button.relative |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Braze is a Leader in the 2025 Gartner® Magic Quadrant™ for Multichannel Marketi… div.slick-track > div.slick-slide > div > a.h-full |
Cookie Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link |