Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 REVIEW 5 FIX

404 Error Page

Action

HTTP 403, bare page

FIX

HTTP 403, bare page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

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 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #f4f4f4 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA 2 pass AA only

h1 Transforming your care

1.50:1

#000000

#002B5C

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Research

1.50:1

#000000

#002B5C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Education

1.50:1

#000000

#002B5C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Find diseases & conditions by first lett…

1.50:1

#000000

#002B5C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Healing starts here

1.50:1

#000000

#002B5C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 World-class care for global patients

1.50:1

#000000

#002B5C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Locations

1.50:1

#000000

#002B5C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Featured care areas

1.50:1

#000000

#002B5C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 There’s still time!

1.50:1

#000000

#002B5C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Follow Mayo Clinic

1.50:1

#000000

#002B5C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get the Mayo Clinic app

1.50:1

#000000

#002B5C

needs 3.0:1 (large text)

24px · bottom of viewport

span Request appointment

2.68:1

#000000

#56514D

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span Register/Log in

1.80:1

#000000

#34393D

needs 4.5:1 (normal text)

16px · top of page (header area)

span Search

1.96:1

#000000

#3D3E40

needs 4.5:1 (normal text)

16px · above the fold

span Menu

2.14:1

#000000

#464343

needs 4.5:1 (normal text)

16px · above the fold

span Request appointment

2.72:1

#000000

#5D5142

needs 4.5:1 (normal text)

16px · above the fold

span Donate

2.27:1

#000000

#534534

needs 4.5:1 (normal text)

16px · above the fold

span Diseases & conditions

1.18:1

#000000

#21150D

needs 4.5:1 (normal text)

16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Transforming your ca…	1.50:1	3.0:1	#000000	#002B5C	Fail
h2 Research	1.50:1	3.0:1	#000000	#002B5C	Fail
h2 Education	1.50:1	3.0:1	#000000	#002B5C	Fail
h2 Find diseases & cond…	1.50:1	3.0:1	#000000	#002B5C	Fail
h2 Healing starts here	1.50:1	3.0:1	#000000	#002B5C	Fail
h2 World-class care for…	1.50:1	3.0:1	#000000	#002B5C	Fail
h2 Locations	1.50:1	3.0:1	#000000	#002B5C	Fail
h2 Featured care areas	1.50:1	3.0:1	#000000	#002B5C	Fail
h2 There’s still time…	1.50:1	3.0:1	#000000	#002B5C	Fail
h2 Follow Mayo Clinic	1.50:1	3.0:1	#000000	#002B5C	Fail
h2 Get the Mayo Clinic …	1.50:1	3.0:1	#000000	#002B5C	Fail
title The world's best hos…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
a Skip to content	5.24:1	4.5:1	#000000	#7F7F7F	Pass
span Request appointment	2.68:1	4.5:1	#000000	#56514D	Fail
span Register/Log in	1.80:1	4.5:1	#000000	#34393D	Fail
span Search	1.96:1	4.5:1	#000000	#3D3E40	Fail
span Menu	2.14:1	4.5:1	#000000	#464343	Fail
span Request appointment	2.72:1	4.5:1	#000000	#5D5142	Fail
span Donate	2.27:1	4.5:1	#000000	#534534	Fail
span Diseases & condition…	1.18:1	4.5:1	#000000	#21150D	Fail

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+

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

5 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

23 headings

PASS

23 headings

Single H1 present

H2 Research
H2 Education
H1 Transforming your care
H2 Find diseases & conditions by first letter
H2 Healing starts here
H2 World-class care for global patients
H2 Locations
H3 Mayo Clinic in Arizona
H3 Mayo Clinic in Florida
H3 Mayo Clinic in Minnesota
H3 Mayo Clinic Health System
H3 Mayo Clinic Healthcare
H2 Featured care areas
H2 There’s still time!
H2 About Mayo Clinic
H2 Medical Professionals
H2 Businesses
H2 Students
H2 Researchers
H2 International Patients
H2 Charitable Care & Financial Assistance
H2 Follow Mayo Clinic
H2 Get the Mayo Clinic app

A+

Alt Text Quality

All 13 images OK

PASS

All 13 images OK

5 decorative image(s) correctly marked

8 image(s) with good alt text

13 images 8 good alt text 5 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-input-globalsearch-773693aac3	text	Search for a disease or condition . Type 3 or more letters to display suggested search options.	for/id
#search-input-globalsearch-c538ac7522	text	Search diseases & conditions . Type 3 or more letters to display suggested search options.	for/id

Link & Button Quality

1 issue(s) across 175 links and 15 buttons

PASS

1 issue(s) across 175 links and 15 buttons

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button[data-testid="cmp-button"]

175 link(s) with descriptive text

175 links

0 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
<button>	(empty)	empty	Add button text or aria-label

189 links and buttons have descriptive text

Icon-only buttons need an aria-label so screen readers can announce them.

button[data-testid="cmp-button"]

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 30 passed

PASS

100

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.

○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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Elements with the `role=text` attribute do not have focusable descendents.

●Background and foreground colors have a sufficient contrast ratio

●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

●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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[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

○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.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○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.