Skip to content
https://fau.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
4
REVIEW
1
PASS
8
INFO
0
Checks
13
8 PASS 1 REVIEW 4 FIX
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗
Icons 2 icon(s)
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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA
h2 NEWS
2.00:1
#000000
on
#0E4269
needs 3.0:1 (large text)
24px · bottom of viewport
h2 #FAU
2.00:1
#000000
on
#0E4269
needs 3.0:1 (large text)
24px · bottom of viewport
h2 STUDENT STORIES
2.00:1
#000000
on
#0E4269
needs 3.0:1 (large text)
24px · bottom of viewport
h2 College with a view
2.00:1
#000000
on
#0E4269
needs 3.0:1 (large text)
24px · bottom of viewport
h3 First and Proud
2.00:1
#000000
on
#0E4269
needs 3.0:1 (large text)
19px · bottom of viewport
title Florida Atlantic University | Florida At…
1.67:1
#000000
on
#003366
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
1.67:1
#000000
on
#003366
needs 4.5:1 (normal text)
16px · top of page (header area)
a campus life
4.23:1
#000000
on
#50729C
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

1 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
h2 NEWS2.00:13.0:1
#000000
#0E4269
Fail
h2 #FAU2.00:13.0:1
#000000
#0E4269
Fail
h2 STUDENT STORIES2.00:13.0:1
#000000
#0E4269
Fail
h2 College with a view2.00:13.0:1
#000000
#0E4269
Fail
h3 First and Proud2.00:13.0:1
#000000
#0E4269
Fail
title Florida Atlantic Uni…1.67:14.5:1
#000000
#003366
Fail
a Skip to main content1.67:14.5:1
#000000
#003366
Fail
a FLORIDA ATLANTIC UNI…9.11:14.5:1
#000000
#99ADC2
Pass
span students21.00:14.5:1
#000000
#FFFFFF
Pass
span faculty/staff21.00:14.5:1
#000000
#FFFFFF
Pass
span alumni21.00:14.5:1
#000000
#FFFFFF
Pass
span families21.00:14.5:1
#000000
#FFFFFF
Pass
a apply21.00:14.5:1
#000000
#FFFFFF
Pass
a visit21.00:14.5:1
#000000
#FFFFFF
Pass
a give21.00:14.5:1
#000000
#FFFFFF
Pass
a admissions21.00:14.5:1
#000000
#FFFFFF
Pass
a academics21.00:14.5:1
#000000
#FFFFFF
Pass
a research12.92:14.5:1
#000000
#B0CDF7
Pass
a campus life4.23:14.5:1
#000000
#50729C
Fail
a athletics10.24:14.5:1
#000000
#B4B5B8
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
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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 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
7 headings
PASS
7 headings
Info::
Single H1 present
  • H1 Your Future Awaits
  • H2 This isn’t just a campus - it's a Coastline
  • H2 NEWS
  • H2 #FAU
  • H2 STUDENT STORIES
  • H3 First and Proud
  • H2 College with a view
A+
Alt Text Quality
All 23 images OK
PASS
All 23 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
12 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
23 images 9 good alt text 12 decorative
IssueCount
too long2 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
#main-navigation__searchsearchSite Searcharia-label
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found | Florida Atlantic University ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A
Favicon & Branding
6 icon(s) detected
PASS
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 28 passed
PASS
96

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.

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
PRIVACY POLICY div.footer-links > ul.links > li > a
REGULATIONS & POLICIES div.footer-links > ul.links > li > a
GET HELP div.footer-links > ul.links > li > a

These items highlight common accessibility best practices.

○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
●`[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
●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
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●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 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
○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.
○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.
○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