braze.com Accessibility Report

Accessibility audit of braze.com — scanned on Feb 20, 2026

Technology
0 /100
F Critical Issues

8 issues found across 2 categories

1 Critical 7 Major

WCAG Compliance Overview

Perceivable 1 issues
Operable 4 issues
Understandable 0 issues
Robust 3 issues

Issues Found

Buttons missing accessible name

Critical

Buttons must have discernible text for screen reader users.

WCAG 4.1.2
3 element(s) affected
  • <button>
  • <button>
  • <button>
How to fix

Add text content, aria-label, or title to all <button> elements.

Heading levels skip order

Major

Headings should follow a logical order (h1 → h2 → h3) without skipping levels.

WCAG 1.3.1
1 element(s) affected
  • <h4> "" (after h2)
How to fix

Restructure headings to follow sequential order. Don't skip from h1 to h3.

Frames missing title

Major

Iframes must have title attributes describing their content.

WCAG 2.4.1
1 element(s) affected
  • <iframe src="https://www.googletagmanager.com/ns.html?id=GTM-W3ZW3HBZ">
How to fix

Add descriptive title attributes to all <iframe> elements.

Duplicate element IDs

Major

Element IDs must be unique to ensure correct assistive technology behavior.

WCAG 4.1.1
2 element(s) affected
  • id="object-object"
How to fix

Make each id attribute value unique within the page.

No skip navigation link

Major

Pages should have a mechanism to bypass repeated navigation blocks.

WCAG 2.4.1
1 element(s) affected
  • No skip navigation link found
How to fix

Add a 'Skip to main content' link as the first focusable element on the page.

Invalid ARIA attributes

Major

ARIA attributes must be valid and used correctly to work with assistive technologies.

WCAG 4.1.2
1 element(s) affected
  • <nav aria-labelledby="language-switcher-button"> (missing ref)
How to fix

Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.

Focus indicator not visible

Major

Interactive elements must have visible focus indicators for keyboard users.

WCAG 2.4.7
13 element(s) affected
  • <div style="...outline:none...">
  • <div style="...outline:none...">
  • <div style="...outline:none...">
  • <div style="...outline:none...">
  • <div style="...outline:none...">
How to fix

Ensure :focus styles are visible. Don't use outline: none without a replacement.

Generic link text

Major

Links must have descriptive text that indicates their purpose. Generic text like 'click here' or 'read more' does not help screen reader users understand where the link goes.

WCAG 2.4.4
1 element(s) affected
  • <a href="/product">learn more</a>
How to fix

Replace generic link text with descriptive text, e.g., 'Read our accessibility guide' instead of 'Read more'.

Top Priority Fixes

Here are the most impactful changes braze.com should make to improve accessibility:

  1. #1
    Buttons missing accessible name Critical

    Add text content, aria-label, or title to all <button> elements.

  2. #2
    Focus indicator not visible Major

    Ensure :focus styles are visible. Don't use outline: none without a replacement.

  3. #3
    Duplicate element IDs Major

    Make each id attribute value unique within the page.

Frequently Asked Questions

Is braze.com accessible?

braze.com scored 29/100 (grade F) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is braze.com WCAG compliant?

Our scan found 8 accessibility issues on braze.com. Full WCAG compliance requires addressing all critical and major issues identified above.

Is braze.com EAA compliant?

The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see braze.com's compliance status.

What accessibility issues does braze.com have?

See the full issue list above with severity levels, affected elements, and recommended fixes for braze.com.

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing