Brave Searchsearch.brave.com
Accessibility Score
Issues Found
Issues Found
SeriousElements must meet minimum color contrast ratio thresholds8 elements
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Failing Elements
<span class="copyright">© Brave Software</span>
Fix any of the following:
- Element has insufficient color contrast of 4.39 (foreground color: #78787c, background color: #ffffff, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
<a href="https://ads.brave.com/register/search?mtm_source=brave-search&mtm_medium=searchhome&mtm_campaign=brave-search&mtm_content=evergreen" target="_blank" rel="noopener" class="svelte-4jwo3w">Advertise</a>
Fix any of the following:
- Element has insufficient color contrast of 4.39 (foreground color: #78787c, background color: #ffffff, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
<a href="https://brave.com/search/api/?mtm_source=brave-search&mtm_medium=searchhome&mtm_campaign=brave-search&mtm_content=evergreen" target="_blank" rel="noopener" class="svelte-4jwo3w">API</a>
Fix any of the following:
- Element has insufficient color contrast of 4.39 (foreground color: #78787c, background color: #ffffff, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
<a href="https://brave.com/category/brave-search/?mtm_source=brave-search&mtm_medium=searchhome&mtm_campaign=brave-search&mtm_content=evergreen" target="_blank" rel="noopener" class="svelte-4jwo3w">News</a>
Fix any of the following:
- Element has insufficient color contrast of 4.39 (foreground color: #78787c, background color: #ffffff, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
<a href="https://brave.com/search/#search-faq?mtm_source=brave-search&mtm_medium=searchhome&mtm_campaign=brave-search&mtm_content=evergreen" target="_blank" rel="noopener" class="svelte-4jwo3w">FAQ</a>
Fix any of the following:
- Element has insufficient color contrast of 4.39 (foreground color: #78787c, background color: #ffffff, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
<a href="/help/privacy-policy" target="_blank" rel="noopener noreferrer" data-sveltekit-reload="" class="svelte-4jwo3w">Privacy Policy</a>
Fix any of the following:
- Element has insufficient color contrast of 4.39 (foreground color: #78787c, background color: #ffffff, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
<a href="https://hackerone.com/brave" target="_blank" rel="noopener noreferrer" class="svelte-4jwo3w">Report a security issue</a>
Fix any of the following:
- Element has insufficient color contrast of 4.39 (foreground color: #78787c, background color: #ffffff, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1
<div class="text t-tertiary">
Fix any of the following:
- Element has insufficient color contrast of 3.92 (foreground color: #78787c, background color: #f2f2f3, font size: 9.8pt (13px), font weight: normal). Expected contrast ratio of 4.5:1
SeriousLinks must be distinguishable without relying on color2 elements
People with low vision or color blindness cannot visually distinguish links from surrounding text without sufficient color contrast (3:1 ratio minimum). When link colors are too similar to regular text, users with visual impairments cannot identify which text is clickable.
Failing Elements
<a href="/settings" target="_self" rel="noopener">Settings</a>
Fix any of the following:
- The link has insufficient color contrast of 1.46:1 with the surrounding text. (Minimum contrast is 3:1, link text: #434fcf, surrounding text: #78787c)
- The link has no styling (such as underline) to distinguish it from the surrounding text
<a href="/help/usage-metrics" target="_blank" data-sveltekit-reload="">Learn more.</a>
Fix any of the following:
- The link has insufficient color contrast of 1.46:1 with the surrounding text. (Minimum contrast is 3:1, link text: #434fcf, surrounding text: #78787c)
- The link has no styling (such as underline) to distinguish it from the surrounding text
ModeratePage should contain a level-one heading1 element
Screen reader users use keyboard shortcuts to jump directly to the first h1, expecting to land at the main content. Without an h1 or with a misplaced one, users must listen to more of the page to understand its structure, wasting valuable time on every page visit.
Failing Elements
<html class="" lang="en-us">
Fix all of the following:
- Page must have a level-one heading
ModerateAll page content should be contained by landmarks1 element
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Failing Elements
<div class="text t-tertiary">
Fix any of the following:
- Some page content is not contained by landmarks
Passed Audits
<html> element must have a lang attribute1 element
Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.
Audit Elements
<html class="" lang="en-us">
<html> element must have a valid value for the lang attribute1 element
Screen readers use language-specific sound libraries for proper pronunciation. Invalid language attributes cause screen readers to use the wrong library, making text sound like a confusing accent or completely unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<html class="" lang="en-us">
All page content should be contained by landmarks67 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<div style="display: contents">
<div id="main" class="full-height">
<div id="home-wrapper" class="svelte-1uha8ag">
<div class="waves-top svelte-1uha8ag"></div>
<div class="waves-bottom svelte-1uha8ag"></div>
<main class="svelte-1uha8ag">
<div id="settings" class="svelte-1uha8ag">
<div class="noscript-hide">
<button id="settings-button" type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Quick settings">
<div class="header-button-icon svelte-7b1tqz">
Showing first 10 of 67 audited elements.
Alternative text of images should not be repeated as text2 elements
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Audit Elements
<img src="https://cdn.search.brave.com/serp/v3/_app/immutable/assets/brave-logo-light.D0nx3pfh.svg" alt="Brave logo" title="Brave Search" height="64" class="svelte-bgy9eh">
<img alt="Brave logo" class="logo logo-small" title="Brave Search" width="21" height="24" src="https://cdn.search.brave.com/serp/v3/_app/immutable/assets/brave-logo-small.Bdzj7Bzm.svg">
ARIA attributes must be used as specified for the element's role7 elements
Using ARIA attributes where they're not expected causes unpredictable behavior in assistive technologies. Following the ARIA specification ensures that screen readers and other tools can properly interpret and communicate your content's meaning to people with disabilities.
Audit Elements
<button id="settings-button" type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Quick settings">
<button id="ai-features-button" type="button" aria-label="AI Features" class="svelte-1g34nor">
<textarea autofocus="" id="searchbox" rows="1" class="desktop-large-regula..." placeholder="Ask anything, find a..." name="q" autocapitalize="off" autocomplete="off" autocorrect="off" aria-label="Search" title="Search" aria-autocomplete="both" aria-haspopup="false" maxlength="2048" ...>
<button type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Start voice input">
<button id="submit-llm-button" type="button" role="button" class="ask-button svelte-xzovz4 is-homepage animate" aria-label="Ask">
<button class="button svelte-na4a2u type size--tiny type--plain-faint theme--default icon-only icon-start tooltip--bottom" role="button" rel="noopener" aria-label="Close" data-sveltekit-reload="true">
<div id="svelte-announcer" aria-live="assertive" aria-atomic="true" style="position: absolute; left: 0; top: 0; clip: rect(0 0 0 0); clip-path: inset(50%); overflow: hidden; white-space: nowrap; width: 1px; height: 1px"><!----></div>
ARIA attributes must conform to valid names7 elements
Misspelled or non-existent ARIA attributes cannot perform their intended accessibility function. Assistive technologies rely on correctly spelled, current ARIA attributes to convey proper user interface behaviors and structural information to people with disabilities.
Audit Elements
<button id="settings-button" type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Quick settings">
<button id="ai-features-button" type="button" aria-label="AI Features" class="svelte-1g34nor">
<textarea autofocus="" id="searchbox" rows="1" class="desktop-large-regula..." placeholder="Ask anything, find a..." name="q" autocapitalize="off" autocomplete="off" autocorrect="off" aria-label="Search" title="Search" aria-autocomplete="both" aria-haspopup="false" maxlength="2048" ...>
<button type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Start voice input">
<button id="submit-llm-button" type="button" role="button" class="ask-button svelte-xzovz4 is-homepage animate" aria-label="Ask">
<button class="button svelte-na4a2u type size--tiny type--plain-faint theme--default icon-only icon-start tooltip--bottom" role="button" rel="noopener" aria-label="Close" data-sveltekit-reload="true">
<div id="svelte-announcer" aria-live="assertive" aria-atomic="true" style="position: absolute; left: 0; top: 0; clip: rect(0 0 0 0); clip-path: inset(50%); overflow: hidden; white-space: nowrap; width: 1px; height: 1px"><!----></div>
ARIA attributes must conform to valid values7 elements
ARIA attributes must contain correctly spelled values that match the attribute's expected options. Invalid values prevent the accessibility feature from working, making content inaccessible to assistive technology users who depend on these attributes for navigation and interaction.
Audit Elements
<button id="settings-button" type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Quick settings">
<button id="ai-features-button" type="button" aria-label="AI Features" class="svelte-1g34nor">
<textarea autofocus="" id="searchbox" rows="1" class="desktop-large-regula..." placeholder="Ask anything, find a..." name="q" autocapitalize="off" autocomplete="off" autocorrect="off" aria-label="Search" title="Search" aria-autocomplete="both" aria-haspopup="false" maxlength="2048" ...>
<button type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Start voice input">
<button id="submit-llm-button" type="button" role="button" class="ask-button svelte-xzovz4 is-homepage animate" aria-label="Ask">
<button class="button svelte-na4a2u type size--tiny type--plain-faint theme--default icon-only icon-start tooltip--bottom" role="button" rel="noopener" aria-label="Close" data-sveltekit-reload="true">
<div id="svelte-announcer" aria-live="assertive" aria-atomic="true" style="position: absolute; left: 0; top: 0; clip: rect(0 0 0 0); clip-path: inset(50%); overflow: hidden; white-space: nowrap; width: 1px; height: 1px"><!----></div>
ARIA hidden element must not be focusable or contain focusable elements2 elements
Elements with aria-hidden="true" are removed from the accessibility API but remain keyboard-focusable, creating confusion about their visibility state. When users tab to these hidden elements, screen readers stay silent, leaving users unaware of what they've focused on or why nothing is being announced.
Audit Elements
<svg xmlns="http://www.w3.org/2000/svg" aria-hidden="true" style="height:0;position:absolute;width:0">
<div class="ask-button-content-overlay svelte-xzovz4" aria-hidden="true">
ARIA role should be appropriate for the element4 elements
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Audit Elements
<button id="settings-button" type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Quick settings">
<button type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Start voice input">
<button id="submit-llm-button" type="button" role="button" class="ask-button svelte-xzovz4 is-homepage animate" aria-label="Ask">
<button class="button svelte-na4a2u type size--tiny type--plain-faint theme--default icon-only icon-start tooltip--bottom" role="button" rel="noopener" aria-label="Close" data-sveltekit-reload="true">
ARIA roles used must conform to valid values4 elements
Invalid ARIA role values prevent assistive technologies from understanding and communicating the element's purpose to users. Without valid roles, screen readers cannot provide information about the element's features, properties, or how users should interact with it.
Audit Elements
<button id="settings-button" type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Quick settings">
<button type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Start voice input">
<button id="submit-llm-button" type="button" role="button" class="ask-button svelte-xzovz4 is-homepage animate" aria-label="Ask">
<button class="button svelte-na4a2u type size--tiny type--plain-faint theme--default icon-only icon-start tooltip--bottom" role="button" rel="noopener" aria-label="Close" data-sveltekit-reload="true">
aria-hidden="true" must not be present on the document body1 element
Setting <body aria-hidden="true" hides all page content from assistive technologies while leaving it visible on screen. This creates a confusing experience where keyboard users can still tab to elements, but screen readers remain completely silent, providing no information about what's focused.
Audit Elements
<body class="is-pc is-serp">
autocomplete attribute must be used correctly1 element
Missing or incorrect autocomplete values make forms inaccessible to screen reader users. Screen readers cannot provide adequate information about form fields without proper autocomplete attributes, preventing users from understanding what information is required and how to complete forms correctly.
Audit Elements
<textarea autofocus="" id="searchbox" rows="1" class="desktop-large-regula..." placeholder="Ask anything, find a..." name="q" autocapitalize="off" autocomplete="off" autocorrect="off" aria-label="Search" title="Search" aria-autocomplete="both" aria-haspopup="false" maxlength="2048" ...>
Buttons must have discernible text5 elements
Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.
Audit Elements
<button id="settings-button" type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Quick settings">
<button id="ai-features-button" type="button" aria-label="AI Features" class="svelte-1g34nor">
<button type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Start voice input">
<button id="submit-llm-button" type="button" role="button" class="ask-button svelte-xzovz4 is-homepage animate" aria-label="Ask">
<button class="button svelte-na4a2u type size--tiny type--plain-faint theme--default icon-only icon-start tooltip--bottom" role="button" rel="noopener" aria-label="Close" data-sveltekit-reload="true">
Contentinfo landmark should not be contained in another landmark1 element
The contentinfo landmark must be at the top level to help screen reader users quickly navigate to footer information. When nested inside another landmark, it becomes harder to find, defeating its purpose of providing quick access to content information.
Audit Elements
<footer class="desktop-small-regular t-tertiary svelte-4jwo3w">
Deprecated ARIA roles must not be used4 elements
Deprecated ARIA roles are not recognized by modern screen readers and assistive technologies. Using outdated roles means some users cannot access essential information or functionality on your site.
Audit Elements
<button id="settings-button" type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Quick settings">
<button type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Start voice input">
<button id="submit-llm-button" type="button" role="button" class="ask-button svelte-xzovz4 is-homepage animate" aria-label="Ask">
<button class="button svelte-na4a2u type size--tiny type--plain-faint theme--default icon-only icon-start tooltip--bottom" role="button" rel="noopener" aria-label="Close" data-sveltekit-reload="true">
Document should have one main landmark1 element
Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.
Audit Elements
<html class="" lang="en-us">
Document should not have more than one contentinfo landmark1 element
Multiple contentinfo landmarks force screen reader users to sort through extra options to find footer information. Each page should have only one content info landmark to enable quick, predictable navigation without overwhelming users with duplicate structural markers.
Audit Elements
<footer class="desktop-small-regular t-tertiary svelte-4jwo3w">
Document should not have more than one main landmark1 element
Multiple main landmarks confuse screen reader users about where the primary content is located. Each page should have only one main landmark so users can quickly and predictably navigate to the primary content area.
Audit Elements
<main class="svelte-1uha8ag">
Documents must have <title> element to aid in navigation1 element
The page title is the first thing screen reader users hear when loading a page. Without a descriptive, unique title, users must read through the entire page to understand its contents and purpose, wasting valuable time on every page visit.
Audit Elements
<html class="" lang="en-us">
Elements must meet minimum color contrast ratio thresholds4 elements
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Audit Elements
<input type="file" accept="image/*" class="image-input svelte-1g34nor">
<textarea autofocus="" id="searchbox" rows="1" class="desktop-large-regula..." placeholder="Ask anything, find a..." name="q" autocapitalize="off" autocomplete="off" autocorrect="off" aria-label="Search" title="Search" aria-autocomplete="both" aria-haspopup="false" maxlength="2048" ...>
<a href="/settings" target="_self" rel="noopener">Settings</a>
<a href="/help/usage-metrics" target="_blank" data-sveltekit-reload="">Learn more.</a>
Elements must only use permitted ARIA attributes7 elements
Using prohibited ARIA attributes prevents important information from reaching assistive technology users. It also causes assistive technologies to behave inconsistently as they attempt to compensate for the error.
Audit Elements
<button id="settings-button" type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Quick settings">
<button id="ai-features-button" type="button" aria-label="AI Features" class="svelte-1g34nor">
<textarea autofocus="" id="searchbox" rows="1" class="desktop-large-regula..." placeholder="Ask anything, find a..." name="q" autocapitalize="off" autocomplete="off" autocorrect="off" aria-label="Search" title="Search" aria-autocomplete="both" aria-haspopup="false" maxlength="2048" ...>
<button type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Start voice input">
<button id="submit-llm-button" type="button" role="button" class="ask-button svelte-xzovz4 is-homepage animate" aria-label="Ask">
<button class="button svelte-na4a2u type size--tiny type--plain-faint theme--default icon-only icon-start tooltip--bottom" role="button" rel="noopener" aria-label="Close" data-sveltekit-reload="true">
<div id="svelte-announcer" aria-live="assertive" aria-atomic="true" style="position: absolute; left: 0; top: 0; clip: rect(0 0 0 0); clip-path: inset(50%); overflow: hidden; white-space: nowrap; width: 1px; height: 1px"><!----></div>
Elements must only use supported ARIA attributes7 elements
Using ARIA attributes in roles where they're not allowed can disable accessibility for entire sections of your application. Invalid attribute-role combinations create conflicts that cause assistive technologies to report incorrect or nonsensical information about your interface.
Audit Elements
<button id="settings-button" type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Quick settings">
<button id="ai-features-button" type="button" aria-label="AI Features" class="svelte-1g34nor">
<textarea autofocus="" id="searchbox" rows="1" class="desktop-large-regula..." placeholder="Ask anything, find a..." name="q" autocapitalize="off" autocomplete="off" autocorrect="off" aria-label="Search" title="Search" aria-autocomplete="both" aria-haspopup="false" maxlength="2048" ...>
<button type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Start voice input">
<button id="submit-llm-button" type="button" role="button" class="ask-button svelte-xzovz4 is-homepage animate" aria-label="Ask">
<button class="button svelte-na4a2u type size--tiny type--plain-faint theme--default icon-only icon-start tooltip--bottom" role="button" rel="noopener" aria-label="Close" data-sveltekit-reload="true">
<div id="svelte-announcer" aria-live="assertive" aria-atomic="true" style="position: absolute; left: 0; top: 0; clip: rect(0 0 0 0); clip-path: inset(50%); overflow: hidden; white-space: nowrap; width: 1px; height: 1px"><!----></div>
Form elements must have labels1 element
Form labels are essential for screen reader users to understand what information each field requires. Without proper labels, screen readers cannot identify input expectations, fields don't receive focus when announced, and users with motor impairments lose the benefit of larger clickable areas that labels provide.
Audit Elements
<textarea autofocus="" id="searchbox" rows="1" class="desktop-large-regula..." placeholder="Ask anything, find a..." name="q" autocapitalize="off" autocomplete="off" autocorrect="off" aria-label="Search" title="Search" aria-autocomplete="both" aria-haspopup="false" maxlength="2048" ...>
Form elements should have a visible label1 element
The title and aria-describedby attributes provide supplementary hints, not labels. Screen readers treat these as advisory information rather than true labels, which prevents them from properly conveying the form element's purpose. Form fields need proper labels that can be programmatically determined.
Audit Elements
<textarea autofocus="" id="searchbox" rows="1" class="desktop-large-regula..." placeholder="Ask anything, find a..." name="q" autocapitalize="off" autocomplete="off" autocorrect="off" aria-label="Search" title="Search" aria-autocomplete="both" aria-haspopup="false" maxlength="2048" ...>
Form field must not have multiple label elements1 element
Multiple labels on the same form field cause inconsistent behavior across screen reader and browser combinations. Some will read the first label, others the last, and some will read both, creating confusion about what information the field requires.
Audit Elements
<textarea autofocus="" id="searchbox" rows="1" class="desktop-large-regula..." placeholder="Ask anything, find a..." name="q" autocapitalize="off" autocomplete="off" autocorrect="off" aria-label="Search" title="Search" aria-autocomplete="both" aria-haspopup="false" maxlength="2048" ...>
Images must have alternative text2 elements
Screen readers cannot translate images into text without alt attributes. Alternative text is essential for blind users and beneficial for users with low vision or color blindness, providing the same information that sighted users get from viewing the image.
Audit Elements
<img src="https://cdn.search.brave.com/serp/v3/_app/immutable/assets/brave-logo-light.D0nx3pfh.svg" alt="Brave logo" title="Brave Search" height="64" class="svelte-bgy9eh">
<img alt="Brave logo" class="logo logo-small" title="Brave Search" width="21" height="24" src="https://cdn.search.brave.com/serp/v3/_app/immutable/assets/brave-logo-small.Bdzj7Bzm.svg">
Inline text spacing must be adjustable with custom stylesheets2 elements
Single-spaced text makes it difficult for people with cognitive disabilities to track lines while reading. Providing line spacing between 1.5 to 2 helps these users start a new line more easily after finishing the previous one.
Audit Elements
<div style="display: contents">
<textarea autofocus="" id="searchbox" rows="1" class="desktop-large-regula..." placeholder="Ask anything, find a..." name="q" autocapitalize="off" autocomplete="off" autocorrect="off" aria-label="Search" title="Search" aria-autocomplete="both" aria-haspopup="false" maxlength="2048" ...>
Interactive controls must not be nested7 elements
Nested interactive elements create empty tab stops where screen readers remain silent. When users tab to a focusable element inside another interactive control, they receive no information about its name, role, or state, creating a confusing and broken navigation experience.
Audit Elements
<button id="settings-button" type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Quick settings">
<img src="https://cdn.search.brave.com/serp/v3/_app/immutable/assets/brave-logo-light.D0nx3pfh.svg" alt="Brave logo" title="Brave Search" height="64" class="svelte-bgy9eh">
<button id="ai-features-button" type="button" aria-label="AI Features" class="svelte-1g34nor">
<button type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Start voice input">
<button id="submit-llm-button" type="button" role="button" class="ask-button svelte-xzovz4 is-homepage animate" aria-label="Ask">
<img alt="Brave logo" class="logo logo-small" title="Brave Search" width="21" height="24" src="https://cdn.search.brave.com/serp/v3/_app/immutable/assets/brave-logo-small.Bdzj7Bzm.svg">
<button class="button svelte-na4a2u type size--tiny type--plain-faint theme--default icon-only icon-start tooltip--bottom" role="button" rel="noopener" aria-label="Close" data-sveltekit-reload="true">
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination2 elements
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Audit Elements
<main class="svelte-1uha8ag">
<footer class="desktop-small-regular t-tertiary svelte-4jwo3w">
Links must have discernible text10 elements
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Audit Elements
<a id="logo" href="/" data-sveltekit-reload="" class="svelte-1uha8ag">
<a class="download-cta-button desktop-small-regular svelte-1uha8ag" href="https://brave.com/download/now/?mtm_campaign=search-homepage-cta" target="_self">
<a href="https://ads.brave.com/register/search?mtm_source=brave-search&mtm_medium=searchhome&mtm_campaign=brave-search&mtm_content=evergreen" target="_blank" rel="noopener" class="svelte-4jwo3w">Advertise</a>
<a href="https://brave.com/search/api/?mtm_source=brave-search&mtm_medium=searchhome&mtm_campaign=brave-search&mtm_content=evergreen" target="_blank" rel="noopener" class="svelte-4jwo3w">API</a>
<a href="https://brave.com/category/brave-search/?mtm_source=brave-search&mtm_medium=searchhome&mtm_campaign=brave-search&mtm_content=evergreen" target="_blank" rel="noopener" class="svelte-4jwo3w">News</a>
<a href="https://brave.com/search/#search-faq?mtm_source=brave-search&mtm_medium=searchhome&mtm_campaign=brave-search&mtm_content=evergreen" target="_blank" rel="noopener" class="svelte-4jwo3w">FAQ</a>
<a href="/help/privacy-policy" target="_blank" rel="noopener noreferrer" data-sveltekit-reload="" class="svelte-4jwo3w">Privacy Policy</a>
<a href="https://hackerone.com/brave" target="_blank" rel="noopener noreferrer" class="svelte-4jwo3w">Report a security issue</a>
<a href="/settings" target="_self" rel="noopener">Settings</a>
<a href="/help/usage-metrics" target="_blank" data-sveltekit-reload="">Learn more.</a>
Main landmark should not be contained in another landmark1 element
The main landmark must be at the top level and not nested inside other landmarks. This ensures screen reader users can quickly navigate to the primary content without searching through complex hierarchy, making page navigation simpler and more predictable.
Audit Elements
<main class="svelte-1uha8ag">
Page must have means to bypass repeated blocks1 element
Keyboard-only users must tab through all navigation and header content before reaching the main content, which can take several minutes and cause physical pain for users with motor limitations. Bypass mechanisms like skip links allow these users to jump directly to main content, saving time and reducing fatigue.
Audit Elements
<html class="" lang="en-us">
Required ARIA attributes must be provided4 elements
ARIA widget roles need required attributes to describe their current state. Without these attributes, screen readers cannot communicate essential information like whether a checkbox is checked or a slider's current value, leaving users unable to interact effectively with the widget.
Audit Elements
<button id="settings-button" type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Quick settings">
<button type="button" role="button" class="header-button svelte-7b1tqz" aria-label="Start voice input">
<button id="submit-llm-button" type="button" role="button" class="ask-button svelte-xzovz4 is-homepage animate" aria-label="Ask">
<button class="button svelte-na4a2u type size--tiny type--plain-faint theme--default icon-only icon-start tooltip--bottom" role="button" rel="noopener" aria-label="Close" data-sveltekit-reload="true">