Stukent utilizes the Voluntary Product Accessibility Templates (VPATs) to document our conformance with the accessibility standards under Section 508 of the Rehabilitation Act and WCAG 2.2 A and AA, providing detailed reports on our compliance with WCAG 2.2 A and AA. These reports can assist educational institutions in evaluating our products’ accessibility features.
At Stukent, accessibility is more than a checklist; it’s a fundamental commitment to inclusivity and opportunity for everyone. We believe that technology should empower, not exclude. Our mission is to break down barriers and ensure that all learners have access to the educational resources they need to succeed.
We don’t view accessibility as a mere technical or business requirement. We see it as a human imperative. We recognize that education is a gateway to opportunity, and we’re dedicated to ensuring that our technology opens those doors wide for everyone. Our commitment extends beyond meeting WCAG 2.2 standards; we strive to create a truly seamless and positive experience for all users, including those who rely on assistive technologies.
Accessibility is an ongoing journey, and we acknowledge that challenges may arise. We are committed to transparency and continuous improvement.
Name of Product: Stukent Edify Web App 2.0.0.
Date: February 2025
Contact Information: accessibility@stukent.com
Notes: When reporting on conformance with the WCAG 2.2 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.2 Conformance Requirements.
Evaluation Methods Used: Evaluation of the product involved a combination of automated, manual, and functional testing against the applicable success criteria within the Web Content Accessibility Guidelines (WCAG) 2.2 Conformance Levels A and AA. Level Access (Level) tested a selection of the product using a representative sample to cover the components and functionality of use flows. Below is a list of the assistive technologies (ATs) used:
The terms used in the Conformance Level information are defined as follows:
This table documents conformance of the Stukent courseware platform to the WCAG 2.2 A and AA standards, with courseware, simulations, and documents undergoing separate, internal accessibility evaluations.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
|
Partially Supports |
Most non-text content presented to the user in the product has text alternatives that serve the equivalent purpose. Exceptions include:
|
|
|
Supports |
The product does not contain prerecorded audio-only or video-only media. |
|
|
Supports |
The product does not contain any prerecorded synchronized media (video with audio) that requires captions.
|
|
|
Supports |
The product does not contain any prerecorded video media that requires audio descriptions or a media alternative.
|
|
|
Partially Supports
|
In most instances, the product ensures that information, structure, and relationships conveyed through presentation can also be determined programmatically or through text. Exceptions include:
|
|
|
Supports |
The product ensures that a correct reading order can be programmatically determined for content whose presentation sequence affects its meaning. |
|
|
Supports |
The product does not contain instructions that rely solely on sensory characteristics such as shape, size, visual location, or sound. |
|
|
Supports |
The product does not use color as the only visual means of conveying information, indicating an action, or prompting a response.
|
|
|
Supports |
The product does not include audio that plays automatically for more than 3 seconds.
|
|
|
Partially Supports
|
In most instances, the product ensures that interactive content and functionality is accessible and operable using a keyboard or keyboard emulator. Exceptions include:
|
|
|
Supports |
Where a component can receive keyboard focus, the product allows focus to be moved away using only the keyboard and advises users of any non-standard methods required to do so. |
|
|
Supports |
The product does not use character key shortcuts.
|
|
|
Supports |
The product does not contain time-limited or time dependent content.
|
|
|
Supports |
The product does not contain content that moves, blinks, scrolls, or auto-updates.
|
|
|
Supports |
The product does not contain flashing content.
|
|
|
Supports |
The product provides skip links and other mechanisms to bypass blocks of content repeated on multiple pages.
|
|
|
Partially Supports
|
Most pages of the product provide titles that adequately describe their topic or purpose. Exceptions include:
|
|
|
Partially Supports
|
In most instances, pages of the product can be navigated sequentially with a focus order that matches the logical reading order. Exceptions include:
|
|
|
Supports |
The product ensures that the purpose of links can be determined from the link text alone or in combination with the surrounding or programmatic context.
|
|
|
Supports
|
The product does not require multipoint or path based gestures for operation.
|
|
|
Supports |
The product does not contain functionality that uses a pointer for operation, or the down-event of the pointer is not used to execute any part of the functionality.
|
|
|
Supports |
The product ensures that when interface components have visual labels that include text, the provided accessible name contains the visually presented text.
|
|
|
Supports |
The product does not contain functionality that requires device motion or user motion.
|
|
|
Supports |
The product ensures that the default human language used on each page can be programmatically determined.
|
|
|
Supports |
The product ensures that interface components do not initiate a change of context when receiving focus.
|
|
|
Supports |
The product ensures that interactive components do not initiate a change in context when the component setting is changed unless followed by an explicit user action such as activation of a button or link unless the user has been advised of this behavior before use.
|
|
|
Supports |
Help mechanisms occur in the same order relative to other page content in the product.
|
|
|
Supports |
Where the product automatically detects input errors, the item or field in error is identified and the error is described to the user in text.
|
|
|
Partially Supports |
In most instances, where user input is required, the product presents adequate labels or instructions for successfully providing that input. Exceptions include:
|
|
|
Supports |
The product does not request redundant user-entered information in multi-step processes.
|
|
|
Not Applicable |
Does Not Apply
|
|
|
Partially Supports
|
In most instances, the product contains user interface components whose name, role, state, and value can be programmatically determined, and whose state, properties, and value, where applicable, can be programmatically set. Exceptions include:
|
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
|
Supports |
The product does not contain any live synchronized media (video with audio) that requires real-time captioning.
|
|
|
Supports |
The product does not contain any prerecorded synchronized media (video with audio) that requires audio descriptions.
|
|
|
Supports |
The product does not restrict its view and operation to a single display orientation, such as portrait or landscape unless a specific orientation is essential.
|
|
|
Supports |
The product ensures that the purpose of input fields that request information about the user, such as name or email, can be programmatically determined.
|
|
|
Supports
|
Visual presentation of text and images of text in the product provides a contrast ratio of at least 4.5:1 against adjacent colors.
|
|
|
Partially Supports
|
In most instances, the product allows text to be resized without assistive technology up to 200 percent without loss of content or functionality. Exceptions include:
|
|
|
Supports |
Except for logos, the product uses text instead of images of text.
|
|
|
Does Not Support |
Pages of the product do not allow for resizing to a minimum width of 320 CSS pixels or vertical height of 256 CSS pixels without loss of content or functionality, and without requiring scrolling in two dimensions except where scrolling is required for two-dimensional content such as tables, diagrams, or maps. Examples include:
|
|
|
Partially Supports |
In most instances, the visual presentation of non-text content in the product has a contrast ratio of at least 3:1 against adjacent color(s). Exceptions include:
|
|
|
Supports
|
The product supports user changes in text style properties, such as line height or text spacing, without loss of content or functionality.
|
|
|
Supports |
The product does not contain content that appears on pointer hover or keyboard focus.
|
|
|
Supports |
The product does not provide a set of pages or apps, and is not otherwise implemented in a way that make it subject to this criterion.
|
|
|
Supports |
Headings and labels provided in the product adequately describe the topic or purpose of the content with which they are associated.
|
|
|
Supports |
The product provides a visible indication of keyboard focus for elements on each page.
|
|
|
Supports |
When user interface components receive keyboard focus, they are, at minimum, partially visible. |
|
|
Supports |
The product does not use dragging movements for interactive functionality. |
|
|
Supports
|
The size of targets in the product meet the requirements of this criterion. |
|
|
Supports
|
Pages of the product present content in a single language. |
|
|
Supports |
The product ensures that navigational mechanisms repeated across the product are presented consistently and in the same relative order.
|
|
|
Supports
|
The product ensures that components with the same functionality are identified consistently across pages of the product. |
|
|
Supports |
Where the product automatically detects input errors and provides error messages, the product also provides suggestions for correcting each error. |
|
|
Supports |
The product does not cause financial transactions or legal commitments to occur. User-controllable data is checked before submission and can be reversed or revised after submission. |
|
|
Supports |
The product does not require an authentication process.
|
|
|
Partially Supports
|
In most instances, the product provides status messages that can be presented to assistive technologies without receiving focus. Exceptions include:
|
To deliver accessible learning platforms, we integrate accessibility into every stage of our development process:
We foster a culture where accessibility is a core value. We are educating our teams—from designers and engineers to product managers and content creators—on assistive technologies and accessibility best practices. We’re sharing user stories and feedback to cultivate empathy and understanding.
We’re incorporating accessibility considerations from the initial design phase, ensuring a solid foundation for all our products. We are leveraging industry-leading guidelines and best practices to build accessible interfaces and features.
We are employing a combination of manual and automated testing techniques to identify and address accessibility issues before release. This includes testing with assistive technologies.
We are tracking accessibility remediation and new feature progress to drive ongoing quality enhancements.
We partner with reputable accessibility vendors, such as Level Access, to conduct regular compliance audits and validate our progress.
To ensure efficient and secure delivery of accessible materials for our Courseware Platform, we ask that users requiring accommodations first contact their institution’s Accessibility Services or Disability Services office. This office is typically best equipped to assess individual needs and manage the provision of necessary accommodations.
If your institution does not have a dedicated accessibility services office, please reach out to the instructor of the course for which you require materials.
The institution’s Accessibility Services office or the course instructor can then directly request the necessary materials from us. Please note that to maintain a streamlined process and ensure appropriate handling of accessibility requests, we are best able to work directly with the institution’s designated accessibility office or the course instructor. Should the requested materials be something we can provide, we will do our best to fulfill the request in a timely manner.
Please be aware that our CTE Platform and Simulation Platform are currently undergoing thorough third-party accessibility audits. We are aware of existing accessibility gaps within these platforms and are actively working towards remediation. Therefore, this request process currently applies only to our Courseware Platform.
We are proud to confirm that our existing courseware platform complies with WCAG 2.2 A and AA standards. We understand the importance of maintaining this level of accessibility in educational resources and are dedicated to the continuous improvement of our Courseware Platform’s accessibility.
None at this time
We are actively working to ensure our CTE Platform complies with WCAG 2.2 standards and are committed to creating an accessible learning environment. Built with an accessibility-first UI component library, our CTE platform provides authors with the ability to add descriptive alternative text to all images, and all video content includes captions. To further enhance accessibility, we are currently undergoing a thorough third-party audit to identify any existing concerns. Upon completion of this audit, we will begin remediating identified issues to improve the platform’s usability for all users. Following these improvements, we will engage a third-party vendor to conduct a comprehensive audit and provide an updated VPAT. We understand the importance of accessible educational resources and are dedicated to the continuous improvement of our CTE Platform’s accessibility.
None at this time.
We are actively working to ensure our Simulation Platform complies with WCAG 2.2 standards. We are currently conducting a thorough third-party audit to identify any existing accessibility concerns. Upon completion, we will begin remediating any identified issues to improve the platform’s usability for all users. We will then engage a third-party vendor to conduct a comprehensive audit and provide an updated VPAT. We understand the importance of accessible educational resources and are dedicated to the continuous improvement of our Simulation Platform’s accessibility.
Details, coming soon.
None at this time.
Phase 1 (Q1): Remediate current findings in the Stukent courseware platform
Phase 2 (Q2 – Q3): Remediate findings in Stukent CTE platform
Phase 3 (every 24 months): Third party audit for platform, excluding some simulations
We are committed to open communication and collaboration. If you have any questions or concerns regarding accessibility, please reach out to us:
We are dedicated to creating accessible and inclusive learning experiences for all. Thank you for your continued partnership.