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 1 REVIEW 5 FIX

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

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.

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 ✗

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Not Found | William & Mary ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Landmark Structure

12 landmarks

PASS

12 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

A+

Heading Hierarchy

32 headings

PASS

32 headings

Single H1 present

H1 William & Mary
H2 Distinct & Distinguished
H2 One Tribe One Day
H3 One Tribe One Day
H2 Start Your William & Mary Admission Journey Here
H2 William & Mary by the Numbers: A Top School for Academics and Beyond
H3 Best Public School for Internships
H3 Best Public School for Undergraduate Teaching
H3 Best Value Public Schools
H3 Study Abroad Participation
H2 Explore William & Mary's Academic Programs
H2 William & Mary News
H2 William & Mary on Instagram
H2 William & Mary Events
H3 Spotlight Event
H3 Upcoming Featured Events
H2 People of William & Mary
H3 Milan Chakraborty ’00
H3 Tucker Peters ’28
H3 Kiya Tomlin ’96
H3 Alexandra Otto ’27
H3 Nyla Pollard ’21
H3 Joe Brady ’13
H3 Ayanna Williams ’26
H3 Rebecca Dougherty M.Ed. ’23
H3 Kristen Popham ’20
H3 Pip Decker ’04
H3 Patton Oswalt ’91, D.A. ’23
H3 Darius McCallum ’27
H2 Resources for
H2 Discover
H2 Quick Links

Alt Text Quality

All 44 images OK

PASS

All 44 images OK

6 image(s) with alt text over 125 characters

10 decorative image(s) correctly marked

28 image(s) with good alt text

44 images 28 good alt text 10 decorative

Issue	Count
too long	6 image(s)

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/id

A+

Link & Button Quality

178 links, 19 buttons — all OK

PASS

178 links, 19 buttons — all OK

178 link(s) with descriptive text

178 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

197 links and buttons have descriptive text

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 William & Mary	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Distinct & Distingui…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 One Tribe One Day	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Start Your William &…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 William & Mary by th…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore William & Ma…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 William & Mary News	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 William & Mary on In…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 William & Mary Event…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 People of William & …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Resources for	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Discover	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Quick Links	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 One Tribe One Day	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Best Public School f…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Best Public School f…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Best Value Public Sc…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Study Abroad Partici…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Spotlight Event	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Upcoming Featured Ev…	21.00:1	3.0: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+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 28 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.

Names and labels

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.wm-topbar > div.button-wrapper-for-older-browsers > nav.wm-topbar__buttons > a.wm-topbar__menu-button `div.wm-topbar > div.button-wrapper-for-older-browsers > nav.wm-topbar__buttons > a.wm-topbar__menu-button`

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.

○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

●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

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

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

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

○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

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