brave.com Accessibility Report

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

Technology
0 /100
F Critical Issues

6 issues found across 2 categories

3 Critical 3 Major

WCAG Compliance Overview

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

Issues Found

Images missing alt text

Critical

Images must have alternative text to convey their meaning to screen reader users.

WCAG 1.1.1
1 element(s) affected
  • <img src="/static-assets/images/brave-logo-text-only.svg">
How to fix

Add descriptive alt attributes to all <img> elements. Use alt="" for decorative images.

Form inputs missing labels

Critical

Form elements must have associated labels so users know what information to enter.

WCAG 1.3.1
9 element(s) affected
  • <input type="text" name="q">
  • <input type="range" name="(no name)">
  • <input type="range" name="(no name)">
  • <input type="range" name="(no name)">
  • <input type="range" name="(no name)">
How to fix

Add <label> elements with matching for attributes, or use aria-label.

Buttons missing accessible name

Critical

Buttons must have discernible text for screen reader users.

WCAG 4.1.2
2 element(s) affected
  • <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
3 element(s) affected
  • <h4> "Private search" (after h1)
  • <h4> "Brave vs Chrome" (after h2)
  • <h4> "User resources" (after h2)
How to fix

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

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.

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
3 element(s) affected
  • <a href="/privacy-features/">learn more</a>
  • <a href="/compare/chrome-vs-brave/">learn more</a>
  • <a href="https://laptop-updates.brave.com/download/BRV002">here</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 brave.com should make to improve accessibility:

  1. #1
    Form inputs missing labels Critical

    Add <label> elements with matching for attributes, or use aria-label.

  2. #2
    Buttons missing accessible name Critical

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

  3. #3
    Images missing alt text Critical

    Add descriptive alt attributes to all <img> elements. Use alt="" for decorative images.

Frequently Asked Questions

Is brave.com accessible?

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

Is brave.com WCAG compliant?

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

Is brave.com EAA compliant?

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

What accessibility issues does brave.com have?

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

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing