Skip to content
https://fsu.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 4 <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
Form Accessibility
Action
3 of 6 controls have issues
REVIEW
3 of 6 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="type">; <input type="text" name="keywords">; <input type="submit" name="fsuSearch">
Info::
3 control(s) properly labeled
6 controls
3 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#osano-cm-dialog-toggle--category_MARKETINGcheckboxnone
#osano-cm-dialog-toggle--category_PERSONALIZATIONcheckboxnone
#osano-cm-dialog-toggle--category_ANALYTICScheckboxnone
typeselect(none)none
keywordstext(none)none
fsuSearchsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select name="type">; <input type="text" name="keywords">; <input type="submit" name="fsuSearch">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 13 fail WCAG AA
REVIEW

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

7 pass 13 fail WCAG AA
h2 Search FSU
2.28:1
#000000
on
#782F40
needs 3.0:1 (large text)
24px · mid-page
h2 Carousel content with 1 slides.
2.28:1
#000000
on
#782F40
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Florida State University names two new R…
2.28:1
#000000
on
#782F40
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Preeminence
2.28:1
#000000
on
#782F40
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Program changes based on Florida law
2.28:1
#000000
on
#782F40
needs 3.0:1 (large text)
24px · bottom of viewport
h3 We take student success seriously
2.28:1
#000000
on
#782F40
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Academic Calendar
2.28:1
#000000
on
#782F40
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Student Stars
2.28:1
#000000
on
#782F40
needs 3.0:1 (large text)
19px · bottom of viewport
h3 kNOw MORE
2.28:1
#000000
on
#782F40
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Florida State's
2.28:1
#000000
on
#782F40
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Economic Impact
2.28:1
#000000
on
#782F40
needs 3.0:1 (large text)
19px · bottom of viewport
title Florida State University
2.28:1
#000000
on
#782F40
needs 4.5:1 (normal text)
16px · top of page (header area)
span Opens in a new window
2.28:1
#000000
on
#782F40
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Search FSU2.28:13.0:1
#000000
#782F40
Fail
h2 Carousel content wit…2.28:13.0:1
#000000
#782F40
Fail
h2 Florida State Univer…2.28:13.0:1
#000000
#782F40
Fail
h2 Preeminence2.28:13.0:1
#000000
#782F40
Fail
h2 Program changes base…2.28:13.0:1
#000000
#782F40
Fail
h3 We take student succ…2.28:13.0:1
#000000
#782F40
Fail
h3 Academic Calendar2.28:13.0:1
#000000
#782F40
Fail
h3 Student Stars2.28:13.0:1
#000000
#782F40
Fail
h3 kNOw MORE2.28:13.0:1
#000000
#782F40
Fail
h3 Florida State's2.28:13.0:1
#000000
#782F40
Fail
h3 Economic Impact2.28:13.0:1
#000000
#782F40
Fail
title Florida State Univer…2.28:14.5:1
#000000
#782F40
Fail
span Opens in a new windo…2.28:14.5:1
#000000
#782F40
Fail
span Opens an external we…9.89:14.5:1
#000000
#C7ABB1
Pass
span Opens an external we…21.00:14.5:1
#000000
#FFFFFF
Pass
span This website utilize…20.29:14.5:1
#000000
#FBFBFB
Pass
span You may change your …19.09:14.5:1
#000000
#F4F4F4
Pass
span You may close this b…19.09:14.5:1
#000000
#F4F4F4
Pass
a Privacy Policy19.09:14.5:1
#000000
#F4F4F4
Pass
a Storage Preferences19.09:14.5:1
#000000
#F4F4F4
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
14 landmarks
PASS
14 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Utility Navigation" SEARCH MAIN ASIDE "carousel pause/play control" CONTENTINFO footer
A+
Heading Hierarchy
15 headings
PASS
15 headings
Info::
Single H1 present
  • H2 Search FSU
  • H1 Florida State University
  • H2 Carousel content with 1 slides.
  • H2 Florida State University names two new Robert O. Lawton Distinguished Professors
  • H2 Preeminence
  • H3 Admissions: Apply Now
  • H4 Related Links
  • H3 We take student success seriously
  • H3 Academic Calendar
  • H3 Student Stars
  • H3 kNOw MORE
  • H3 Florida State's Economic Impact
  • H2 PUBLIC RECORDS NOTICE PURSUANT TO SECTION 119.12, F.S.
  • H2 Florida Board of Governors Statement of Free Expression
  • H2 Program changes based on Florida law
A+
Alt Text Quality
All 8 images OK
PASS
All 8 images OK
Info::
5 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
8 images 3 good alt text 5 decorative
All images have appropriate alt text.
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 Academics | Florida State University ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /_/s3.4/css/print.css
Print Stylesheet ✓ Print Optimized
Print stylesheet /_/s3.4/css/print.css ✓Inline @media print Not detected ✗
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 32 passed
PASS
100

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.

○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]` 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.
●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
●`<frame>` or `<iframe>` elements have a title
●`<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
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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.
○`[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.
○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