Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 2 REVIEW 4 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

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

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title OHSU interpreter services ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 5 fail WCAG AA

REVIEW

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

15 pass 5 fail WCAG AA 3 pass AA only

a OHSU

2.82:1

#000000

#405485

needs 4.5:1 (normal text)

16px · top of page (header area)

a About

4.11:1

#000000

#616E8B

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a News

1.53:1

#000000

#242F33

needs 4.5:1 (normal text)

16px · above the fold

a OHSU Foundation

1.68:1

#000000

#2B3636

needs 4.5:1 (normal text)

16px · above the fold

a OHSU Facts

1.56:1

#000000

#2A3030

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 Built for the future…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 OHSU News	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Work at OHSU	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 'One bad day in the …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 OHSU's new Vista Pav…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Patients who lose in…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Give to OHSU	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title OHSU \| Healing Begin…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main navigat…	10.92:1	4.5:1	#000000	#B3BBCE	Pass
a OHSU	2.82:1	4.5:1	#000000	#405485	Fail
a About	4.11:1	4.5:1	#000000	#616E8B	Fail
a About OHSU	4.72:1	4.5:1	#000000	#6F7888	Pass
a Jobs	4.93:1	4.5:1	#000000	#737B8B	Pass
a Contact	4.92:1	4.5:1	#000000	#767A89	Pass
a News	1.53:1	4.5:1	#000000	#242F33	Fail
a OHSU Foundation	1.68:1	4.5:1	#000000	#2B3636	Fail
a OHSU Facts	1.56:1	4.5:1	#000000	#2A3030	Fail
a OHSU Vision	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Initiatives	21.00:1	4.5: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.

Landmark Structure

14 landmarks

PASS

14 landmarks

<main> landmark present

9 <nav> landmark(s) found

8 of 9 <nav> elements are unlabeled

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

Skip navigation link present

Page Structure — as a screen reader sees it

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

Heading Hierarchy

18 headings, 1 skip(s)

PASS

18 headings, 1 skip(s)

Single H1 present

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

1 hidden heading(s) (aria-hidden)

H2 OHSU
H1 Built for the future of cancer care
H2 Patients
H2 Students
H2 Research
H3 Work at OHSU
H2 OHSU News
H3 'One bad day in the NICU' can affect preemie brain long-term
H3 OHSU's new Vista Pavilion provides a new approach to cancer care
H3 Patients who lose insurance have harder time with diabetes
H3 Give to OHSU
H5 About OHSU skipped
H5 Patient Resources
H5 Research
H5 Academics
H5 For Employees
H5 Inclusive Care and Access
H5 Connect with OHSU on social media hidden

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 3 controls have issues

PASS

1 of 3 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit" id="edit-submit">

2 control(s) properly labeled

3 controls

2 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#search--trigger	checkbox	Toggle search form	aria-label
#edit-keys	text	Search OHSU	aria-label
#edit-submit	submit	(none)	none

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

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

Link & Button Quality

1 issue(s) across 154 links and 1 buttons

PASS

1 issue(s) across 154 links and 1 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#main-content

153 link(s) with descriptive text

154 links

1 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label

154 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#main-content

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /sites/default/files/css/css_00an8MLdNFH_m4gTiWW9kVrg5QUMG1g4nt-XUvEudAI.css?delta=4&language=en&theme=ohsu_digs&include=eJx1jksKQyEQBC8keiQZtaPC-MHWhNw-8EJINtk01bWqIKzRBSFMuLCBlAyaKIqeZLkP2F3QYEbh8almutvomz8_6wiiZsqSvGQWurTOFLVfY0-fJ2hlQTKErFi8zOrl7BFHm4oN98cbPrnR3rH3igfdtbaNdBQv_aFPAg

Print Stylesheet ✓ Print Optimized

Print stylesheet /sites/default/files/css/css_00an8MLdNFH_m4gTiWW9kVrg5QUMG1g4nt-XUvEudAI.css?delta=4&language=en&theme=ohsu_digs&include=eJx1jksKQyEQBC8keiQZtaPC-MHWhNw-8EJINtk01bWqIKzRBSFMuLCBlAyaKIqeZLkP2F3QYEbh8almutvomz8_6wiiZsqSvGQWurTOFLVfY0-fJ2hlQTKErFi8zOrl7BFHm4oN98cbPrnR3rH3igfdtbaNdBQv_aFPAg ✓Inline @media print Not detected ✗

A+

Lighthouse Accessibility Audits

Score 98/100 — 1 failing, 24 passed

PASS

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
About OHSU `nav.site-footer__nav > div.footer-nav-column > div#block-footermenu1-2 > h5.footer-nav-header`

These are opportunities to improve keyboard navigation in your application.

○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

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○Buttons have an accessible name

○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

○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

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

○Elements with visible text labels have matching accessible names.

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