Skip to content
https://pdx.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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 ✗
C
Navigation UX
Action
2 navigation pattern(s)
REVIEW
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA 2 pass AA only
a Student
2.14:1
#000000
on
#38491E
needs 4.5:1 (normal text)
16px · above the fold
a Faculty / Staff
2.37:1
#000000
on
#454E24
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

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)
ElementRatioRequiredFGBGResult
h1 Homepage21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Go beyond the classr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Upcoming Events21.00:13.0:1
#000000
#FFFFFF
Pass
h2 News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 PSU social buttons21.00:13.0:1
#000000
#FFFFFF
Pass
title Homepage | Portland …21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main content21.00:14.5:1
#000000
#FFFFFF
Pass
label Search10.35:14.5:1
#000000
#B7B6B2
Pass
a Apply10.42:14.5:1
#000000
#B6B7B4
Pass
a Visit Campus10.40:14.5:1
#000000
#B6B7B1
Pass
a Request Info8.62:14.5:1
#000000
#A8A69F
Pass
a Give10.37:14.5:1
#000000
#B5B6BB
Pass
a myPSU10.67:14.5:1
#000000
#B9B9B5
Pass
button I am a5.39:14.5:1
#000000
#8C8066
Pass
a Alumni5.09:14.5:1
#000000
#78824B
Pass
a Student2.14:14.5:1
#000000
#38491E
Fail
a Faculty / Staff2.37:14.5:1
#000000
#454E24
Fail
a First Generation Stu…14.20:14.5:1
#000000
#DED3C2
Pass
a Parent21.00:14.5:1
#000000
#FFFFFF
Pass
a Padre21.00:14.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.

A+
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Website main navigation bar" SEARCH MAIN CONTENTINFO footer
A+
Heading Hierarchy
26 headings
PASS
26 headings
Info::
Single H1 present
  • H1 Homepage
  • H2 Go beyond the classroom
  • H3 Our Urban Campus →
  • H3 Big Possibilities. Low Tuition. →
  • H3 Apply to PSU →
  • H3 Go for Graduate School →
  • H2 MOST AFFORDABLE PUBLIC RESEARCH UNIVERSITY IN OREGON
  • H2 MOST DIVERSERESEARCH UNIVERSITYIN OREGON
  • H2 TOP 10BEST LGBTQ-FRIENDLYCOLLEGES
  • H2 Featured content
  • H3 Next Stop PSU: Your Path to Transfer Success
  • H4 Get personalized support to navigate your journey from PCC to PSU
  • H2 Upcoming Events
  • H3 Sociohydrology for Water Just Futures | Joint OSU-PSU-USGS Water, People, and Society Seminar
  • H3 Transfer Student Climb Night
  • H3 Women's+ Community Sports Hour
  • H3 Show & Tell Design Lecture Series presents Nishat Akhtar
  • H2 News
  • H3 PSU Welcomes Portland Fire WNBA Training Camp to Viking Pavilion
  • H3 PSU Awarded $1 Million Grant to Expand Semiconductor Career Pathways
  • H3 Unhoused People Seek Permanent Housing, Face Financial Barriers
  • H2 Contact PSU Contact PSU
  • H2 Legal Legal
  • H2 Learn More Learn More
  • H2 Support Support
  • H2 PSU social buttons
A+
Alt Text Quality
All 22 images OK
PASS
All 22 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
8 decorative image(s) correctly marked
Info::
13 image(s) with good alt text
22 images 13 good alt text 8 decorative
IssueCount
too long1 image(s)
A
Form Accessibility
1 of 7 controls have issues
PASS
1 of 7 controls have issues
Critical::
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-search">
Info::
6 control(s) properly labeled
7 controls
6 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#edit-keys--2searchSearch PDX.eduaria-label
#edit-submit--2submitSearcharia-label
#edit-keys-7searchSearch PDX.eduaria-label
#edit-submit-8submitSearcharia-label
#edit-keyssearchSearchfor/id
#edit-submitsubmitSearcharia-label
#edit-submit-searchsubmit(none)none

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

<input type="submit" id="edit-submit-search">

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

A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | Portland State University ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 26 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.

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
ADD TO MY CALENDAR div.upcoming_event_horizontal__content_outer > div.upcoming_event_horizontal__add_calendar > span.addtocalendar > a.atcb-link
ADD TO MY CALENDAR div.upcoming_event_horizontal__content_outer > div.upcoming_event_horizontal__add_calendar > span.addtocalendar > a.atcb-link
ADD TO MY CALENDAR div.upcoming_event_horizontal__content_outer > div.upcoming_event_horizontal__add_calendar > span.addtocalendar > a.atcb-link
ADD TO MY CALENDAR div.upcoming_event_horizontal__content_outer > div.upcoming_event_horizontal__add_calendar > span.addtocalendar > a.atcb-link
○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
●`[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 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
○`[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
○`<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
○Form elements have associated labels
○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.

Send Feedback