Skip to content
https://binghamton.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Form Accessibility
Action
4 of 5 controls have issues
REVIEW
4 of 5 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="btn_site" id="search-btn-site">; <input type="button" name="btn_section" id="search-btn-section">; <input type="button" name="btn_people" id="search-btn-people">; <input type="button" name="btn_programs" id="search-btn-programs">
Info::
1 control(s) properly labeled
5 controls
1 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
#search-qsearchSearchfor/id
#search-btn-sitesubmit(none)none
#search-btn-sectionbutton(none)none
#search-btn-peoplebutton(none)none
#search-btn-programsbutton(none)none

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

<input type="submit" name="btn_site" id="search-btn-site">; <input type="button" name="btn_section" id="search-btn-section">; <input type="button" name="btn_people" id="search-btn-people">; <input type="button" name="btn_programs" id="search-btn-programs">

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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title File not Found - Binghamton University ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 15 fail WCAG AA
REVIEW

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

5 pass 15 fail WCAG AA
h2 The best public university in the Northe…
1.57:1
#000000
on
#003724
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Undergraduate Admissions
1.57:1
#000000
on
#01371F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Graduate Admissions
1.57:1
#000000
on
#01371F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Recent News
1.57:1
#000000
on
#01371F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 BingU Social
1.57:1
#000000
on
#01371F
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Video
1.57:1
#000000
on
#01371F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Binghamton Students Help Kids Communicat…
1.57:1
#000000
on
#01371F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Blog
1.57:1
#000000
on
#01371F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Info For
1.57:1
#000000
on
#01371F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Find
1.57:1
#000000
on
#01371F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Resources
1.57:1
#000000
on
#01371F
needs 3.0:1 (large text)
19px · bottom of viewport
title Binghamton University, State University …
1.85:1
#000000
on
#004333
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
1.85:1
#000000
on
#004333
needs 4.5:1 (normal text)
16px · top of page (header area)
a Binghamton University: The State Univers…
3.04:1
#000000
on
#665750
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
label Search
4.02:1
#000000
on
#716B6B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

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 Binghamton20.82:13.0:1
#000000
#FEFEFE
Pass
h2 The best public univ…1.57:13.0:1
#000000
#003724
Fail
h2 Undergraduate Admiss…1.57:13.0:1
#000000
#01371F
Fail
h2 Graduate Admissions1.57:13.0:1
#000000
#01371F
Fail
h2 Recent News1.57:13.0:1
#000000
#01371F
Fail
h2 BingU Social1.57:13.0:1
#000000
#01371F
Fail
h3 Video1.57:13.0:1
#000000
#01371F
Fail
h3 Binghamton Students …1.57:13.0:1
#000000
#01371F
Fail
h3 Blog1.57:13.0:1
#000000
#01371F
Fail
h3 Info For1.57:13.0:1
#000000
#01371F
Fail
h3 Find1.57:13.0:1
#000000
#01371F
Fail
h3 Resources1.57:13.0:1
#000000
#01371F
Fail
title Binghamton Universit…1.85:14.5:1
#000000
#004333
Fail
a Skip to main content1.85:14.5:1
#000000
#004333
Fail
a Binghamton Universit…3.04:14.5:1
#000000
#665750
Fail
div Binghamton Universit…9.89:14.5:1
#000000
#BDAFAC
Pass
span search8.72:14.5:1
#000000
#98A9BA
Pass
span menu9.60:14.5:1
#000000
#B8ADAB
Pass
label Search4.02:14.5:1
#000000
#716B6B
Fail
div Binghamton Universit…11.25:14.5:1
#000000
#C4BBC4
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
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
1 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Skip Navigation" MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
12 headings
PASS
12 headings
Info::
Single H1 present
  • H1 Binghamton
  • H2 The best public university in the Northeast
  • H2 Undergraduate Admissions
  • H2 Graduate Admissions
  • H2 Recent News
  • H2 BingU Social
  • H3 Video
  • H3 Binghamton Students Help Kids Communicate on Horseback
  • H3 Blog
  • H3 Info For
  • H3 Find
  • H3 Resources
A+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
2 image(s) with good alt text
2 images 2 good alt text
All images have appropriate alt 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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Info For div.columns > ul.accordion > li.accordion-item > a#18ljrb-accordion-label
Find div.columns > ul.accordion > li.accordion-item > a#hu4j1g-accordion-label
Resources div.columns > ul.accordion > li.accordion-item > a#z5jlwx-accordion-label

These are opportunities to improve the usage of ARIA in your application which 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-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
●`<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
●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
○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.
○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