Startpage startpage.com
Accessibility score
League position
1stof 9
Issues found
6
Audits passed
21
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousARIA progressbar nodes must have an accessible name1 element
Screen reader users cannot determine what a role="progressbar" element is tracking without an accessible name. The name tells users what process or task is progressing.
Failing Elements
<div id="progress" role="progressbar" aria-labelledby="sp-message" aria-valuenow="91.26225987630951" style="display: inline-block;">
<div class="bar-inner" style="width: 91.2623%;"></div>
</div>Fix any of the following:
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
SeriousDocuments 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.
Failing Elements
<html lang="en">
Fix any of the following:
- Document does not have a non-empty <title> element
SeriousLinks must have discernible text1 element
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.
Failing Elements
<a href="https://www.startpage.com">
Fix all of the following:
- Element is in tab order and does not have accessible text
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
ModerateDocument 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.
Failing Elements
<html lang="en">
Fix all of the following:
- Document does not have a main 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
ModerateAll page content should be contained by landmarks3 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.
Failing Elements
<div class="sp-message">Verifying your request...</div>
Fix any of the following:
- Some page content is not contained by landmarks
<div id="progress" role="progressbar" aria-labelledby="sp-message" aria-valuenow="91.26225987630951" style="display: inline-block;">
<div class="bar-inner" style="width: 91.2623%;"></div>
</div>Fix any of the following:
- Some page content is not contained by landmarks
<p id="status">Calculating...<br>Difficulty: 4, Speed: 32.549kH/s</p>
Fix any of the following:
- Some page content is not contained by landmarks
Passed audits21 across 1 page
<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 landmarks7 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 class="sp-wrap">
<a href="https://www.startpage.com">
<div class="bar-inner" style="width: 91.2623%;"></div>
<div class="sp-body">
<div class="centered-div">
Showing first 5 of 7 audited elements.
ARIA attributes must be used as specified for the element's role1 element
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 id="progress" role="progressbar" aria-labelledby="sp-message" aria-valuenow="91.26225987630951" style="display: inline-block;">
<div class="bar-inner" style="width: 91.2623%;"></div>
</div>ARIA attributes must conform to valid names1 element
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 id="progress" role="progressbar" aria-labelledby="sp-message" aria-valuenow="91.26225987630951" style="display: inline-block;">
<div class="bar-inner" style="width: 91.2623%;"></div>
</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 class="sp-logo sp-only-light" fill="none" height="47" viewBox="0 0 240 53" width="213" xmlns="http://www.w3.org/2000/svg" aria-hidden="true">
<svg class="sp-logo sp-only-dark" fill="none" height="47" viewBox="0 0 240 53" width="213" xmlns="http://www.w3.org/2000/svg" aria-hidden="true">
ARIA role should be appropriate for the element2 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 id="progress" role="progressbar" aria-labelledby="sp-message" aria-valuenow="91.26225987630951" style="display: inline-block;">
<div class="bar-inner" style="width: 91.2623%;"></div>
</div><div id="progress" role="progressbar" aria-labelledby="status"><div class="bar-inner"></div></div>
ARIA roles used must conform to valid values1 element
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 id="progress" role="progressbar" aria-labelledby="sp-message" aria-valuenow="91.26225987630951" style="display: inline-block;">
<div class="bar-inner" style="width: 91.2623%;"></div>
</div>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>
Content must reflow without two-dimensional scrolling1 element
People who zoom to 400% or use a narrow viewport must be able to scroll in one direction only. A layout that still requires horizontal scrolling at 320 CSS pixels forces magnified readers to pan left and right line by line, which makes the page close to unusable.
Audit Elements
<div class="css-1tgrcud" style="overflow: hidden; transform: translateX(-6px);">
Deprecated ARIA roles must not be used1 element
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 id="progress" role="progressbar" aria-labelledby="sp-message" aria-valuenow="91.26225987630951" style="display: inline-block;">
<div class="bar-inner" style="width: 91.2623%;"></div>
</div>Elements must meet minimum color contrast ratio thresholds1 element
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
<div class="sp-message">Verifying your request...</div>
Elements must only use permitted ARIA attributes1 element
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 id="progress" role="progressbar" aria-labelledby="sp-message" aria-valuenow="91.26225987630951" style="display: inline-block;">
<div class="bar-inner" style="width: 91.2623%;"></div>
</div>Elements must only use supported ARIA attributes1 element
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 id="progress" role="progressbar" aria-labelledby="sp-message" aria-valuenow="91.26225987630951" style="display: inline-block;">
<div class="bar-inner" style="width: 91.2623%;"></div>
</div>IDs used in ARIA and labels must be unique1 element
Duplicate IDs break the accessibility of ARIA elements, form labels, and table headers. When IDs are duplicated, assistive technologies and scripts only reference the first instance, causing subsequent elements with the same ID to be ignored or incorrectly associated.
Audit Elements
<p id="status">Calculating...<br>Difficulty: 4, Speed: 32.549kH/s</p>
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 id="progress" role="progressbar" aria-labelledby="sp-message" aria-valuenow="91.26225987630951" style="display: inline-block;">
<div class="bar-inner" style="width: 91.2623%;"></div>
</div><div class="bar-inner" style="width: 91.2623%;"></div>
Interactive 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.
Audit Elements
<div id="progress" role="progressbar" aria-labelledby="sp-message" aria-valuenow="91.26225987630951" style="display: inline-block;">
<div class="bar-inner" style="width: 91.2623%;"></div>
</div>Required ARIA attributes must be provided1 element
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 id="progress" role="progressbar" aria-labelledby="sp-message" aria-valuenow="91.26225987630951" style="display: inline-block;">
<div class="bar-inner" style="width: 91.2623%;"></div>
</div>Text must remain readable when spacing is increased0 elements
People with low vision and dyslexia increase line height, letter spacing, word spacing, and paragraph spacing so they can read. Fixed-height boxes and overflow: hidden containers clip or overlap that text, which is a loss of content under WCAG 1.4.12.
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">
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">
How does your site stack up against Startpage?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Search Engine