Edfinity Accessibility Conformance Report

VPAT® Version 2.5

Name of Product/Version: Edfinity, version 11.0

Product Description: Edfinity is an online homework system that provides affordable access to educational instruction and content for students.

Date Reviewed: November 4, 2024

Contact Information: accessibility@edfinity.com

Notes:

Evaluation Methods Used: This VPAT covers all features related to student enrollment and assessment activities. Conformance to the listed accessibility standards has been evaluated using a combination of static analysis tools and manual testing with assistive technologies. Evaluations were conducted by Edfinity as well as by a third party assistive technology specialist.

Axe DevTools Pro was used to conduct automated browser testing. Testing with screen reading software was conducted by a native AT user, who worked through student applications flows using JAWS for Windows (version 2024) screen reading software within a Chrome browser. Additionally, the Edfinity accessibility team worked through the flows using VoiceOver screen reading software (version MacOS 14.7) within a Chrome browser.

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Standard/Guideline Included in Report
Web Content Accessibility Guidelines 2.2, at https://www.w3.org/TR/WCAG22/ Level A included
Level AA included
Level AAA included
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018, at https://www.Section508.gov Yes
EN 301 549 V3.2.1 Accessibility requirements suitable for public procurement of ICT products and services in Europe, at https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf Yes

Terms

The terms used in the Conformance Level information are defined as follows:

  • Supports — The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
  • Partially Supports — Some functionality of the product does not meet the criterion.
  • Does Not Support — The majority of product functionality does not meet the criterion.
  • Not Applicable — The criterion is not relevant to the product.
  • Not Evaluated — The product has not been evaluated against the criterion. This can be used only in WCAG 2.2 Level AAA.

WCAG 2.2 Report

Table 1 and Table 2 also document conformance with:

  • EN 301 549: Chapter 9 – Web, Chapter 10 – Non-Web documents, Section 11.2.1- Non-Web Software (excluding closed functionality), and Section 11.2.2 – Non-Web Software (closed functionality).
  • Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.

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.

Table 1: Success Criteria, Level A

Criteria Conformance Level Remarks and Explanations

1.1.1 Non-text Content (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.1.1.1 (Web)
  • 10.1.1.1 (Non-web document)
  • 11.1.1.1.1 (Open Functionality Software)
  • 11.1.1.1.2 (Closed Functionality Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity uses standard HTML and WAI-ARIA techniques for providing text equivalents of non-text elements. This includes the use of “alt” attributes for images and the use of “aria-label” or “aria-describedby” attributes for other visual elements.

Some purely decorative elements that have no functional or informational purpose may not provide a text alternative.

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.1.2.1 (Web)
  • 10.1.2.1 (Non-web document)
  • 11.1.2.1.1 (Open Functionality Software)
  • 11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity does not include audio or video content by default. However, users may choose to include video content in courses built within Edfinity. In such cases, users may include alternative representations (such as text transcripts) that present equivalent information to the videos.

1.2.2 Captions (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.1.2.2 (Web)
  • 10.1.2.2 (Non-web document)
  • 11.1.2.2 (Open Functionality Software)
  • 11.1.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Does Not Support

Edfinity does not include audio or video content by default. However, users may choose to include video content in courses built using Edfinity. In that case, Edfinity does not provide capabilities for captioning or defining audio descriptions of designer-specified video content.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.1.2.3 (Web)
  • 10.1.2.3 (Non-web document)
  • 11.1.2.3.1 (Open Functionality Software)
  • 11.1.2.3.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Not Applicable

Edfinity does not use synchronized media.

1.3.1 Info and Relationships (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.1.3.1 (Web)
  • 10.1.3.1 (Non-web document)
  • 11.1.3.1.1 (Open Functionality Software)
  • 11.1.3.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity uses semantically-correct markup so that information, structure, and relationships can be understood independent of presentation.

1.3.2 Meaningful Sequence (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.1.3.2 (Web)
  • 10.1.3.2 (Non-web document)
  • 11.1.3.2.1 (Open Functionality Software)
  • 11.1.3.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity generates semantically-correct markup to allow assistive technologies to interpret the meaning of content and controls.

1.3.3 Sensory Characteristics (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.1.3.3 (Web)
  • 10.1.3.3 (Non-web document)
  • 11.1.3.3 (Open Functionality Software)
  • 11.1.3.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity does not depend solely on sensory characteristics such as shape, size, visual location, orientation, or sound to understand content. For example, while labels and instructions display in close proximity to corresponding input elements, Edfinity also uses WAI-ARIA techniques to ensure that those relationships are available to Assistive Technologies.

For user-specified content, Edfinity provides capabilities for defining text alternatives and specifying the overall layout.

1.4.1 Use of Color (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.1.4.1 (Web)
  • 10.1.4.1 (Non-web document)
  • 11.1.4.1 (Open Functionality Software)
  • 11.1.4.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Color is only used as a decorative or supplemental attribute of user interface elements. A textual representation is always used as the primary mechanism for conveying information.

Users may choose how to use color in the courses they build using Edfinity. Edfinity provides capabilities for defining text alternatives of designer-specified content.

1.4.2 Audio Control (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.1.4.2 (Web)
  • 10.1.4.2 (Non-web document)
  • 11.1.4.2 (Open Functionality Software)
  • 11.1.4.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity does not include audio or video content by default. However, users may choose to include video content in courses they build with Edfinity.

2.1.1 Keyboard (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.1.1 (Web)
  • 10.2.1.1 (Non-web document)
  • 11.2.1.1.1 (Open Functionality Software)
  • 11.2.1.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity is a web-based application that supports standard keyboard navigation and input functions (such as pressing [Tab] to move between input fields, pressing the arrow keys to move between list items, and pressing [Space] or [Enter] to make selections).

2.1.2 No Keyboard Trap (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.1.2 (Web)
  • 10.2.1.2 (Non-web document)
  • 11.2.1.2 (Open Functionality Software)
  • 11.2.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity is a web-based application that supports standard keyboard navigation and ensures that keyboard users cannot be trapped in a subset of content.

2.1.4 Character Key Shortcuts (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.1.4 (Web)
  • 10.2.1.4 (Non-web document)
  • 11.2.1.4.1 (Open Functionality Software)
  • 11.2.1.4.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 - Does not apply

 Not Applicable

Edfinity does not implement a keyboard shortcut in content using only letter.

2.2.1 Timing Adjustable (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.2.1 (Web)
  • 10.2.2.1 (Non-web document)
  • 11.2.2.1 (Open Functionality Software)
  • 11.2.2.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Partially Supports

For assignment sessions that specify a time limit, Edfinity has a timeout alert to notify students when the session is about to end. Assistive technologies do not announce this message as an alert, although users may navigate via mouse or keyboard to read the message.

In addition, an educator administering a timed assignment can adjust the time limit as needed to accommodate a student.

2.2.2 Pause, Stop, Hide (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.2.2 (Web)
  • 10.2.2.2 (Non-web document)
  • 11.2.2.2 (Open Functionality Software)
  • 11.2.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Not Applicable

Edfinity does not include moving, blinking, scrolling, or auto-updating information.

2.3.1 Three Flashes or Below Threshold (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.3.1 (Web)
  • 10.2.3.1 (Non-web document)
  • 11.2.3.1 (Open Functionality Software)
  • 11.2.3.1(Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Not Applicable

Edfinity does not use flashing interface elements.

2.4.1 Bypass Blocks (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.4.1 (Web)
  • 10.2.4.1 (Non-web document) – Does not apply
  • 11.2.4.1 (Open Functionality Software) – Does not apply
  • 11.2.4.1 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

A hidden link (available to screen readers) allows users to jump to the main content of each page.

2.4.2 Page Titled (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.4.2 (Web)
  • 10.2.4.2 (Non-web document)
  • 11.2.4.2 (Open Functionality Software) - Does not apply
  • 11.2.4.2 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Web pages within Edfinity have descriptive titles that indicate the topic or purpose of each page.

2.4.3 Focus Order (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.4.3 (Web)
  • 10.2.4.3 (Non-web document)
  • 11.2.4.3 (Open Functionality Software)
  • 11.2.4.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity uses a logical tab order through interactive elements such as links and form controls.

Edfinity also uses semantically correct markup, ensuring that the markup matches the visual presentation of content on the page.

2.4.4 Link Purpose (In Context) (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.4.4 (Web)
  • 10.2.4.4 (Non-web document)
  • 11.2.4.4 (Open Functionality Software)
  • 11.2.4.4 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity uses descriptive text or WAI-ARIA techniques, such as adding an “aria-label” attribute to table paging control icons, to identify the purpose of links.

Users may choose to include links in the courses that they build with Edfinity. Edfinity provides capabilities for defining the text of designer-specified link content.

2.5.1 Pointer Gestures (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.5.1 (Web)
  • 10.2.5.1 (Non-web document)
  • 11.2.5.1 (Open Functionality Software)
  • 11.2.5.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 - Does not apply

 Supports

All multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture.

2.5.2 Pointer Cancellation (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.5.2 (Web)
  • 10.2.5.2 (Non-web document)
  • 11.2.5.2 (Open Functionality Software)
  • 11.2.5.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 - Does not apply

 Supports

For functionality that can be operated using a single pointer, Edfinity ensures that the function can be canceled (e.g., drag-and-drop).

2.5.3 Label in Name (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.5.3 (Web)
  • 10.2.5.3 (Non-web document)
  • 11.2.5.3 (Open Functionality Software)
  • 11.2.5.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 - Does not apply

 Supports

For Edfinity user interface components with labels that include text or images of text, the name contains the text that is presented visually.

2.5.4 Motion Actuation (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.2.5.4 (Web)
  • 10.2.5.4 (Non-web document)
  • 11.2.5.4 (Open Functionality Software)
  • 11.2.5.4 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 - Does not apply

 Not Applicable

Edfinity does not use functions that can be operated by device motion or user motion.

3.1.1 Language of Page (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.3.1.1 (Web)
  • 10.3.1.1 (Non-web document)
  • 11.3.1.1.1 (Open Functionality Software)
  • 11.3.1.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity uses the language attribute on the HTML element to specify the default language of a page.

3.2.1 On Focus (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.3.2.1 (Web)
  • 10.3.2.1 (Non-web document)
  • 11.3.2.1 (Open Functionality Software)
  • 11.3.2.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

When a component in an Edfinity user interface receives focus, it does not initiate a change of context.

3.2.2 On Input (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.3.2.2 (Web)
  • 10.3.2.2 (Non-web document)
  • 11.3.2.2 (Open Functionality Software)
  • 11.3.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Changing the setting of a component in an Edfinity user interface does not initiate a change of context.

3.2.6 Consistent Help (Level A)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports

Edfinity offers help mechanisms on all user-authenticated web pages, either via an inline widget or a Help Center link.

3.3.1 Error Identification (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.3.3.1 (Web)
  • 10.3.3.1 (Non-web document)
  • 11.3.3.1.1 (Open Functionality Software)
  • 11.3.3.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity provides capabilities for specifying error text for user interface components configured by application designers with Edfinity.

Additionally, Edfinity uses “aria-invalid” to flag inputs with errors and relay this information to Assistive Technologies.

3.3.2 Labels or Instructions (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.3.3.2 (Web)
  • 10.3.3.2 (Non-web document)
  • 11.3.3.2 (Open Functionality Software)
  • 11.3.3.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity provides capabilities for specifying labels and instructions for user input components configured by users.

Edfinity uses standard HTML and WAI-ARIA attributes to associate labels and instructions to user interface elements. This includes the use of “aria-labelledby” and “aria-describedby” to describe relationships to Assistive Technologies.

3.3.7 Redundant Entry (Level A)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports

Edfinity does not require the user to re-enter previously entered information, except when resetting a password.

4.1.1 Parsing (Level A) (obsolete and removed)

Also applies to:

EN 301 549 Criteria

  • 9.4.1.1 (Web)
  • 10.4.1.1 (Non-web document)
  • 11.4.1.1.1 (Open Functionality Software)
  • 11.4.1.1.2 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity uses semantically-correct markup for all interface elements. In most cases, the markup is programmatically generated to prevent parsing errors.

4.1.2 Name, Role, Value (Level A)

Also applies to:

EN 301 549 Criteria

  • 9.4.1.2 (Web)
  • 10.4.1.2 (Non-web document)
  • 11.4.1.2.1 (Open Functionality Software)
  • 11.4.1.2.2 (Closed Software) – Not required
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies.

Table 2: Success Criteria, Level AA

Criteria Conformance Level Remarks and Explanations

1.2.4 Captions (Live) (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.4.1.2 (Web)
  • 10.4.1.2 (Non-web document)
  • 11.4.1.2.1 (Open Functionality Software)
  • 11.4.1.2.2 (Closed Software) – Not required
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Not Applicable

Edfinity does not use synchronized media.

1.2.5 Audio Description (Prerecorded) (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.4.1.2 (Web)
  • 10.4.1.2 (Non-web document)
  • 11.4.1.2.1 (Open Functionality Software)
  • 11.4.1.2.2 (Closed Software) – Not required
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Not Applicable

Edfinity does not use synchronized media.

1.3.4 Orientation (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.1.3.4 (Web)
  • 10.1.3.4 (Non-web document)
  • 11.1.3.4 (Open Functionality Software)
  • 11.1.3.4 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

 Supports

Edfinity content does not restrict its view and operation to a single display orientation, such as portrait or landscape.

1.3.5 Identify Input Purpose (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.1.3.5 (Web)
  • 10.1.3.5 (Non-web document)
  • 11.1.3.5 (Open Functionality Software)
  • 11.1.3.5 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 - Does not apply

 Supports

The purpose of Edfinity form input collecting information about the user can be programmatically determined.

1.4.3 Contrast (Minimum) (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.1.4.3 (Web)
  • 10.1.4.3 (Non-web document)
  • 11.1.4.3 (Open Functionality Software)
  • 11.1.4.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Partially Supports

The visual presentation of text in Edfinity provides sufficient contrast.

Placeholder text on login and registration pages does not meet necessary contrast requirements.

1.4.4 Resize text (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.1.4.4 (Web)
  • 10.1.4.4 (Non-web document)
  • 11.1.4.4.1 (Open Functionality Software)
  • 11.1.4.4.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity user interfaces support standard zoom capabilities built into modern web browsers and operating systems.

1.4.5 Images of Text (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.1.4.5 (Web)
  • 10.1.4.5 (Non-web document)
  • 11.1.4.5.1 (Open Functionality Software)
  • 11.1.4.5.2 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity does not use images of text by default. Users may choose to include images of text in courses that they build with Edfinity.

1.4.10 Reflow (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.1.4.10 (Web)
  • 10.1.4.10 (Non-web document)
  • 11.1.4.10.1 (Open Functionality Software)
  • 11.1.4.10.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 - Does not apply

 Supports

Edfinity content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions, except for parts of the content which require two-dimensional layout for usage or meaning.

1.4.11 Non-text Contrast (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.1.4.11 (Web)
  • 10.1.4.11 (Non-web document)
  • 11.1.4.11 (Open Functionality Software)
  • 11.1.4.11 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 - Does not apply

 Supports

Visual presentation of user interface components and graphical objects have a contrast ratio of at least 3:1 against an adjacent color.

1.4.12 Text Spacing (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.1.4.12 (Web)
  • 10.1.4.12 (Non-web document)
  • 11.1.4.12 (Open Functionality Software)
  • 11.1.4.12 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 - Does not apply

 Supports

Edfinity uses cascading stylesheets (CSS). Modification of styles for line height, spacing following paragraphs, letter spacing, and word spacing would not result in a loss of content or functionality.

1.4.13 Content on Hover or Focus (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.1.4.13 (Web)
  • 10.1.4.13 (Non-web document)
  • 11.1.4.13 (Open Functionality Software)
  • 11.1.4.13 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 - Does not apply

 Supports

Edfinity uses the ARIA "tooltip" role as well as hover and focus pseudo classes to ensure that, where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the mechanism is dismissible, hoverable, and persistent.

2.4.5 Multiple Ways (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.4.5 (Web)
  • 10.2.4.5 (Non-web document) – Does not apply
  • 11.2.4.5 (Open Functionality Software) – Does not apply
  • 11.2.4.5 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity provides capabilities for incorporating navigation links and search functions in user interfaces built with Edfinity. Users may choose to implement these techniques as they see fit.

2.4.6 Headings and Labels (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.4.6 (Web)
  • 10.2.4.6 (Non-web document)
  • 11.2.4.6 (Open Functionality Software)
  • 11.2.4.6 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity uses semantically-correct markup for all interface elements, including headings and labels.

For users building courses within Edfinity, Edfinity provides capabilities for defining descriptive headings and labels.

2.4.7 Focus Visible (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.2.4.7 (Web)
  • 10.2.4.7 (Non-web document)
  • 11.2.4.7 (Open Functionality Software)
  • 11.2.4.7 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity uses visual changes to elements to indicate the current position of focus.

2.5.7 Dragging Movements (Level AA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports

Edfinity ensures that all dragging operations can be achieved by a single pointer without dragging unless dragging is essential.

2.5.8 Target Size (Minimum) (Level AA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports

Edfinity ensures the size of the target for pointer inputs is at least 24 by 24 CSS pixels, with exceptions due to spacing, equivalent controls, inline text, user agent control, or essential presentation.

2.4.11 Focus Not Obscured (Minimum) (Level AA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports

Edfinity ensures no part of user interface components are hidden by author-created content.

3.1.2 Language of Parts (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.3.1.2 (Web)
  • 10.3.1.2 (Non-web document)
  • 11.3.1.2 (Open Functionality Software) – Does not apply
  • 11.3.1.2 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Does Not Support

In Edfinity, the language of a page can be programmatically determined. However, there is no mechanism to specify different languages for subsets of a page. Even though the language of different parts of a page cannot be programmatically determined, all content specified by users, regardless of language, renders in Edfinity user interfaces.

3.2.3 Consistent Navigation (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.3.2.3 (Web)
  • 10.3.2.3 (Non-web document) – Does not apply
  • 11.3.2.3 (Open Functionality Software) – Does not apply
  • 11.3.2.3 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity uses the same navigation mechanisms across pages.

3.2.4 Consistent Identification (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.3.2.4 (Web)
  • 10.3.2.4 (Non-web document) – Does not apply
  • 11.3.2.4 (Open Functionality Software) – Does not apply
  • 11.3.2.4 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity provides a standard set of tools for course designers, ensuring consistent functionality and presentation across pages.

3.3.3 Error Suggestion (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.3.3.3 (Web)
  • 10.3.3.3 (Non-web document)
  • 11.3.3.3 (Open Functionality Software)
  • 11.3.3.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

When a form is not successfully submitted, errors are described for the affected inputs along with information on how to correct the errors.

3.3.4 Error Prevention (Legal, Financial, Data)

Also applies to:

EN 301 549 Criteria

  • 9.3.3.4 (Web)
  • 10.3.3.4 (Non-web document)
  • 11.3.3.4 (Open Functionality Software)
  • 11.3.3.4 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)
 Supports

Edfinity user interfaces incorporate methods such as checking for input errors, ensuring that submissions are reversible, and allowing users to review and confirm information prior to submission.

3.3.8 Accessible Authentication (Minimum) (Level AA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports

Edfinity allows passwords to be supplied via cut and paste or from a password manager.

4.1.3 Status Messages (Level AA)

Also applies to:

EN 301 549 Criteria

  • 9.4.1.3 (Web)
  • 10.4.1.3 (Non-web document) – Does not apply
  • 11.4.1.3 (Open Functionality Software) – Does not apply
  • 11.4.1.3 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 - Does not apply

 Supports

Edfinity uses ARIA roles "alert" and "status" to present messages to the user that can be programmatically determined.

Table 3: Success Criteria, Level AAA

Criteria Conformance Level Remarks and Explanations

1.2.6 Sign Language (Prerecorded) (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Not Applicable Edfinity does not include audio content by default.

1.2.7 Extended Audio Description (Prerecorded) (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Not Applicable Edfinity does not include audio content by default.

1.2.8 Media Alternative (Prerecorded) (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Not Applicable Edfinity does not include audio content by default.

1.2.9 Audio-only (Live) (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Not Applicable Edfinity does not include audio content by default.

1.3.6 Identify Purpose (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports The purpose of many elements on a page can be programmatically determined.

1.4.6 Contrast Enhanced (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports The visual presentation of text and images of text has a contrast ratio of at least 7:1, with exception of large text (4.5:1 ratio) and decorative text or images of text.

1.4.7 Low or No Background Audio (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Not Applicable Edfinity does not include audio content by default.

1.4.8 Visual Presentation (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Partially Supports

For the most part, visually rendered text is presented in such a manner that it can be perceived without its layout interfering with its readability.

  • Edfinity does not allow a user to select the color of text or the background.
  • Text can be resized without requiring scrolling.
  • Text is not justified (aligned to both the left and the right margins).
  • Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing.

1.4.9 Images of Text (No Exception) Control (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.

2.1.3 Keyboard (No Exception) (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.

2.2.3 No Timing (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events.

2.2.4 Interruptions (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.

2.2.5 Re-authenticating (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.
2.2.6 Timeouts (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports Edfinity does not use timeouts.

2.3.2 Three Flashes (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports Edfinity pages do not contain anything that flashes more than three times in any one second period.
2.3.3 Animation from Interactions (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Partially Supports Edfinity does not generally use animation on pages. On the assignment editor page, however, there is a publish button that pulses gently. This cannot be disabled.

2.4.8 Location (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports Edfinity makes use of context-specific links and breadcrumb trails to help users orient themselves when navigating around the site.

2.4.9 Link Purpose (Link Only) (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports Edfinity uses mechanisms like aria-label and descriptive text on links to allow their purpose to be identified by text alone.

2.4.10 Section Headings (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports Section headings are used to organize content.

2.4.12 Focus Not Obscured (Enhanced) (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports

Edfinity ensures no part of user interface components are hidden by author-created content.

2.4.12 Focus Appearance (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports

Edfinity uses a keyboard focus indicator that has the appropriate thickness and contrast.

2.5.5 Target Size (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Partially Supports Within the student user interface, the size of the target for pointer inputs is at least 44 by 44 CSS pixels. Witin the educator interface, toolbar buttons in some tabbed interfaces do not quite meet these requirements.

2.5.6 Concurrent Input Mechanisms (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports Users can interact with web content with whichever input mechanism is preferred and available to them. They may switch between input mechanisms when they desire or the circumstances require it.

3.1.3 Unusual Words (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports Edfinity offers subject-based content in which text may include a definition for a word used in a way deemed unusual to those unfamiliar with the subject. In these instances, definitions are provided in associated instructional content or help tools included within assessment items.

3.1.4 Abbreviations (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports When an abbreviation is used, the expanded form of the abbreviation is also provided. For user-specified content, Edfinity allows authors to present abbreviations in their expanded form.

3.1.5 Reading Level (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Partially Supports When working with assessment items, students are provided with contextual hints and syntax warnings for incorrect answers which may indicate a lack of understanding.

3.1.6 Pronunciation (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Does Not Support Edfinity does not provide a mechanism for identifying the specific pronunciation of words.

3.2.5 Change on Request (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports Changes of context are initiated only by user request. Edfinity uses standard redirects and fully supports use of the back button in the browser.

3.3.9 Accessible Authentication (Enhanced) (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports

Edfinity does not require a cognitive function test in order to log in.

3.3.5 Help (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports Context-sensitive help is available to help users perform specific operations.

3.3.6 Error Prevention (All) (Level AAA)

Also applies to:

EN 301 549 Criteria – Does not apply

Revised Section 508 - Does not apply

 Supports

For pages that require the user to submit information, at least one of the following is true:

  • Reversible: Submissions are reversible.
  • Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
  • Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

Revised Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria Conformance Level Remarks and Explanations
302.1 Without Vision Supports Edfinity uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies.
302.2 With Limited Vision Supports Edfinity supports standard browser magnification and contrast adjustments.
302.3 Without Perception of Color Supports Color is only used as a decorative or supplemental attribute of user interface elements. A textual representation is always used as the primary mechanism for conveying information.
302.4 Without Hearing Not Applicable Edfinity does not include audio-only features that require hearing to be used.
302.5 With Limited Hearing Not Applicable Edfinity does not include audio-only features that require hearing to be used.
302.6 Without Speech Not Applicable Edfinity does not require speech input.
302.7 With Limited Manipulation Supports Edfinity supports standard input mechanisms such as user-provided keyboards and pointing devices. Usage of the product does not require fine motor controls nor simultaneous actions.
302.8 With Limited Reach and Strength Not Applicable
302.9 With Limited Language, Cognitive, and Learning Abilities Supports

Chapter 4: Hardware

Notes: Edfinity is a web software application and is not subject to the requirements of this section.

Chapter 5: Software

Criteria Conformance Level Remarks and Explanations
501.1 Scope – Incorporation of WCAG 2.2 AA See WCAG 2.2 section See information in WCAG 2.2 section.
502 Interoperability with Assistive Technology Heading cell – no response required Heading cell – no response required
502.2.1 User Control of Accessibility Features Not Applicable Edfinity is not considered platform software as defined by Section 508.
502.2.2 No Disruption of Accessibility Features Supports Edfinity is compatible with operating system and browser accessibility features configured by the user.
502.3 Accessibility Services Heading cell – no response required Heading cell – no response required
502.3.1 Object Information Supports Edfinity uses WAI-ARIA attributes to describe the role, state, and description of user interface elements to Assistive Technologies. The includes the use of “role”, “aria-invalid”, and “aria-required” attributes.
502.3.2 Modification of Object Information Supports Edfinity uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies.
502.3.3 Row, Column, and Headers Supports Edfinity uses standard HTML attributes to define table structure and relationships, including column and row headers, to Assistive Technologies.
502.3.4 Values Supports Edfinity uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies.
502.3.5 Modification of Values Supports Edfinity uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies.
502.3.6 Label Relationships Supports Edfinity uses standard HTML and WAI-ARIA attributes to describe label relationships of user interface elements to Assistive Technologies. This includes the use of “<label>” and “aria-labelledby” attributes.
502.3.7 Hierarchical Relationships Supports Edfinity uses standard HTML markup to express hierarchical relationships.
502.3.8 Text Supports Edfinity renders strings as plain text values in HTML for maximum compatibility with assistive technologies.
502.3.9 Modification of Text Supports Edfinity renders strings as plain text values in HTML for maximum compatibility with assistive technologies.
502.3.10 List of Actions Supports Edfinity uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies.
502.3.11 Actions on Objects Supports Edfinity uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies.
502.3.12 Focus Cursor Supports Edfinity uses visual changes to elements to indicate the current position of focus.
502.3.13 Modification of Focus Cursor Supports Edfinity uses standard HTML elements with standard cursor controls for user input.
502.3.14 Event Notification Partially Supports

For assignment sessions that specify a time limit, Edfinity has a timeout alert to notify students when the session is about to end. Assistive technologies do not announce this message as an alert, although users may navigate via mouse or keyboard to read the message.

In addition, an educator administering a timed assignment can adjust the time limit as needed to accommodate a student.
502.4 Platform Accessibility Features Not Applicable Edfinity is not considered platform software as defined by Section 508.
503 Applications Heading cell – no response required Heading cell – no response required
503.2 User Preferences Supports Edfinity respects user preferences from platform or OS settings. For example, if a user enables high contrast mode, Edfinity user interfaces will display with high contrast.
503.3 Alternative User Interfaces Not Applicable Edfinity does not provide any alternative user interfaces that function as assistive technology.
503.4 User Controls for Captions and Audio Description Heading cell – no response required Heading cell – no response required
503.4.1 Caption Controls Does Not Support Edfinity does not provide capabilities for captioning or defining audio descriptions of designer-specified video content.
503.4.2 Audio Description Controls Does Not Support Edfinity does not provide capabilities for captioning or defining audio descriptions of designer-specified video content.
504 Authoring Tools Heading cell – no response required Heading cell – no response required
504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) See WCAG 2.2 section See information in WCAG 2.2 section.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion Not Applicable
504.2.2 PDF Export Not Applicable
504.3 Prompts Not Applicable
504.4 Templates Not Applicable

Chapter 6: Support Documentation and Services

Notes: This report covers accessibility conformance for Edfinity and does not discuss Documentation or Support Services.

EN 301 549 Report

Chapter 4: 4.2 Functional Performance Statements (FPS)

Criteria Conformance Level Remarks and Explanations
4.2.1 Usage without vision Supports Edfinity uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies.
4.2.2 Usage with limited vision Supports Edfinity supports standard browser magnification and contrast adjustments.
4.2.3 Usage without perception of colour Supports Colour is only used as a decorative or supplemental attribute of user interface elements. A textual representation is always used as the primary mechanism for conveying information.
4.2.4 Usage without hearing Not Applicable Edfinity does not include audio-only features that require hearing to be used.
4.2.5 Usage with limited hearing Not Applicable Edfinity does not include audio-only features that require hearing to be used.
4.2.6 Usage without vocal capability Not Applicable Edfinity does not require speech input.
4.2.7 Usage with limited manipulation or strength Supports Edfinity supports standard input mechanisms such as user-provided keyboards and pointing devices.
4.2.8 Usage with limited reach Not Applicable
4.2.9 Minimize photosensitive seizure triggers Supports Edfinity does not include visual features with flashing that could trigger seizures.
4.2.10 Usage with limited cognition Supports Edfinity uses a logical focus order, and provides capabilities for specifying error text for user interface components configured by application designers.
4.2.11 Privacy Supports Edfinity does not impede usage of standard privacy controls alongside assistive technologies. For example, users can connect a headset for private listening to screen reader announcements.

Chapter 5: Generic Requirements

Notes: Edfinity supports standard assistive technologies and is therefore not subject to the Closed Functionality criteria described in this Chapter.

Chapter 6: ICT with Two-Way Voice Communication

Notes: Edfinity does not offer two-way voice communication and is therefore not subject to the requirements of this section.

Chapter 7: ICT with Video Capabilities

Notes: Edfinity does not include video content. However, users may choose to include video content courses that they build with Edfinity. Edfinity does not provide capabilities for captioning or defining audio descriptions of user-specified video content.

Criteria Conformance Level Remarks and Explanations
7.1 Caption processing technology Heading cell – no response required Heading cell – no response required
7.1.1 Captioning playback Does Not Support
7.1.2 Captioning synchronization Does Not Support
7.1.3 Preservation of captioning Does Not Support
7.2.1 Audio description playback Does Not Support
7.2.2 Audio description synchronization Does Not Support
7.2.3 Preservation of audio description Does Not Support
7.3 User controls for captions and audio description Does Not Support

Chapter 8: Hardware

Notes: Edfinity is a web software application and is not subject to the requirements of this section.

Chapter 9: Web (see WCAG 2.2 section)

Chapter 10: Non-web Documents

Notes: Edfinity does not include non-web documents and is therefore not subject to the requirements of this section.

Chapter 11: Software

Criteria Conformance Level Remarks and Explanations
11.2.1 Software success criteria (excluding closed functionality) See WCAG 2.2 section See information in WCAG 2.2 section
11.2.2 Software success criteria (closed functionality) See WCAG 2.2 section See information in WCAG 2.2 section
11.3 Interoperability with assistive technology Heading cell – no response required Heading cell – no response required
11.3.1 Closed functionality (informative) Heading cell – no response required Heading cell – no response required
11.3.2 Accessibility services Heading cell – no response required Heading cell – no response required
11.3.2.1 Platform accessibility service support for software that provides a user interface See 11.3.2.5 through 11.3.2.17 See information in 11.3.2.5 through 11.3.2.17
11.3.2.2 Platform accessibility service support for assistive technologies See 11.3.2.5 through 11.3.2.17 See information in 11.3.2.5 through 11.3.2.17
11.3.2.3 Use of accessibility services Supports Edfinity uses standard platform accessibility services.
11.3.2.4 Assistive technology Not Applicable Edfinity is not itself an assistive technology.
11.3.2.5 Object information Supports Edfinity uses WAI-ARIA attributes to describe the role, state, and description of user interface elements to Assistive Technologies. The includes the use of “role”, “aria-invalid”, and “aria-required” attributes.
11.3.2.6 Row, column, and headers Supports Edfinity uses standard HTML attributes to define table structure and relationships, including column and row headers, to Assistive Technologies.
11.3.2.7 Values Supports
11.3.2.8 Label relationships Supports Edfinity uses standard HTML and WAI-ARIA attributes to describe label relationships of user interface elements to Assistive Technologies. This includes the use of “<label>” and “aria-labelledby” attributes.
11.3.2.9 Parent-child relationships Supports
11.3.2.10 Text Supports
11.3.2.11 List of available actions Supports
11.3.2.12 Execution of available actions Supports
11.3.2.13 Tracking of focus and selection attributes Supports
11.3.2.14 Modification of focus and selection attributes Supports
11.3.2.15 Change notification Supports
11.3.2.16 Modifications of states and properties Supports
11.3.2.17 Modifications of values and text Supports
11.4 Documented accessibility usage Heading cell – no response required Heading cell – no response required
11.4.1 User control of accessibility features Not Applicable Edfinity is not considered platform software as defined by EN 301 549.
11.4.2 No disruption of accessibility features Supports
11.5 User preferences Supports Edfinity respects user preferences from platform or OS settings. For example, if a user enables high contrast mode, Edfinity user interfaces will display with high contrast.