Skip to content
https://buffalo.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
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 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ 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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 2 <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.
C
Landmark Structure
Action
7 landmarks
REVIEW
7 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 12 fail WCAG AA
REVIEW

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

8 pass 12 fail WCAG AA 8 pass AA only
h1 Your Privacy is Important To Us.
1.05:1
#000000
on
#0D0804
needs 3.0:1 (large text)
32px · top of page (header area)
title Welcome to the University at Buffalo - U…
1.54:1
#000000
on
#002F56
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to Content
1.23:1
#000000
on
#021D34
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
p Buffalo.edu uses cookies to help build a…
1.13:1
#000000
on
#1B110B
needs 4.5:1 (normal text)
16px · top of page (header area)
a Privacy Policy
1.13:1
#000000
on
#1D1009
needs 4.5:1 (normal text)
16px · above the fold
button Okay
1.27:1
#000000
on
#281C17
needs 4.5:1 (normal text)
16px · above the fold
span University at Buffalo (UB)
1.37:1
#000000
on
#0C2351
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
div The State University
1.74:1
#000000
on
#023377
needs 4.5:1 (normal text)
16px · above the fold
div of New York
1.52:1
#000000
on
#002671
needs 4.5:1 (normal text)
16px · above the fold
span University at Buffalo (UB)
1.29:1
#000000
on
#00185D
needs 4.5:1 (normal text)
16px · above the fold
span Toggle Navigation Menu
1.15:1
#000000
on
#000E47
needs 4.5:1 (normal text)
16px · above the fold
div Search
1.17:1
#000000
on
#010F4B
needs 4.5:1 (normal text)
16px · above the fold

2 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 Your Privacy is Impo…1.05:13.0:1
#000000
#0D0804
Fail
h2 We have your major3.66:13.0:1
#000000
#666666
Pass
h2 See how3.66:13.0:1
#000000
#666666
Pass
h2 improves lives3.66:13.0:1
#000000
#666666
Pass
h2 Find People and Depa…3.66:13.0:1
#000000
#666666
Pass
h2 Join Our UB Family3.66:13.0:1
#000000
#666666
Pass
h2 Maps and Directions3.66:13.0:1
#000000
#666666
Pass
h2 UB Mobile App3.66:13.0:1
#000000
#666666
Pass
h3 Come see what it mea…3.66:13.0:1
#000000
#666666
Pass
title Welcome to the Unive…1.54:14.5:1
#000000
#002F56
Fail
a Skip to Content1.23:14.5:1
#000000
#021D34
Fail
p Buffalo.edu uses coo…1.13:14.5:1
#000000
#1B110B
Fail
a Privacy Policy1.13:14.5:1
#000000
#1D1009
Fail
button Okay1.27:14.5:1
#000000
#281C17
Fail
span University at Buffal…1.37:14.5:1
#000000
#0C2351
Fail
div The State University1.74:14.5:1
#000000
#023377
Fail
div of New York1.52:14.5:1
#000000
#002671
Fail
span University at Buffal…1.29:14.5:1
#000000
#00185D
Fail
span Toggle Navigation Me…1.15:14.5:1
#000000
#000E47
Fail
div Search1.17:14.5:1
#000000
#010F4B
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.

B
Lighthouse Accessibility Audits
Score 84/100 — 5 failing, 22 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.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.lSPager > li.active > a > img ul.lSPager > li.active > a > img
ul.lSPager > li > a > img ul.lSPager > li > a > img
ul.lSPager > li > a > img ul.lSPager > li > a > img
ul.lSPager > li > a > img ul.lSPager > li > a > img
ul.lSPager > li > a > img ul.lSPager > li > a > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.lSSlideOuter > ul.lSPager > li.active > a div.lSSlideOuter > ul.lSPager > li.active > a
div.lSSlideOuter > ul.lSPager > li > a div.lSSlideOuter > ul.lSPager > li > a
div.lSSlideOuter > ul.lSPager > li > a div.lSSlideOuter > ul.lSPager > li > a
div.lSSlideOuter > ul.lSPager > li > a div.lSSlideOuter > ul.lSPager > li > a
div.lSSlideOuter > ul.lSPager > li > a div.lSSlideOuter > ul.lSPager > li > a

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SKIP TO CONTENT body#page-8ddb584249 > nav > a#skip-to-content-link

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.

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
Arts and Sciences ul.link-list > li > span.teaser > a.teaser-primary-anchor
Dental Medicine ul.link-list > li > span.teaser > a.teaser-primary-anchor
Careers at UB ul.link-list > li > span.teaser > a.teaser-primary-anchor
View interactive campus maps ul.link-list > li > span.teaser > a.teaser-primary-anchor
Directions and detailed maps ul.link-list > li > span.teaser > a.teaser-primary-anchor

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○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
●`[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.
●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
●Heading elements appear in a sequentially-descending order
●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
○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.
A+
Heading Hierarchy
11 headings
PASS
11 headings
Info::
Single H1 present
  • H1 Your Privacy is Important To Us.
  • H2 We have your major
  • H2 See how our research improves lives
  • H3 Come see what it means to be True Blue
  • H2 Schools and Colleges
  • H2 Find People and Departments
  • H2 Join Our UB Family
  • H2 For Media
  • H2 UB Social Media
  • H2 Maps and Directions
  • H2 UB Mobile App
A
Alt Text Quality
All 20 images OK
PASS
All 20 images OK
Info::
5 image(s) with alt text over 125 characters
Info::
15 image(s) with good alt text
20 images 15 good alt text
IssueCount
too long5 image(s)
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ubcms-gen-151485158textSearcharia-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback