Startpagestartpage.com
Accessibility Score
Issues Found
Issues Found
SeriousElements 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.
Failing Elements
<span class="link-text">Add to Chrome</span>
Fix any of the following:
- Element has insufficient color contrast of 1.7 (foreground color: #ffffff, background color: #29ddcc, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1
<p>MIS Professor of Social and Ethical Issues of the Internet</p>
Fix any of the following:
- Element has insufficient color contrast of 3.49 (foreground color: #7f869e, background color: #fbfbfd, font size: 9.8pt (13px), font weight: normal). Expected contrast ratio of 4.5:1
<p>President of Freedom of the Press Foundation</p>
Fix any of the following:
- Element has insufficient color contrast of 3.49 (foreground color: #7f869e, background color: #fbfbfd, font size: 9.8pt (13px), font weight: normal). Expected contrast ratio of 4.5:1
<p>Founder of NOYB - European Center for Digital Rights</p>
Fix any of the following:
- Element has insufficient color contrast of 3.49 (foreground color: #7f869e, background color: #fbfbfd, font size: 9.8pt (13px), font weight: normal). Expected contrast ratio of 4.5:1
SeriousInteractive controls must not be nested1 element
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.
Failing Elements
<div class="hide-promo css-2f320f" role="button" tabindex="0"><div role="button" tabindex="0" class="css-zhw45g"><div class="hide-promo-image-container css-1sx5uuz"><div class="hide-promo-image css-y54zji"></div></div><span class="hide-promo-text">Hide promotional messaging</span></div></div>
Fix any of the following:
- Element has focusable descendants
ModerateContentinfo 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.
Failing Elements
<footer role="contentinfo" aria-label="footer" class="css-1h47swe eu3pp1u0">
Fix any of the following:
- The contentinfo landmark is contained in another landmark.
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 lang="en">
Fix all of the following:
- Page must have a level-one heading
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 lang="en">
<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 lang="en">
All page content should be contained by landmarks210 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 id="root">
<div class="themeProvider">
<div class="Layout">
<main id="home" class="home">
<section class="hero css-1crqdqo">
<div id="home-top-header" class="banner-container css-beuhud">
<div class="nav-container css-1rlv5cb">
<div class="nav-app-promo css-5ej25d">
<div class="css-1pducxn"></div>
<div class="hamburger-menu-app-promo" data-hide-promo-messaging="false">
Showing first 10 of 210 audited elements.
Alternative text of images should not be repeated as text22 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 class="no-script-hide css-1guhnn0" height="100%" width="100%" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-1guhnn0" height="100%" width="100%" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-1guhnn0" height="100%" width="100%" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-1iyuuc5" height="55px" width="55px" src="" alt="" loading="lazy" data-testid="test-image">
Showing first 10 of 22 audited elements.
ARIA attributes must be used as specified for the element's role22 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
<div class="hamburger-button css-1g9wt7p" data-testid="hamburger-menu-toggle" role="button" aria-label="hamburger menu" tabindex="0"><i></i></div>
<form action="/do/settings" method="post" class="css-13cn4bc" aria-label="Settings">
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="hamburger-menu-brows..." title="" tabindex="0" class="home-cta css-16okzfa">
<form action="/sp/search" method="post" class="search-form-form" id="search" data-testid="search" role="search" aria-label="top search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q" data-testid="q" maxlength="2048" name="query" placeholder="Search privately" role="searchbox" spellcheck="false" title="Search" type="text" class="search-form-input" value="">
<button class="search-btn" type="submit" aria-label="search button"></button>
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="home-cta" title="" tabindex="0" class="home-cta css-zjntmh">
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="home-cta" title="" tabindex="0" class="home-cta css-usj27l">
<form action="/sp/search" method="post" class="search-form-form" id="search-btf" data-testid="search" role="search" aria-label="bottom search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q-btf" data-testid="q" maxlength="2048" name="query" placeholder="Start your search wi..." role="searchbox" spellcheck="false" title="Search" type="text" value="" ...>
Showing first 10 of 22 audited elements.
ARIA attributes must conform to valid names22 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
<div class="hamburger-button css-1g9wt7p" data-testid="hamburger-menu-toggle" role="button" aria-label="hamburger menu" tabindex="0"><i></i></div>
<form action="/do/settings" method="post" class="css-13cn4bc" aria-label="Settings">
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="hamburger-menu-brows..." title="" tabindex="0" class="home-cta css-16okzfa">
<form action="/sp/search" method="post" class="search-form-form" id="search" data-testid="search" role="search" aria-label="top search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q" data-testid="q" maxlength="2048" name="query" placeholder="Search privately" role="searchbox" spellcheck="false" title="Search" type="text" class="search-form-input" value="">
<button class="search-btn" type="submit" aria-label="search button"></button>
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="home-cta" title="" tabindex="0" class="home-cta css-zjntmh">
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="home-cta" title="" tabindex="0" class="home-cta css-usj27l">
<form action="/sp/search" method="post" class="search-form-form" id="search-btf" data-testid="search" role="search" aria-label="bottom search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q-btf" data-testid="q" maxlength="2048" name="query" placeholder="Start your search wi..." role="searchbox" spellcheck="false" title="Search" type="text" value="" ...>
Showing first 10 of 22 audited elements.
ARIA attributes must conform to valid values22 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
<div class="hamburger-button css-1g9wt7p" data-testid="hamburger-menu-toggle" role="button" aria-label="hamburger menu" tabindex="0"><i></i></div>
<form action="/do/settings" method="post" class="css-13cn4bc" aria-label="Settings">
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="hamburger-menu-brows..." title="" tabindex="0" class="home-cta css-16okzfa">
<form action="/sp/search" method="post" class="search-form-form" id="search" data-testid="search" role="search" aria-label="top search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q" data-testid="q" maxlength="2048" name="query" placeholder="Search privately" role="searchbox" spellcheck="false" title="Search" type="text" class="search-form-input" value="">
<button class="search-btn" type="submit" aria-label="search button"></button>
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="home-cta" title="" tabindex="0" class="home-cta css-zjntmh">
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="home-cta" title="" tabindex="0" class="home-cta css-usj27l">
<form action="/sp/search" method="post" class="search-form-form" id="search-btf" data-testid="search" role="search" aria-label="bottom search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q-btf" data-testid="q" maxlength="2048" name="query" placeholder="Start your search wi..." role="searchbox" spellcheck="false" title="Search" type="text" value="" ...>
Showing first 10 of 22 audited elements.
ARIA commands must have an accessible name3 elements
Screen reader users cannot determine the purpose of interactive elements with role="link", role="button", or role="menuitem" that lack an accessible name. Without a name, these controls are essentially invisible to assistive technology users.
Audit Elements
<div class="hamburger-button css-1g9wt7p" data-testid="hamburger-menu-toggle" role="button" aria-label="hamburger menu" tabindex="0"><i></i></div>
<div class="hide-promo css-2f320f" role="button" tabindex="0"><div role="button" tabindex="0" class="css-zhw45g"><div class="hide-promo-image-container css-1sx5uuz"><div class="hide-promo-image css-y54zji"></div></div><span class="hide-promo-text">Hide promotional messaging</span></div></div>
<div role="button" tabindex="0" class="css-zhw45g"><div class="hide-promo-image-container css-1sx5uuz"><div class="hide-promo-image css-y54zji"></div></div><span class="hide-promo-text">Hide promotional messaging</span></div>
ARIA hidden element must not be focusable or contain focusable elements15 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
<div class="close-btn css-hpffgq" role="button" tabindex="-1" aria-label="close hamburger menu" aria-hidden="true">
<svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg" stroke="#374677" stroke-width="1.5" aria-hidden="true">
<a href="/?sc=rUGuvI93a7DP00&t=device" rel="noopener nofollow" target="_self" aria-label="Startpage Search" aria-hidden="true" data-testid="" title="" tabindex="-1" class="link-text css-5pmhv9">
<a href="https://app.startpage.com/?source=home-hamburger" rel="noopener nofollow" target="_self" aria-label="Mobile Browser" aria-hidden="true" data-testid="" title="" tabindex="-1" class="link-text css-5pmhv9">
<a href="https://vanish.startpage.com/en/?source=default" rel="noopener nofollow" target="_self" aria-label="Vanish: Private AI" aria-hidden="true" data-testid="" title="" tabindex="-1" class="link-text css-xiv83d">
<a href="https://www.startpage.com/en/about-us?t=device" rel="noopener nofollow" target="_self" aria-label="About Us" aria-hidden="true" data-testid="" title="" tabindex="-1" class="link-text css-1y67b6v"><span class="link-text">About Us</span></a>
<a href="https://www.startpage.com/en/privacy-policy?t=device" rel="noopener nofollow" target="_self" aria-label="Privacy Policy" aria-hidden="true" data-testid="" title="" tabindex="-1" class="link-text css-1y67b6v"><span class="link-text">Privacy Policy</span></a>
<a href="https://www.startpage.com/privacy-please/press/" rel="noopener nofollow" target="_self" aria-label="Press" aria-hidden="true" data-testid="" title="" tabindex="-1" class="link-text css-1y67b6v"><span class="link-text">Press</span></a>
<a href="https://support.startpage.com/hc/en-us" rel="noopener nofollow" target="_self" aria-label="Support" aria-hidden="true" data-testid="" title="" tabindex="-1" class="link-text css-1y67b6v"><span class="link-text">Support</span></a>
<a href="https://support.startpage.com/hc/en-us/articles/4521527855636-Impressum" rel="noopener nofollow" target="_self" aria-label="Imprint" aria-hidden="true" data-testid="" title="" tabindex="-1" class="link-text css-1y67b6v"><span class="link-text">Imprint</span></a>
Showing first 10 of 15 audited elements.
ARIA role should be appropriate for the element11 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
<div class="hamburger-button css-1g9wt7p" data-testid="hamburger-menu-toggle" role="button" aria-label="hamburger menu" tabindex="0"><i></i></div>
<div class="close-btn css-hpffgq" role="button" tabindex="-1" aria-label="close hamburger menu" aria-hidden="true">
<button tabindex="-1" class="css-ocm99y" type="submit" data-testid="hamburger-menu-settings-link" role="link">
<form action="/sp/search" method="post" class="search-form-form" id="search" data-testid="search" role="search" aria-label="top search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q" data-testid="q" maxlength="2048" name="query" placeholder="Search privately" role="searchbox" spellcheck="false" title="Search" type="text" class="search-form-input" value="">
<div class="hide-promo css-2f320f" role="button" tabindex="0"><div role="button" tabindex="0" class="css-zhw45g"><div class="hide-promo-image-container css-1sx5uuz"><div class="hide-promo-image css-y54zji"></div></div><span class="hide-promo-text">Hide promotional messaging</span></div></div>
<div role="button" tabindex="0" class="css-zhw45g"><div class="hide-promo-image-container css-1sx5uuz"><div class="hide-promo-image css-y54zji"></div></div><span class="hide-promo-text">Hide promotional messaging</span></div>
<form action="/sp/search" method="post" class="search-form-form" id="search-btf" data-testid="search" role="search" aria-label="bottom search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q-btf" data-testid="q" maxlength="2048" name="query" placeholder="Start your search wi..." role="searchbox" spellcheck="false" title="Search" type="text" value="" ...>
<footer role="contentinfo" aria-label="footer" class="css-1h47swe eu3pp1u0">
Showing first 10 of 11 audited elements.
ARIA roles used must conform to valid values10 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
<div class="hamburger-button css-1g9wt7p" data-testid="hamburger-menu-toggle" role="button" aria-label="hamburger menu" tabindex="0"><i></i></div>
<button tabindex="-1" class="css-ocm99y" type="submit" data-testid="hamburger-menu-settings-link" role="link">
<form action="/sp/search" method="post" class="search-form-form" id="search" data-testid="search" role="search" aria-label="top search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q" data-testid="q" maxlength="2048" name="query" placeholder="Search privately" role="searchbox" spellcheck="false" title="Search" type="text" class="search-form-input" value="">
<div class="hide-promo css-2f320f" role="button" tabindex="0"><div role="button" tabindex="0" class="css-zhw45g"><div class="hide-promo-image-container css-1sx5uuz"><div class="hide-promo-image css-y54zji"></div></div><span class="hide-promo-text">Hide promotional messaging</span></div></div>
<div role="button" tabindex="0" class="css-zhw45g"><div class="hide-promo-image-container css-1sx5uuz"><div class="hide-promo-image css-y54zji"></div></div><span class="hide-promo-text">Hide promotional messaging</span></div>
<form action="/sp/search" method="post" class="search-form-form" id="search-btf" data-testid="search" role="search" aria-label="bottom search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q-btf" data-testid="q" maxlength="2048" name="query" placeholder="Start your search wi..." role="searchbox" spellcheck="false" title="Search" type="text" value="" ...>
<footer role="contentinfo" aria-label="footer" class="css-1h47swe eu3pp1u0">
<button tabindex="0" class="css-ocm99y" type="submit" role="link" title="Startpage home page">
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="ai-chat-banner-visible">
autocomplete attribute must be used correctly2 elements
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
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q" data-testid="q" maxlength="2048" name="query" placeholder="Search privately" role="searchbox" spellcheck="false" title="Search" type="text" class="search-form-input" value="">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q-btf" data-testid="q" maxlength="2048" name="query" placeholder="Start your search wi..." role="searchbox" spellcheck="false" title="Search" type="text" value="" ...>
Buttons must have discernible text4 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 tabindex="-1" class="css-ocm99y" type="submit" data-testid="hamburger-menu-settings-link" role="link">
<button class="search-btn" type="submit" aria-label="search button"></button>
<button class="search-btn" type="submit" aria-label="search button"></button>
<button tabindex="0" class="css-ocm99y" type="submit" role="link" title="Startpage home page">
Deprecated ARIA roles must not be used10 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
<div class="hamburger-button css-1g9wt7p" data-testid="hamburger-menu-toggle" role="button" aria-label="hamburger menu" tabindex="0"><i></i></div>
<button tabindex="-1" class="css-ocm99y" type="submit" data-testid="hamburger-menu-settings-link" role="link">
<form action="/sp/search" method="post" class="search-form-form" id="search" data-testid="search" role="search" aria-label="top search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q" data-testid="q" maxlength="2048" name="query" placeholder="Search privately" role="searchbox" spellcheck="false" title="Search" type="text" class="search-form-input" value="">
<div class="hide-promo css-2f320f" role="button" tabindex="0"><div role="button" tabindex="0" class="css-zhw45g"><div class="hide-promo-image-container css-1sx5uuz"><div class="hide-promo-image css-y54zji"></div></div><span class="hide-promo-text">Hide promotional messaging</span></div></div>
<div role="button" tabindex="0" class="css-zhw45g"><div class="hide-promo-image-container css-1sx5uuz"><div class="hide-promo-image css-y54zji"></div></div><span class="hide-promo-text">Hide promotional messaging</span></div>
<form action="/sp/search" method="post" class="search-form-form" id="search-btf" data-testid="search" role="search" aria-label="bottom search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q-btf" data-testid="q" maxlength="2048" name="query" placeholder="Start your search wi..." role="searchbox" spellcheck="false" title="Search" type="text" value="" ...>
<footer role="contentinfo" aria-label="footer" class="css-1h47swe eu3pp1u0">
<button tabindex="0" class="css-ocm99y" type="submit" role="link" title="Startpage home page">
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 lang="en">
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 role="contentinfo" aria-label="footer" class="css-1h47swe eu3pp1u0">
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 id="home" class="home">
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 lang="en">
Elements marked as presentational should be consistently ignored22 elements
Elements with role="none" or role="presentation" should be removed from the accessibility tree. Adding global ARIA attributes or making these elements focusable prevents their removal, leaving them accessible to screen readers when they should be ignored, creating unexpected and confusing behavior.
Audit Elements
<img class="no-script-hide css-1guhnn0" height="100%" width="100%" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-1guhnn0" height="100%" width="100%" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-1guhnn0" height="100%" width="100%" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-1iyuuc5" height="55px" width="55px" src="" alt="" loading="lazy" data-testid="test-image">
Showing first 10 of 22 audited elements.
Elements must meet minimum color contrast ratio thresholds32 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
<p class="startpage-hero-tagline css-1nkohvv">The world’s most private search engine.</p>
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q" data-testid="q" maxlength="2048" name="query" placeholder="Search privately" role="searchbox" spellcheck="false" title="Search" type="text" class="search-form-input" value="">
<h2>The world’s most private search engine.</h2>
<p>Startpage’s search engine and Anonymous View feature are free and simple ways to take control of your online privacy. We will never save or sell your search history.</p>
<h2>Quality search results in true privacy.</h2>
<p class="section-description">Startpage delivers Google search results via our proprietary personal data protection technology.</p>
<h3>Encrypted connection</h3>
<p>Your IP address is removed from all our global premise servers.</p>
<h3>Block price trackers</h3>
<p>We prevent 3rd parties from setting price trackers on you.</p>
Showing first 10 of 32 audited elements.
Elements must only use permitted ARIA attributes22 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
<div class="hamburger-button css-1g9wt7p" data-testid="hamburger-menu-toggle" role="button" aria-label="hamburger menu" tabindex="0"><i></i></div>
<form action="/do/settings" method="post" class="css-13cn4bc" aria-label="Settings">
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="hamburger-menu-brows..." title="" tabindex="0" class="home-cta css-16okzfa">
<form action="/sp/search" method="post" class="search-form-form" id="search" data-testid="search" role="search" aria-label="top search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q" data-testid="q" maxlength="2048" name="query" placeholder="Search privately" role="searchbox" spellcheck="false" title="Search" type="text" class="search-form-input" value="">
<button class="search-btn" type="submit" aria-label="search button"></button>
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="home-cta" title="" tabindex="0" class="home-cta css-zjntmh">
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="home-cta" title="" tabindex="0" class="home-cta css-usj27l">
<form action="/sp/search" method="post" class="search-form-form" id="search-btf" data-testid="search" role="search" aria-label="bottom search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q-btf" data-testid="q" maxlength="2048" name="query" placeholder="Start your search wi..." role="searchbox" spellcheck="false" title="Search" type="text" value="" ...>
Showing first 10 of 22 audited elements.
Elements must only use supported ARIA attributes22 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
<div class="hamburger-button css-1g9wt7p" data-testid="hamburger-menu-toggle" role="button" aria-label="hamburger menu" tabindex="0"><i></i></div>
<form action="/do/settings" method="post" class="css-13cn4bc" aria-label="Settings">
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="hamburger-menu-brows..." title="" tabindex="0" class="home-cta css-16okzfa">
<form action="/sp/search" method="post" class="search-form-form" id="search" data-testid="search" role="search" aria-label="top search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q" data-testid="q" maxlength="2048" name="query" placeholder="Search privately" role="searchbox" spellcheck="false" title="Search" type="text" class="search-form-input" value="">
<button class="search-btn" type="submit" aria-label="search button"></button>
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="home-cta" title="" tabindex="0" class="home-cta css-zjntmh">
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="home-cta" title="" tabindex="0" class="home-cta css-usj27l">
<form action="/sp/search" method="post" class="search-form-form" id="search-btf" data-testid="search" role="search" aria-label="bottom search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q-btf" data-testid="q" maxlength="2048" name="query" placeholder="Start your search wi..." role="searchbox" spellcheck="false" title="Search" type="text" value="" ...>
Showing first 10 of 22 audited elements.
Elements should not have tabindex greater than zero41 elements
Using tabindex values greater than 0 creates unexpected tab orders that disorient users. It makes elements appear to be skipped when users tab past them, requires setting tabindex on every element to maintain order, and forces all tabindex items to be visited before any normal elements, breaking natural navigation flow.
Audit Elements
<div class="hamburger-button css-1g9wt7p" data-testid="hamburger-menu-toggle" role="button" aria-label="hamburger menu" tabindex="0"><i></i></div>
<button tabindex="-1" class="css-ocm99y" type="submit" data-testid="hamburger-menu-settings-link" role="link">
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="hamburger-menu-brows..." title="" tabindex="0" class="home-cta css-16okzfa">
<div class="hide-promo css-2f320f" role="button" tabindex="0"><div role="button" tabindex="0" class="css-zhw45g"><div class="hide-promo-image-container css-1sx5uuz"><div class="hide-promo-image css-y54zji"></div></div><span class="hide-promo-text">Hide promotional messaging</span></div></div>
<div role="button" tabindex="0" class="css-zhw45g"><div class="hide-promo-image-container css-1sx5uuz"><div class="hide-promo-image css-y54zji"></div></div><span class="hide-promo-text">Hide promotional messaging</span></div>
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="home-cta" title="" tabindex="0" class="home-cta css-zjntmh">
<div tabindex="-1" class="css-zybtxx">
<div tabindex="-1" class="css-zybtxx">
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="home-cta" title="" tabindex="0" class="home-cta css-usj27l">
<div tabindex="-1" class="css-xiehbc">
Showing first 10 of 41 audited elements.
Form elements must have labels2 elements
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
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q" data-testid="q" maxlength="2048" name="query" placeholder="Search privately" role="searchbox" spellcheck="false" title="Search" type="text" class="search-form-input" value="">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q-btf" data-testid="q" maxlength="2048" name="query" placeholder="Start your search wi..." role="searchbox" spellcheck="false" title="Search" type="text" value="" ...>
Form elements should have a visible label2 elements
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
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q" data-testid="q" maxlength="2048" name="query" placeholder="Search privately" role="searchbox" spellcheck="false" title="Search" type="text" class="search-form-input" value="">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q-btf" data-testid="q" maxlength="2048" name="query" placeholder="Start your search wi..." role="searchbox" spellcheck="false" title="Search" type="text" value="" ...>
Form field must not have multiple label elements2 elements
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
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q" data-testid="q" maxlength="2048" name="query" placeholder="Search privately" role="searchbox" spellcheck="false" title="Search" type="text" class="search-form-input" value="">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q-btf" data-testid="q" maxlength="2048" name="query" placeholder="Start your search wi..." role="searchbox" spellcheck="false" title="Search" type="text" value="" ...>
Heading levels should only increase by one11 elements
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h2>The Internet without tracking.</h2>
<h2>The world’s most private search engine.</h2>
<h2>Quality search results in true privacy.</h2>
<h3>Encrypted connection</h3>
<h3>Block price trackers</h3>
<h3>Avoid retargeting ads</h3>
<h3>Browse anonymously</h3>
<h3>Receive unprofiled news</h3>
<h3>Prevent online profiling</h3>
<h2>Trusted by users worldwide.</h2>
Showing first 10 of 11 audited elements.
Headings should not be empty11 elements
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h2>The Internet without tracking.</h2>
<h2>The world’s most private search engine.</h2>
<h2>Quality search results in true privacy.</h2>
<h3>Encrypted connection</h3>
<h3>Block price trackers</h3>
<h3>Avoid retargeting ads</h3>
<h3>Browse anonymously</h3>
<h3>Receive unprofiled news</h3>
<h3>Prevent online profiling</h3>
<h2>Trusted by users worldwide.</h2>
Showing first 10 of 11 audited elements.
Images must have alternative text22 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 class="no-script-hide css-1guhnn0" height="100%" width="100%" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-1guhnn0" height="100%" width="100%" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-bb974q" height="128px" width="128px" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-1guhnn0" height="100%" width="100%" src="" alt="" loading="lazy" data-testid="test-image">
<img class="no-script-hide css-1iyuuc5" height="55px" width="55px" src="" alt="" loading="lazy" data-testid="test-image">
Showing first 10 of 22 audited elements.
Inline text spacing must be adjustable with custom stylesheets1 element
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 class="theme-checker" style="color:#f2f3ff"></div>
Interactive controls must not be nested4 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
<div class="hamburger-button css-1g9wt7p" data-testid="hamburger-menu-toggle" role="button" aria-label="hamburger menu" tabindex="0"><i></i></div>
<button class="search-btn" type="submit" aria-label="search button"></button>
<div role="button" tabindex="0" class="css-zhw45g"><div class="hide-promo-image-container css-1sx5uuz"><div class="hide-promo-image css-y54zji"></div></div><span class="hide-promo-text">Hide promotional messaging</span></div>
<button class="search-btn" type="submit" aria-label="search button"></button>
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination6 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 id="home" class="home">
<form action="/do/settings" method="post" class="css-13cn4bc" aria-label="Settings">
<form action="/sp/search" method="post" class="search-form-form" id="search" data-testid="search" role="search" aria-label="top search bar">
<form action="/sp/search" method="post" class="search-form-form" id="search-btf" data-testid="search" role="search" aria-label="bottom search bar">
<footer role="contentinfo" aria-label="footer" class="css-1h47swe eu3pp1u0">
<form action="/" method="post" class="css-0" aria-label="Startpage home page">
Links must have discernible text12 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 href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="hamburger-menu-brows..." title="" tabindex="0" class="home-cta css-16okzfa">
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="home-cta" title="" tabindex="0" class="home-cta css-zjntmh">
<a href="https://chrome.googl..." rel="noopener nofollow" target="_blank" aria-label="Add Startpage extens..." aria-hidden="false" data-testid="home-cta" title="" tabindex="0" class="home-cta css-usj27l">
<a href="https://www.startpage.com/privacy-please/" rel="noopener nofollow" target="_self" aria-label="Privacy Please Blog" aria-hidden="false" data-testid="" title="" tabindex="0" class="css-kztwvx">
<a href="https://www.startpage.com/en/privacy-policy?t=device" rel="noopener nofollow" target="_blank" aria-label="Privacy Policy" aria-hidden="false" data-testid="" title="" tabindex="0" class="css-kztwvx"><span class="link-text">Privacy Policy</span></a>
<a href="https://www.startpage.com/en/about-us?t=device" rel="noopener nofollow" target="_blank" aria-label="About Us" aria-hidden="false" data-testid="" title="" tabindex="0" class="css-kztwvx"><span class="link-text">About Us</span></a>
<a href="https://www.startpage.com/privacy-please/press/" rel="noopener nofollow" target="_blank" aria-label="Press" aria-hidden="false" data-testid="" title="" tabindex="0" class="css-kztwvx"><span class="link-text">Press</span></a>
<a href="https://twitter.com/startpage" rel="noopener nofollow" target="_self" aria-label="twitter" aria-hidden="false" data-testid="" title="" tabindex="0" class="css-kztwvx">
<a href="https://www.reddit.com/r/StartpageSearch/" rel="noopener nofollow" target="_self" aria-label="reddit" aria-hidden="false" data-testid="" title="" tabindex="0" class="css-kztwvx">
<a href="https://www.instagram.com/startpage/" rel="noopener nofollow" target="_self" aria-label="instagram" aria-hidden="false" data-testid="" title="" tabindex="0" class="css-kztwvx">
Showing first 10 of 12 audited elements.
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 id="home" class="home">
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 lang="en">
Required ARIA attributes must be provided10 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
<div class="hamburger-button css-1g9wt7p" data-testid="hamburger-menu-toggle" role="button" aria-label="hamburger menu" tabindex="0"><i></i></div>
<button tabindex="-1" class="css-ocm99y" type="submit" data-testid="hamburger-menu-settings-link" role="link">
<form action="/sp/search" method="post" class="search-form-form" id="search" data-testid="search" role="search" aria-label="top search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q" data-testid="q" maxlength="2048" name="query" placeholder="Search privately" role="searchbox" spellcheck="false" title="Search" type="text" class="search-form-input" value="">
<div class="hide-promo css-2f320f" role="button" tabindex="0"><div role="button" tabindex="0" class="css-zhw45g"><div class="hide-promo-image-container css-1sx5uuz"><div class="hide-promo-image css-y54zji"></div></div><span class="hide-promo-text">Hide promotional messaging</span></div></div>
<div role="button" tabindex="0" class="css-zhw45g"><div class="hide-promo-image-container css-1sx5uuz"><div class="hide-promo-image css-y54zji"></div></div><span class="hide-promo-text">Hide promotional messaging</span></div>
<form action="/sp/search" method="post" class="search-form-form" id="search-btf" data-testid="search" role="search" aria-label="bottom search bar">
<input aria-haspopup="false" aria-label="search" autocapitalize="off" autocomplete="off" autocorrect="off" dir="ltr" id="q-btf" data-testid="q" maxlength="2048" name="query" placeholder="Start your search wi..." role="searchbox" spellcheck="false" title="Search" type="text" value="" ...>
<footer role="contentinfo" aria-label="footer" class="css-1h47swe eu3pp1u0">
<button tabindex="0" class="css-ocm99y" type="submit" role="link" title="Startpage home page">
Scrollable region must have keyboard access1 element
Scrollable regions must contain focusable elements or be focusable themselves to enable keyboard navigation. Without keyboard access, users cannot scroll to view content that extends beyond the visible area, making that content completely inaccessible to keyboard-only users.
Audit Elements
<html lang="en">
Users should be able to zoom and scale the text up to 500%1 element
The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.
Audit Elements
<meta name="viewport" content="width=device-width,initial-scale=1.0">
Zooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Audit Elements
<meta name="viewport" content="width=device-width,initial-scale=1.0">