Skip to content
https://uclahealth.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
3
REVIEW
6
PASS
4
INFO
0
Checks
13
4 PASS 6 REVIEW 3 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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::
7 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 7 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Heading Hierarchy
40 headings
REVIEW
40 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Achieving the exceptional doesn’t just happen
  • H2 Your best care is closer than you think
  • H2 Primary Care
  • H2 Immediate Care
  • H2 Locations
  • H2 Find a Doctor
  • H2 Medical Services
  • H2 Clinical Trials
  • H2 UCLA Health top-ranked in annual assessment of hospital patient care
  • H2 Orthopedic and sports medicine care from pros
  • H2 Why choose UCLA Health for medical care?
  • H3 Cancer Care
  • H3 Neuroscience
  • H3 Transplant
  • H3 Orthopedics & Sports Medicine
  • H3 Heart & Vascular Care
  • H3 Head & Neck Surgery
  • H3 Children's Care
  • H3 Women's Health
  • H3 Psychiatry
  • H2 Latest News
  • H3 UCLA medical students celebrate Match Day on their path to becoming practicing doctors
  • H3 Federal housing assistance may lead to improved two-year survival among older people with prostate cancer
  • H3 Cellular neighborhoods inside tumors may predict which patients with melanoma benefit from combination immunotherapy
  • H3 Women’s Cancer Survivors Conference blends community, education
  • H3 Dr. Aditya Bardia elected to American Society for Clinical Investigation
  • H2 Stay in Touch
  • H3 CONNECT WITH US
  • H3 CONNECT WITH US
  • H3 CONNECT WITH US
  • H3 FIND CARE
  • H3 FIND CARE
  • H3 FIND CARE
  • H3 PATIENT RESOURCES
  • H3 PATIENT RESOURCES
  • H3 PATIENT RESOURCES
  • H3 DISCOVER UCLA HEALTH
  • H3 DISCOVER UCLA HEALTH
  • H3 DISCOVER UCLA HEALTH
  • H2 Policy links (footer)

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C
Form Accessibility
Action
5 of 7 controls have issues
REVIEW
5 of 7 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">
Info::
2 control(s) properly labeled
7 controls
2 labeled
0 placeholder only
5 unlabeled
ControlTypeLabelMethod
selectselectWidget de idiomas del Traductoraria-label
#edit-s-uclahealth-general-search-modal-formtextSearchfor/id
#goog-gt-votingInputSrcLangtext(none)none
#goog-gt-votingInputTrgLangtext(none)none
#goog-gt-votingInputSrcTexttext(none)none
#goog-gt-votingInputTrgTexttext(none)none
#goog-gt-votingInputVotetext(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title We Can't Find This Page | UCLA Health ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: UCLA Health
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name UCLA Health ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name UCLA Health Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
A+
Landmark Structure
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "block-explore-links-header-menu" MAIN CONTENTINFO footer
A+
Alt Text Quality
All 11 images OK
PASS
All 11 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
11 images 9 good alt text 1 decorative
IssueCount
too long1 image(s)
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
h2 Achieving the except…19.09:13.0:1
#000000
#F6F4EE
Pass
h2 Your best care is cl…19.09:13.0:1
#000000
#F6F4EE
Pass
h2 Primary Care19.09:13.0:1
#000000
#F6F4EE
Pass
h2 Immediate Care19.09:13.0:1
#000000
#F6F4EE
Pass
h2 Locations19.09:13.0:1
#000000
#F6F4EE
Pass
h2 Find a Doctor19.09:13.0:1
#000000
#F6F4EE
Pass
h2 Medical Services19.09:13.0:1
#000000
#F6F4EE
Pass
h2 Clinical Trials19.09:13.0:1
#000000
#F6F4EE
Pass
h2 UCLA Health top-rank…19.09:13.0:1
#000000
#F6F4EE
Pass
h2 Orthopedic and sport…19.09:13.0:1
#000000
#F6F4EE
Pass
h2 Why choose UCLA Heal…19.09:13.0:1
#000000
#F6F4EE
Pass
h2 Latest News19.09:13.0:1
#000000
#F6F4EE
Pass
h2 Stay in Touch19.09:13.0:1
#000000
#F6F4EE
Pass
h2 Policy links (footer…19.09:13.0:1
#000000
#F6F4EE
Pass
h3 Cancer Care19.09:13.0:1
#000000
#F6F4EE
Pass
h3 Neuroscience19.09:13.0:1
#000000
#F6F4EE
Pass
h3 Transplant19.09:13.0:1
#000000
#F6F4EE
Pass
h3 Orthopedics & Sports…19.09:13.0:1
#000000
#F6F4EE
Pass
h3 Heart & Vascular Car…19.09:13.0:1
#000000
#F6F4EE
Pass
h3 Head & Neck Surgery19.09:13.0:1
#000000
#F6F4EE
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.

A+
Lighthouse Accessibility Audits
Score 95/100 — 1 failing, 26 passed
PASS
95

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.relative > div.max-w-screen-xl > div.flex > button.block div.relative > div.max-w-screen-xl > div.flex > button.block

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○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
●Image elements have `[alt]` attributes
●`[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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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
○`<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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○`[lang]` attributes have a valid value
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback