Skip to content
https://uber.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 429, bare page
FIX
HTTP 429, bare page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 429 ✗Page Title 429 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Favicon & Branding
Action
10 icon(s) detected
REVIEW
10 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 84/100 — 6 failing, 27 passed
REVIEW
84

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
This website uses third party cookies to serve you relevant ads and provide per… body > div#privacy-cookie-banners-root

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Date div.css-cvpIEi > div.css-cYTjpz > label > p.css-hljex
Time div.css-cvpIEi > div.css-cYTjpz > label > p.css-hljex

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Log in Sign up nav.css-EuaFB > div.css-jpTJNR > div.css-bjVkCt > ul.css-jaByka

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Log in div.css-bjVkCt > ul.css-jaByka > div.logged-out-style-wrapper > li.css-iJiqqk
Sign up div.css-bjVkCt > ul.css-jaByka > div.logged-out-style-wrapper > li.css-dmqvLf

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Visit Help Center div.css-bVFrLX > div.css-rjIkq > div > a.css-iBZTkJ

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Change city div.css-dgZOOc > div.css-bYqxpw > div.css-gjrQew > button.css-hVaYbi
Visit Help Center div.css-bVFrLX > div.css-rjIkq > div > a.css-iBZTkJ
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A
Heading Hierarchy
56 headings
PASS
56 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Go anywhere with Uber
  • H1 Go anywhere with Uber duplicate H1
  • H1 Go anywhere with Uber duplicate H1
  • H2 Suggestions
  • H2 Suggestions
  • H2 Suggestions
  • H2 Log in to see your account details
  • H2 Planning your next getaway?
  • H2 Drive when you want, make what you need
  • H2 The Uber you know, reimagined for business
  • H2 Safety, simplified
  • H2 Safety, simplified
  • H2 Safety, simplified
  • H2 Use your skills to earn anytime, from anywhere
  • H2 It’s easier in the apps
  • H2 Download the Uber app
  • H2 Download the Driver app
  • H2 It’s easier in the apps
  • H2 Download the Uber app
  • H2 Download the Driver app
  • H2 Select your preferred language
  • H3 Earn
  • H3 About
  • H2 Select your preferred language
  • H2 Ride
  • H2 Earn
  • H2 Uber Eats
  • H2 Business
  • H2 Sign in to drive & deliver
  • H2 Sign in to ride
  • H2 Sign in to order delivery with Uber Eats
  • H2 Sign in to your Uber for Business account
  • H2 Drive & deliver
  • H2 Ride
  • H2 Uber Eats
  • H2 Uber for Business
  • H2 Manage account
  • H2 Sign out
  • H2 Select your preferred language
  • H3 Earn
  • H3 About
  • H2 Select your preferred language
  • H2 Ride
  • H2 Earn
  • H2 Uber Eats
  • H2 Business
  • H2 Sign in to drive & deliver
  • H2 Sign in to ride
  • H2 Sign in to order delivery with Uber Eats
  • H2 Sign in to your Uber for Business account
  • H2 Drive & deliver
  • H2 Ride
  • H2 Uber Eats
  • H2 Uber for Business
  • H2 Manage account
  • H2 Sign out

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Alt Text Quality
All 34 images OK
PASS
All 34 images OK
Info::
16 decorative image(s) correctly marked
Info::
18 image(s) with good alt text
34 images 18 good alt text 16 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 12 controls labeled
PASS
All 12 controls labeled
Info::
12 control(s) properly labeled
12 controls
12 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#rv-pudo-select-0.6g7hqkel04uinputPickup location needs to be filled inaria-label
#rv-pudo-select-0.0nqep2yhhnhinputDropoff location needs to be filled inaria-label
#rv-pudo-select-0.hboai9p1clinputPickup location needs to be filled inaria-label
#rv-pudo-select-0.7c515r10hvrinputDropoff location needs to be filled inaria-label
#rv-pudo-select-0.4dpe6nxdmwinputPickup location needs to be filled inaria-label
#rv-pudo-select-0.hhul4y14hoinputDropoff location needs to be filled inaria-label
#rv-pudo-select-0.k3liw0hbpx8inputPickup location needs to be filled inaria-label
#rv-pudo-select-0.xxbuurrdwi7inputDropoff location needs to be filled inaria-label
#rv-pudo-select-0.nmem8c8w33inputPickup location needs to be filled inaria-label
#rv-pudo-select-0.fecqym1smhfinputDropoff location needs to be filled inaria-label
#rv-pudo-select-0.b0rggngikqfinputPickup location needs to be filled inaria-label
#rv-pudo-select-0.udbm4qempn9inputDropoff location needs to be filled inaria-label
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Go anywhere with Ube…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Go anywhere with Ube…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Go anywhere with Ube…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Suggestions21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Suggestions21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Suggestions21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Log in to see your a…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Planning your next g…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Drive when you want,…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The Uber you know, r…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Safety, simplified21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Safety, simplified21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Safety, simplified21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Use your skills to e…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 It’s easier in the…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Download the Uber ap…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Download the Driver …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 It’s easier in the…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Download the Uber ap…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Download the Driver …21.00:13.0:1
#000000
#FFFFFF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback