Skip to content
https://instructure.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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 Present
✗ 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
Theme color only
FIX
Theme color only
Info::
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: #8eabc3
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 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.

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::
6 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 6 <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.
C
Heading Hierarchy
Action
45 headings, 3 skip(s)
REVIEW
45 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Utility-inst
  • H2 Select your location
  • H2 Main - inst
  • H4 Simplifying Digital Learning with Seamless Canvas Integration skipped
  • H4 Your Guide to Choosing a Learning Management System
  • H4 Laying the Groundwork for Effective Edtech
  • H4 Migration Myth Busting: The Truth About Switching Your LMS
  • H4 Supporting One of the Largest Sports Organizations with Canvas LMS
  • H2 Select your location
  • H2 Utility-inst-Login-only
  • H2 In professional learning, outcomes eat skills for breakfast.
  • H2 Be part of education in the making at InstructureCon 2026.
  • H2 Educators are already seeing quick wins with Ignite AI
  • H2 State summative test scores: When you can predict, you can act.
  • H2 What does it mean to be learning, unlearning, and relearning?
  • H2 InstructureCon 2026
  • H1 Welcome to the most-visited education website in the world.
  • H2 Solutions for every age, stage, and transitional moment
  • H3 K–12
  • H3 Higher education
  • H3 Business and government
  • H2 Explore the Instructure ecosystem
  • H2 We're dreaming big, so you can, too.
  • H5 We love our customers (and the feeling is mutual) skipped
  • H3 Accolades from the education world
  • H2 More partners and integrations than any other edtech company
  • H2 Success stories and resources
  • H4 The External Education Playbook skipped
  • H4 Hamilton County Schools and Mastery
  • H4 Trends and Insights from K–12 to Career
  • H4 The Road to Career and College Readiness
  • H4 Providing Equitable Access Statewide With Canvas
  • H4 Your Guide to Strengthening the Student Experience
  • H4 The External Education Playbook
  • H4 Hamilton County Schools and Mastery
  • H4 Trends and Insights from K–12 to Career
  • H4 The Road to Career and College Readiness
  • H4 Providing Equitable Access Statewide With Canvas
  • H4 Your Guide to Strengthening the Student Experience
  • H4 The External Education Playbook
  • H4 Hamilton County Schools and Mastery
  • H2 Ready for the next step?
  • H2 Social
  • H2 Footer Utility
  • H2 Footer - Inst

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

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

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

C
Alt Text Quality
Action
36 of 90 images have issues
REVIEW
36 of 90 images have issues
Critical::
36 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 decorative image(s) correctly marked
Info::
53 image(s) with good alt text
90 images 53 good alt text 1 decorative 36 missing
IssueCount
missing36 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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="edit-submit-solr-search">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="srch" id="edit-srch">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#edit-srchtext(Search...)placeholder only
#edit-submit-solr-searchsubmit(none)none

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

<input type="submit" id="edit-submit-solr-search">

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="text" name="srch" id="edit-srch">

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

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 404 - Page Not Found | Instructure ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Lighthouse Accessibility Audits
Action
Score 78/100 — 6 failing, 23 passed
REVIEW
78

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Why Instructure Solutions Products Resources About Us Support Explore Canvas EN… div.region > div.region-content > nav#block-inst-maininst > ul.menu

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Why Instructure Solutions Products Resources About Us Support Explore Canvas EN… div.region > div.region-content > nav#block-inst-maininst > ul.menu

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Why Instructure nav#block-inst-maininst > ul.menu > li#sa4315-acc-menu-link > a#menu-label-why-instructure
Solutions nav#block-inst-maininst > ul.menu > li#nc571o-acc-menu-link > a#menu-label-solutions
Products nav#block-inst-maininst > ul.menu > li#cobgbv-acc-menu-link > a#menu-label-products
Resources nav#block-inst-maininst > ul.menu > li#3sffen-acc-menu-link > a#menu-label-resources
About Us nav#block-inst-maininst > ul.menu > li#7pkjp7-acc-menu-link > a#menu-label-about-us

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
¡Bienvenido a Instructure.com! Notamos que está visitando desde otra región, ¿l… div.container

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI assistant body.path-frontpage > q-focus-sentinel > div
After AI assistant body.path-frontpage > q-focus-sentinel > div
AI assistant, start div#qualified-multimodal-host > div
AI assistant, end div#qualified-multimodal-host > div

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.

Navigation

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
We love our customers (and the feeling is mutual) div.layout-content > div.layout__region > div.block > h5#we-love-our-customers-and-the-feeling-is-mutual
Trends and Insights from K–12 to Career div#slick-slide00 > div.paragraph > div.asset-slider-inside__item > h4.field--name-field-heading

These are opportunities to improve keyboard navigation in your application.

○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-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.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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 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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○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.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○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
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "block-inst-utilityinst-menu" MAIN CONTENTINFO footer
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
h2 Utility-inst19.92:13.0:1
#000000
#F8F9FA
Pass
h2 Select your location20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Main - inst20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Select your location20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Utility-inst-Login-o…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 In professional lear…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Be part of education…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Educators are alread…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 State summative test…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 What does it mean to…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 More partners and in…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Success stories and …20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Social20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Footer Utility20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Footer - Inst20.82:13.0:1
#000000
#FEFEFE
Pass
h3 K–1220.82:13.0:1
#000000
#FEFEFE
Pass
h3 Higher education20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Business and governm…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Accolades from the e…20.82:13.0:1
#000000
#FEFEFE
Pass
title Instructure: Leading…21.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