Buttons missing accessible name
CríticoButtons must have discernible text for screen reader users.
WCAG 4.1.23 elemento(s) afetado(s)
<button><button><button>
Como corrigir
Add text content, aria-label, or title to all <button> elements.
Auditoria de acessibilidade de braze.com — verificado em Feb 20, 2026
Technology8 problemas encontrados em 2 categorias
Buttons must have discernible text for screen reader users.
WCAG 4.1.2<button><button><button>Add text content, aria-label, or title to all <button> elements.
Headings should follow a logical order (h1 → h2 → h3) without skipping levels.
WCAG 1.3.1<h4> "" (after h2)Restructure headings to follow sequential order. Don't skip from h1 to h3.
Iframes must have title attributes describing their content.
WCAG 2.4.1<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-W3ZW3HBZ">Add descriptive title attributes to all <iframe> elements.
Element IDs must be unique to ensure correct assistive technology behavior.
WCAG 4.1.1id="object-object"Make each id attribute value unique within the page.
Pages should have a mechanism to bypass repeated navigation blocks.
WCAG 2.4.1No skip navigation link foundAdd a 'Skip to main content' link as the first focusable element on the page.
ARIA attributes must be valid and used correctly to work with assistive technologies.
WCAG 4.1.2<nav aria-labelledby="language-switcher-button"> (missing ref)Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.
Interactive elements must have visible focus indicators for keyboard users.
WCAG 2.4.7<div style="...outline:none..."><div style="...outline:none..."><div style="...outline:none..."><div style="...outline:none..."><div style="...outline:none...">Ensure :focus styles are visible. Don't use outline: none without a replacement.
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<a href="/product">learn more</a>Replace generic link text with descriptive text, e.g., 'Read our accessibility guide' instead of 'Read more'.
Aqui estão as mudanças mais impactantes que braze.com deveria fazer:
Add text content, aria-label, or title to all <button> elements.
Ensure :focus styles are visible. Don't use outline: none without a replacement.
Make each id attribute value unique within the page.
braze.com obteve 29/100 (nota F) em nossa auditoria. Esta pontuação reflete verificações automáticas segundo WCAG 2.1 nível AA.
Nosso scan encontrou 8 problemas de acessibilidade em braze.com. A conformidade WCAG completa requer resolver todos os problemas críticos e maiores.
A Lei Europeia de Acessibilidade exige que os sites cumpram WCAG 2.1 AA. Consulte o relatório detalhado acima para o estado de conformidade de braze.com.
Consulte a lista completa de problemas acima com níveis de gravidade, elementos afetados e correções recomendadas para braze.com.
Obtenha um relatório de acessibilidade gratuito em segundos.