Skip to content
https://classlink.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
D
Landmark Structure
Action
17 landmarks
FIX
17 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
7 <nav> landmark(s) found
Warning::
1 of 7 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "w-dropdown-toggle-0" SEARCH MAIN (missing!) ASIDE "Language selected: English" CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

D
Form Accessibility
Action
4 of 4 controls have issues
FIX
4 of 4 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="query" id="search">; <input type="email" name="Subscribe-Email" id="subscribe-email">
4 controls
0 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#searchsearch(Search…)placeholder only
#subscribe-emailemail(Subscribe)placeholder only
inputsubmit(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit">

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

Placeholder text disappears on focus and is not a reliable label.

<input type="search" name="query" id="search">; <input type="email" name="Subscribe-Email" id="subscribe-email">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name 192×192 icon 512×512 icon Start URL Display Mode
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
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Back-to-top link detected
Info::
7 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 7 <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.
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode Dark Mode Supported
color-scheme meta Not set Dark theme-color Not set CSS indicators Detected

Detection limited to meta tags and inline styles.

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

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

0 pass 20 fail WCAG AA
h1 Identity first schools are safer, faster…
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
32px · bottom of viewport
h2 How Can ClassLink Help?
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ClassLink's Library of Products
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Single Sign-On Into Thousands of Apps
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What's New With ClassLink
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Begin Your ClassLink Journey
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Connect
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Products
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Resources
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Company
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Help
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Identity & Access Management
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Learning Analytics
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cybersecurity & MFA
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Secure Single Sign-On
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Transparency & Trust
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
19px · bottom of viewport
h3 LaunchPad
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Analytics
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
19px · bottom of viewport
h3 OneSync
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Roster Server
1.03:1
#000000
on
#010221
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Identity first schoo…1.03:13.0:1
#000000
#010221
Fail
h2 How Can ClassLink He…1.03:13.0:1
#000000
#010221
Fail
h2 ClassLink's Library …1.03:13.0:1
#000000
#010221
Fail
h2 Single Sign-On Into …1.03:13.0:1
#000000
#010221
Fail
h2 What's New With Clas…1.03:13.0:1
#000000
#010221
Fail
h2 Begin Your ClassLink…1.03:13.0:1
#000000
#010221
Fail
h2 Connect1.03:13.0:1
#000000
#010221
Fail
h2 Products1.03:13.0:1
#000000
#010221
Fail
h2 Resources1.03:13.0:1
#000000
#010221
Fail
h2 Company1.03:13.0:1
#000000
#010221
Fail
h2 Help1.03:13.0:1
#000000
#010221
Fail
h3 Identity & Access Ma…1.03:13.0:1
#000000
#010221
Fail
h3 Learning Analytics1.03:13.0:1
#000000
#010221
Fail
h3 Cybersecurity & MFA1.03:13.0:1
#000000
#010221
Fail
h3 Secure Single Sign-O…1.03:13.0:1
#000000
#010221
Fail
h3 Transparency & Trust1.03:13.0:1
#000000
#010221
Fail
h3 LaunchPad1.03:13.0:1
#000000
#010221
Fail
h3 Analytics1.03:13.0:1
#000000
#010221
Fail
h3 OneSync1.03:13.0:1
#000000
#010221
Fail
h3 Roster Server1.03:13.0:1
#000000
#010221
Fail

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.

B
Lighthouse Accessibility Audits
Score 89/100 — 4 failing, 29 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.

ARIA

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Identity div.home-banner-2025-text-col > div.home-banner_2025 > div.banner-text-gold-wrapper > div.banner-text-gold
first schools are safer, faster, and easier to run div.home-banner-2025-content-wrapper > div.home-banner-2025-text-col > div.home-banner_2025 > div.banner-text-white

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
div.navbar-width-container > div.upper-navbar-tools-wrapper > form.navbar-search > input.nav-search-btn div.navbar-width-container > div.upper-navbar-tools-wrapper > form.navbar-search > input.nav-search-btn
Request a Demo div.home-banner-2025-content-wrapper > div.home-banner-2025-text-col > div.home-banner-btn-wrapper > a.button-general
Sign In div.home-banner-mockup_wrapper > div.home-banner-mockup-content > div.launchpad-login-modal-section > div
ClassLink Solutions section.section-standard > div.body-container-standard > div.tab-dropdown-toggle > div.tab-dropdown-toggle-text
6,000 digital learning resources section.section-standard > div.body-container-standard > p.centered > a

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
6,000 digital learning resources section.section-standard > div.body-container-standard > p.centered > a

These are opportunities to improve the legibility of your content.

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
LOGIN div.navbar-width-container > div.upper-navbar-tools-wrapper > div.div-block-804 > a.nabar-login
 See the Benefits div.home-banner-2025-content-wrapper > div.home-banner-2025-text-col > div.home-banner-btn-wrapper > a.button-general
45 E Madison Ave, Ste 7 Clifton, NJ 07011 div.footer-main > div.w-layout-grid > div#w-node-_10203e4a-fb0a-6714-422c-fcec6db2eb8b-6db2eb88 > a.footer-link
Help Center div#w-node-_10203e4a-fb0a-6714-422c-fcec6db2ebf7-6db2eb88 > ul.footer-nav > li.footer-item > a.footer-link
Support div#w-node-_10203e4a-fb0a-6714-422c-fcec6db2ebf7-6db2eb88 > ul.footer-nav > li.footer-item > a.footer-link
Status div#w-node-_10203e4a-fb0a-6714-422c-fcec6db2ebf7-6db2eb88 > ul.footer-nav > li.footer-item > a.footer-link
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>`
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
Image elements have `[alt]` attributes
Input buttons have discernible text.
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
`[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 have a discernible name
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.
`[lang]` attributes have a valid value
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"]`
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[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
Buttons have an accessible name
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 type="image">` elements have `[alt]` text
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
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.
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.
A+
Heading Hierarchy
23 headings
PASS
23 headings
Info::
Single H1 present
  • H1 Identity first schools are safer, faster, and easier to run
  • H2 How Can ClassLink Help?
  • H3 Identity & Access Management
  • H3 Learning Analytics
  • H3 Cybersecurity & MFA
  • H3 Secure Single Sign-On
  • H3 Transparency & Trust
  • H2 ClassLink's Library of Products
  • H3 LaunchPad
  • H3 Analytics
  • H3 OneSync
  • H3 Roster Server
  • H2 Single Sign-On Into Thousands of Apps
  • H2 What's New With ClassLink
  • H3 CLON26: Highlights, Big Announcements, and A Look At What’s Next
  • H3 Why Higher Education Needs Passkeys Now
  • H3 ClassLink Scores Triple Category Win for Tech & Learning’s Best of 2025 Awards
  • H2 Begin Your ClassLink Journey
  • H2 Connect
  • H2 Products
  • H2 Resources
  • H2 Company
  • H2 Help
A+
Alt Text Quality
All 106 images OK
PASS
All 106 images OK
Info::
61 decorative image(s) correctly marked
Info::
45 image(s) with good alt text
106 images 45 good alt text 61 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 ClassLink | Page Not Found Custom Styling Navigation Homepage Link Search Form
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback