Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 5 REVIEW 3 FIX

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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 ✗

Alt Text Quality

2 of 35 images have issues

REVIEW

2 of 35 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

26 decorative image(s) correctly marked

7 image(s) with good alt text

35 images 7 good alt text 26 decorative 2 missing

Issue	Count
missing	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

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 Page not found - York University ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 1 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Start your future wi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Learning for life-lo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Undergraduate Progra…	15.43:1	3.0:1	#212529	#FFFFFF	Pass
h2 Graduate Programs	15.43:1	3.0:1	#212529	#FFFFFF	Pass
h2 Continuing Studies	15.43:1	3.0:1	#212529	#FFFFFF	Pass
h2 International Studen…	15.43:1	3.0:1	#212529	#FFFFFF	Pass
h2 Student Voices	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 York by the Numbers	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Your journey starts …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore your future …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What’s happening a…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 York U Views	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Connect with York Un…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title York University \| To…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
legend Global Search	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label search box	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span search button	15.56:1	4.5:1	#000000	#E2DCE1	Pass
a Skip to main content	14.99:1	4.5:1	#000000	#DBD9DE	Pass
a Skip to local naviga…	6.51:1	4.5:1	#000000	#959252	Pass
span Mobile navigation bu…	7.00:1	4.5:1	#000000	#A3971B	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.

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

4 <nav> landmark(s) found

2 of 4 <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

13 headings

PASS

13 headings

Single H1 present

H1 Start your future with confidence
H2 Learning for life-long success
H2 Undergraduate Programs
H2 Graduate Programs
H2 Continuing Studies
H2 International Students
H2 Student Voices
H2 York by the Numbers
H2 Your journey starts here, with a community that moves you forward
H2 Explore your future campus
H2 What’s happening at York U
H2 York U Views
H2 Connect with York University

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
#yeb13searchfield	search	search box	for/id

Link & Button Quality

171 links, 4 buttons — all OK

PASS

171 links, 4 buttons — all OK

8 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://futurestudents.yorku.ca/; https://futurestudents.yorku.ca/requirements; https://www.yorku.ca/partnerships/; http://yorku.ca/about; https://students.yorku.ca/student-communities; https://futurestudents.yorku.ca/financing-your-degree/scholarships-bursaries; https://www.youtube.com/watch?v=4JZaN8U3Xl8&ab_channel=YorkUniversity; https://futurestudents.yorku.ca/tours

163 link(s) with descriptive text

171 links

0 empty

0 generic text

8 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://futurestudents.yorku.ca/	Explore Programs	new tab	Add '(opens in new tab)' to text
https://futurestudents.yorku.ca/requirem…	Requirements	new tab	Add '(opens in new tab)' to text
https://www.yorku.ca/partnerships/	Partnerships	new tab	Add '(opens in new tab)' to text
http://yorku.ca/about	About	new tab	Add '(opens in new tab)' to text
https://students.yorku.ca/student-commun…	Student Life	new tab	Add '(opens in new tab)' to text
https://futurestudents.yorku.ca/financin…	Scholarships & Bursaries	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/watch?v=4JZaN8U3…	Watch the Welcome Video	new tab	Add '(opens in new tab)' to text
https://futurestudents.yorku.ca/tours	Book a Tour	new tab	Add '(opens in new tab)' to text

167 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://futurestudents.yorku.ca/; https://futurestudents.yorku.ca/requirements; https://www.yorku.ca/partnerships/; http://yorku.ca/about; https://students.yorku.ca/student-communities; https://futurestudents.yorku.ca/financing-your-degree/scholarships-bursaries; https://www.youtube.com/watch?v=4JZaN8U3Xl8&ab_channel=YorkUniversity; https://futurestudents.yorku.ca/tours

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Lighthouse Accessibility Audits

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

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
View All News `div.wp-block-group > div.wp-block-group > p.view-all-wrapper > a`

These are opportunities to improve the legibility of your content.

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

●`button`, `link`, and `menuitem` elements have accessible names

●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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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