Table of Contents
Are your Catalogs accessible to individuals with disabilities?
What specific accessibility standards does the External Catalog meet?
Is there a report that shows the level of accessibility?
Does your External Catalog have a responsive design?
Does your Catalog support keyboards?
Has the External Catalog been tested by individuals with disabilities to ensure accessibility?
In what ways do you test the accessibility of external catalogs?
How do you handle user feedback and accessibility issues, and what is your process for addressing them?
Related Articles
Are your Catalogs accessible to individuals with disabilities?
Yes. Our public-facing catalogs are accessible to all users, regardless of their disabilities. Our External Catalog supports keyboards, screen readers, and third-party tools that increase accessibility level (high contrast, larger font size/spacing, etc.).
However, it is important to note that external catalogs are highly configurable and could become inaccessible due to client configuration (poor color-contrast ratio, etc.).
What specific accessibility standards does the External Catalog meet?
Our goal is to meet the worldwide standard for web accessibility known as “WCAG 2.1 A-level”. These guidelines comprise a set of best practices that ensure that our application is fully accessible to all users, including those who use assistive technologies like screen readers.
We are aware of a few minor accessibility issues that prevent us from being fully WCAG 2.1 A-level compliant, and we are working to resolve them.
Is there a report that shows the level of accessibility?
Yes, in March 2023, we conducted our first internal accessibility Voluntary Product Accessibility Template (VPAT) audit, which shows External Catalog compliance with WCAG guidelines.
You can find that report, and learn more about its findings, here.
The VPAT report reflects our accessibility level as of the date of the report. The information in the report is provided in good faith, is true and correct to the best of our knowledge, and is supplied for the customer “as is” for informational purposes only.
Does your External Catalog have a responsive design?
Yes, our public-facing Catalog provides a rock-solid experience on all devices, resolutions, and operating systems. Moreover, by following industry Code quality standards, we go beyond standard breakpoints for typical screen resolutions when it comes to responsiveness. This allows us to fit content perfectly no matter what 3rd party plugins (e.g. High Contrast, ARC Toolkit) or assistive software are being used.
Does your Catalog support keyboards?
Yes, we support keyboards across the entire public-facing Catalog. By presenting content in a meaningful order, separating navigation menus from content, and following industry standards when coding HTML, we make sure it works seamlessly.
Has the External Catalog been tested by individuals with disabilities to ensure accessibility?
As of yet, we haven't conducted such tests on our external catalog.
In order to ensure that we could assess accessibility fully, we followed industry-standard guidelines (WCAG) and the latest research findings from design leaders (Norman-Nielsen Group & Interaction Design Foundation), and our internal design expertise supported by modern tools.
In addition, we participate in user testing sessions conducted by our customers (on average 6 hours per quarter).
In what ways do you test the accessibility of external catalogs?
In 2023, we tested eight different public-facing Catalogs using a Google Chrome browser.
Catalogs were tested both automatically and manually to ensure they met the right criteria from a human perspective.
We tested their home page, global search modal, program landing page, program page, course landing page, course page, custom pages (parent + child), and department pages.
Assistive technology used was VoiceOver (MacOS).
Accessibility testing tools include Browser Development Tools, Google Lighthouse Accessibility Checker, aXe: the Accessibility Engine, and ARC Toolkit.
The accessibility standard we’re checking against is WCAG 2.1 A and AA Level.
How do you handle user feedback and accessibility issues, and what is your process for addressing them?
Feedback and accessibility issues can be reported to your Customer Success representative (Project Manager or CSM), Product Managers, and support@coursedog.com.
We work in an iterative development process, all reported issues are re-evaluated internally and added to the engineering backlog if they impact site accessibility.