Skip to content
https://byu.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
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::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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.
B
Heading Hierarchy
20 headings, 1 skip(s)
REVIEW
20 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H3 Go Forth to Serve skipped
  • H3 A Unique Light
  • H3 Full Divine Potential
  • H3 By Study & By Faith
  • H3 Apply
  • H3 Disciples of Christ
  • H3 Academic Calendar
  • H3 Becoming BYU
  • H3 Athletics
  • H2 Highlighted Events
  • H3 Winter Semester Finals
  • H3 Commencement & Convocations
  • H3 Spring Term Classes Begin
  • H2 News
  • H3 BYU Spanish for nurses club president shares his light through nursing, research and global service
  • H3 BYU illustrator David Habben reimagines Stations of the Cross at BYU Museum of Art
  • H3 Devotional: Trevor Wilson
  • H3 A BYU grad's first-generation journey guided by God
  • H3 Contact BYU Info

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Burger Menu Icon Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
B
Lighthouse Accessibility Audits
Score 89/100 — 5 failing, 27 passed
REVIEW
89

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

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.Page-body > div.ie-div-position-customer-chat > div.button-iframe-wrap > iframe#icChatButton body.Page-body > div.ie-div-position-customer-chat > div.button-iframe-wrap > iframe#icChatButton

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1_Primary_white.svg div.Header-stickyContainer > ps-header.Header > div.Header-contentTop > h1.Header-home-logo
Contact BYU Info Call or Text: 801-422-4636 Email: byu-info@byu.edu Brigham … span.Enhancement > div.RawHtmlModule > div.RawHtmlModule-html > div#byu-info
801-422-4636 div.RawHtmlModule-html > div#byu-info > p > a
byu-info@byu.edu div.RawHtmlModule-html > div#byu-info > p > a
Brigham Young University Provo, UT 84602 div.RawHtmlModule > div.RawHtmlModule-html > div#byu-info > p.mailing-address

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
Go Forth to Serve div.PromoCarouselHeadline > div.PromoCarouselHeadline-container > div.PromoCarouselHeadline-content > h3.PromoCarouselHeadline-title

These are opportunities to improve keyboard navigation in your application.

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
A-Z Index div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU Mobile App (Android) div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU Mobile App (iOS) div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Student Development Services div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Employment at BYU div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Office of Belonging div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Helping Distressed Students div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Library div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Office of IT div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Title IX (sexual misconduct) div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
University Police & Parking div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU-Hawaii div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU-Idaho div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU-Pathway Worldwide div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Ensign College div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU Alumni div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU Athletics div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU News div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU Store div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYUtv div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink

These items highlight common accessibility best practices.

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
More div.PromoCarouselHeadline-container > div.PromoCarouselHeadline-content > div.PromoCarouselHeadline-cta > a.btn
More div.PromoCarouselHeadline-container > div.PromoCarouselHeadline-content > div.PromoCarouselHeadline-cta > a.btn
More div.PromoCarouselHeadline-container > div.PromoCarouselHeadline-content > div.PromoCarouselHeadline-cta > a.btn
More div.PromoCarouselHeadline-container > div.PromoCarouselHeadline-content > div.PromoCarouselHeadline-cta > a.btn
801-422-4636 div.RawHtmlModule-html > div#byu-info > p > a
byu-info@byu.edu div.RawHtmlModule-html > div#byu-info > p > a
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
Image elements have `[alt]` attributes
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.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[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.
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
`[lang]` attributes have a valid value
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
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
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.
`<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.
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
3 landmarks
PASS
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN CONTENTINFO footer
A
Alt Text Quality
3 of 13 images have issues
PASS
3 of 13 images have issues
Warning::
3 image(s) with filename as alt text
Info::
2 decorative image(s) correctly marked
Info::
8 image(s) with good alt text
13 images 8 good alt text 2 decorative 3 generic
IssueCount
filename3 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
qtextSearcharia-label
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)
ElementRatioRequiredFGBGResult
h3 Contact21.00:13.0:1
#000000
#FFFFFF
Pass
title Home - BYU21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main content21.00:14.5:1
#000000
#FFFFFF
Pass
span Menu21.00:14.5:1
#000000
#FFFFFF
Pass
a MyBYU21.00:14.5:1
#000000
#FFFFFF
Pass
a Learning Suite21.00:14.5:1
#000000
#FFFFFF
Pass
span Search21.00:14.5:1
#000000
#FFFFFF
Pass
span Search21.00:14.5:1
#000000
#FFFFFF
Pass
a About21.00:14.5:1
#000000
#FFFFFF
Pass
a Admissions & Aid21.00:14.5:1
#000000
#FFFFFF
Pass
a Academics21.00:14.5:1
#000000
#FFFFFF
Pass
a This is Y21.00:14.5:1
#000000
#FFFFFF
Pass
div contentVerticalPosit…21.00:14.5:1
#000000
#FFFFFF
Pass
div contentVerticalPosit…21.00:14.5:1
#000000
#FFFFFF
Pass
a Go Forth to Serve21.00:14.5:1
#000000
#FFFFFF
Pass
div Each year, thousands…21.00:14.5:1
#000000
#FFFFFF
Pass
a More21.00:14.5:1
#000000
#FFFFFF
Pass
div contentVerticalPosit…21.00:14.5:1
#000000
#FFFFFF
Pass
div contentVerticalPosit…21.00:14.5:1
#000000
#FFFFFF
Pass
a A Unique Light21.00:14.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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback