Buttons missing accessible name
KritischButtons must have discernible text for screen reader users.
WCAG 4.1.23 Element(e) betroffen
<button><button><button>
Wie zu beheben
Add text content, aria-label, or title to all <button> elements.
Barrierefreiheitsaudit von braze.com — gescannt am Feb 20, 2026
Technology8 Probleme in 2 Kategorien gefunden
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'.
Hier sind die wirkungsvollsten Änderungen, die braze.com vornehmen sollte:
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 erzielte 29/100 (Note F) in unserem Barrierefreiheitsaudit. Dieser Score basiert auf automatisierten Prüfungen nach WCAG 2.1 Level AA.
Unser Scan hat 8 Barrierefreiheitsprobleme auf braze.com gefunden. Vollständige WCAG-Konformität erfordert die Behebung aller kritischen und schwerwiegenden Probleme.
Das Barrierefreiheitsstärkungsgesetz verlangt, dass Websites den WCAG 2.1 AA-Standards entsprechen. Prüfen Sie den Bericht oben für den Konformitätsstatus von braze.com.
Sehen Sie die vollständige Problemliste oben mit Schweregradangaben, betroffenen Elementen und empfohlenen Korrekturen für braze.com.
Erhalten Sie in Sekunden einen kostenlosen Barrierefreiheitsbericht.