Accessibility

F

Heading Hierarchy

Action

20 headings, 3 skip(s)

FIX

20 headings, 3 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

H4 Admissions
H4 Academics
H4 Research
H4 Global
H4 Campus Life
H4 About BU
H6 Resources for: skipped
H6 University Publications
H3 Could a Retinal Prosthesis Restore Sight for People with Age-Related Macular Degeneration?
H6 Resources for: skipped
H5 CFA’s 2026 Kahn Award Winner and Finalists Plan to Use Their Prize Money to Make an Impact
H5 BU Entrepreneurs Shine at BU’s 2026 Innovators’ Night, Which Drew Hundreds of Spectators
H5 MBTA Green Line B Branch Will Be Suspended from Kenmore Square to BC April 22 to 30
H4 BU Launches Next Phase of You Are Why Initiative Focused on Student Experience
H4 This Alum’s Start-Up Is Now Worth Seven Figures
H4 A Fresh Perspective for BU Medical Students, by Medical Students
H3 BU Athletics
H3 BU Hub
H3 Giving
H6 Resources for: skipped

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

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

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

D

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

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.

D

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.

D

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

9 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 9 <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

Alt Text Quality

Action

3 of 10 images have issues

REVIEW

3 of 10 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

4 image(s) with good alt text

10 images 4 good alt text 1 decorative 3 missing

Issue	Count
missing	3 image(s)
too long	2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title The Brink ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

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

a Academics

2.35:1

#000000

on

#54464A

needs 4.5:1 (normal text)

16px · above the fold

a Research

1.99:1

#000000

on

#463C42

needs 4.5:1 (normal text)

16px · above the fold

a Giving

2.56:1

#000000

on

#564C55

needs 4.5:1 (normal text)

16px · above the fold

a Search

1.96:1

#000000

on

#453B45

needs 4.5:1 (normal text)

16px · above the fold

button Close Menu

1.37:1

#000000

on

#232528

needs 4.5:1 (normal text)

16px · above the fold

a Search Boston University...

1.35:1

#000000

on

#222427

needs 4.5:1 (normal text)

16px · above the fold

a Admissions

1.35:1

#000000

on

#222426

needs 4.5:1 (normal text)

16px · above the fold

a Undergraduate

1.35:1

#000000

on

#222427

needs 4.5:1 (normal text)

16px · mid-page

a Graduate

1.37:1

#000000

on

#232528

needs 4.5:1 (normal text)

16px · mid-page

a International

1.38:1

#000000

on

#242629

needs 4.5:1 (normal text)

16px · mid-page

a Transfer

1.38:1

#000000

on

#242629

needs 4.5:1 (normal text)

16px · mid-page

a Financial Aid

1.38:1

#000000

on

#242629

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h3 Could a Retinal Pros…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Homepage \| Boston Un…	9.55:1	4.5:1	#000000	#EB9999	Pass
a Skip to Main Content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Boston University	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Full Menu	11.07:1	4.5:1	#000000	#BCBCBD	Pass
span Close Menu	7.20:1	4.5:1	#000000	#96979B	Pass
a Admissions	9.80:1	4.5:1	#000000	#AFB1B7	Pass
a Academics	2.35:1	4.5:1	#000000	#54464A	Fail
a Research	1.99:1	4.5:1	#000000	#463C42	Fail
a Giving	2.56:1	4.5:1	#000000	#564C55	Fail
a Search	1.96:1	4.5:1	#000000	#453B45	Fail
button Close Menu	1.37:1	4.5:1	#000000	#232528	Fail
a Search Boston Univer…	1.35:1	4.5:1	#000000	#222427	Fail
a Admissions	1.35:1	4.5:1	#000000	#222426	Fail
a Undergraduate	1.35:1	4.5:1	#000000	#222427	Fail
a Graduate	1.37:1	4.5:1	#000000	#232528	Fail
a International	1.38:1	4.5:1	#000000	#242629	Fail
a Transfer	1.38:1	4.5:1	#000000	#242629	Fail
a Financial Aid	1.38:1	4.5:1	#000000	#242629	Fail
a Extended Ed	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.

B

Lighthouse Accessibility Audits

Score 86/100 — 5 failing, 22 passed

REVIEW

86

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
CLOSE MENU Search Boston University... Admissions Undergraduate Graduate Intern… `body#top > div.page-wrapper > div#buhp-navigation-modal`

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
headlines: `div.buhp-homepage-headlines > div.buhp-homepage-headlines-header > div.buhp-homepage-headlines-date > span`
Resources for: `div.page-wrapper > footer.site-footer > nav.utility-nav > h6.buhp-resources-header`

These are opportunities to improve the legibility of your content.

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
CFA’s 2026 Kahn Award Winner and Finalists Plan to Use Their Prize Money to Mak… `div.buhp-homepage-headlines-content > ul.buhp-homepage-headlines-list > li.buhp-homepage-headlines-item > h5.buhp-homepage-headlines-hed`
Resources for: `div.page-wrapper > footer.site-footer > nav.utility-nav > h6.buhp-resources-header`

These are opportunities to improve keyboard navigation in your application.

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
li.buhp-footer-cards-item > div.buhp-footer-cards-content > figure.buhp-footer-cards-item-media > img `li.buhp-footer-cards-item > div.buhp-footer-cards-content > figure.buhp-footer-cards-item-media > img`
li.buhp-footer-cards-item > div.buhp-footer-cards-content > figure.buhp-footer-cards-item-media > img `li.buhp-footer-cards-item > div.buhp-footer-cards-content > figure.buhp-footer-cards-item-media > img`
li.buhp-footer-cards-item > div.buhp-footer-cards-content > figure.buhp-footer-cards-item-media > img `li.buhp-footer-cards-item > div.buhp-footer-cards-content > figure.buhp-footer-cards-item-media > img`

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.

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
FULL MENU `div.page-wrapper > header.buhp-masthead > nav.buhp-nav-condensed > button.nav-toggle`

○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

●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 use only permitted ARIA attributes

●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

●Touch targets have sufficient size and spacing.

●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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○No element has a `[tabindex]` value greater than 0

○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

Landmark Structure

12 landmarks

PASS

12 landmarks

<main> landmark present

9 <nav> landmark(s) found

9 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

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#q	text	Search for:	none

A+

Link & Button Quality

1 issue(s) across 98 links and 4 buttons

PASS

1 issue(s) across 98 links and 4 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://www.bu.edu/articles/2026/retinal-prosthesis-age-related-macular-degen… ("Learn more")

97 link(s) with descriptive text

98 links

0 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.bu.edu/articles/2026/retinal…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Retinal Prosthesis Age Related Macular Degeneration

101 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://www.bu.edu/articles/2026/retinal-prosthesis-age-related-macular-degen… ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central