EchoExam
Accessibility Conformance Report published by Echo360
Partial extraction. We read 19 of 31 Level A and 15 of 24 Level AA criteria from this document (62% coverage). The remainder are missing from our extraction, not necessarily from Echo360's report — their table layout defeated our parser. Treat the figures below as incomplete and read the source document for the full picture.
Conformance by level
Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.
Level A — 19 criteria
- Supports
- 12
- Partially supports
- 5
- Does not support
- 2
- Not applicable
- 0
- Not evaluated
- 0
Level AA — 15 criteria
- Supports
- 8
- Partially supports
- 5
- Does not support
- 2
- Not applicable
- 0
- Not evaluated
- 0
Source: View the original report published by Echo360.
These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.
All reported criteria (34)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Does Not Support | Web: Most non-text content in the product does not |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Supports | Web: The product does not contain prerecorded audio- only or video-only media. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Supports | Web: The product does not contain any prerecorded video media that requires audio descriptions or a media alternative. |
| 1.3.1 | Info and Relationships | A | Does Not Support | Web: The product does not consistently ensure |
| 1.3.2 | Meaningful Sequence | A | Supports | Web: The product ensures that a correct reading order can be programmatically determined for content whose presentation sequence affects its meaning. |
| 1.4.1 | Use of Color | A | Supports | Web: The product does not use color as the only visual means of conveying information, indicating an action, or prompting a response. |
| 2.1.1 | Keyboard | A | Partially Supports | Web: In some instances, the product ensures that interactive content and functionality is accessible and operable using a keyboard or keyboard emulator. Exceptions include: • On the My Library and Resources screen there are interactive buttons that cannot be operated with the single time "Enter or Spacebar" key, When the user presses double time "Enter or Spacebar" key then only it is activated. • On the Test Editor screen there are interactive controls that cannot be navigated to and/or operated with the keyboard. • On the Exam screen there are interactive controls that cannot be navigated to and/or operated with the keyboard. |
| 2.1.4 | Character Key Shortcuts | A | Supports | Web: The product does not use character key shortcuts. |
| 2.2.2 | Pause, Stop, Hide | A | Supports | Web: The product does not contain content that moves, blinks, scrolls, or auto-updates. |
| 2.4.1 | Bypass Blocks | A | Partially Supports | Web: In most instances, the product provides skip links and other mechanisms to bypass blocks of content repeated on multiple screens. Exceptions include: • In the Header and Navigation there is no available method to bypass repeated blocks of content and go directly to the beginning of the main content. |
| 2.4.3 | Focus Order | A | Partially Supports | Web: In some instances, screens of the product can be navigated sequentially with a focus order that matches the logical reading order. Exceptions include: • On the Question Editor screen the elements don't have a logical navigation sequence using only the keyboard. • On the Exam screen Tab focus moves to plain text that should not receive focus due to its state. • On the Course Details screen focus moves to the top of the page when 'Instructors' combo box is collapsed creating an illogical focus order. |
| 2.5.1 | Pointer Gestures | A | Supports | Web: The product does not require multipoint or path- based gestures for operation. |
| 2.5.2 | Pointer Cancellation | A | Supports | Web: The product ensures that functionality on pointer |
| 2.5.3 | Label in Name | A | Partially Supports | Web: In some instances, the product ensures that when interface components have visual labels that include text, the provided accessible name contains the visually presented text. Exceptions include: • On the Login screen there are form controls without a programmatically associated label describing their purpose. • On the Print Test screen there are form controls with visual labels that are not programmatically associated with the control. • On the Course Details screen there are form controls with visual labels that are not programmatically associated with the control. |
| 3.1.1 | Language of Page | A | Supports | Web: The product ensures that the default human language used on each screen can be programmatically determined. |
| 3.2.2 | On Input | A | Supports | Web: 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. |
| 3.3.1 | Error Identification | A | Supports | Web: 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. |
| 3.3.7 | Redundant Entry | A | Supports | Web: The product does not request redundant user- entered information in multi-step processes. |
| 4.1.2 | Name, Role, Value | A | Partially Supports | Web: In some instances, the product contains user interface components whose name, role, state, and value can be programmatically determined. Exceptions include: • On the Login screen there are form controls without a programmatically associated label describing their purpose. • On the Question Editor screen there are elements whose ARIA role is not contained by parent. The element does not include ARIA roles necessary to communicate the relationship to the screen reader with secondary elements. • On the Exam Report Roster screen there are tabs without appropriate name, role, and/or state information. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Supports | Web: The product does not contain any prerecorded synchronized media (video with audio) that requires audio descriptions. |
| 1.3.5 | Identify Input Purpose | AA | Partially Supports | Web: In most instances, the product ensures that the purpose of input fields that request information about the user, such as name or email, can be programmatically determined. Exceptions include: • On the Login screen there are common form controls that lack a programmatic way to communicate purpose, such as an autocomplete attribute. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Web: In some instances, the visual presentation of |
| 1.4.4 | Resize text | AA | Partially Supports | Web: In some instances, the product allows text to be resized without assistive technology up to 200 percent without loss of content or functionality. Exceptions include: • On the Login screen the user-scalable parameter set to "no"/maximum-scale less than 2 within the <meta name="viewport"> tag is disabling zooming on the page. • In the Header and Navigation component there is content that disappears and overlaps when viewing the page at 200% browser zoom and a 1280-pixel viewport width. • On the My Library and Publisher Titles screen there is content that is cut off when viewing the page at 200% browser zoom and a 1280- pixel viewport width. |
| 1.4.10 | Reflow | AA | Does Not Support | Web: Screens across the product do not consistently 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. Examples include: • On the My Library screen there is content that requires horizontal scrolling to view when the page has a viewport width of 320 CSS pixels. • On the My Courses screen there is content that requires horizontal scrolling to view when the page has a viewport width of 320 CSS pixels. • On the Course Details screen the content of the page requires horizontal scrolling to view when the page has a viewport width of 320 CSS pixels. |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Web: In some instances, the visual presentation of |
| 1.4.12 | Text Spacing | AA | Supports | Web: The product supports user changes in text style properties, such as line height or text spacing, without loss of content or functionality. |
| 1.4.13 | Content on Hover or Focus | AA | Supports | Web: Content in the product that is triggered by hover |
| 2.4.5 | Multiple Ways | AA | Supports | Web: The product provides multiple ways to navigate through screens in the product. |
| 2.4.7 | Focus Visible | AA | Partially Supports | Web: In some instances, the product provides a visible indication of keyboard focus for elements on each screen. Exceptions include: • On the My Library and Publisher Titles screen there are interactive controls without a visible keyboard focus indicator. • On the My Reports screen there are interactive controls without a visible keyboard focus indicator. • On the Learner Performance screen there are interactive controls without a visible keyboard focus indicator. |
| 2.5.7 | Dragging Movements | AA | Supports | Web: When dragging movement is needed for operation the product allows the functionality to be accomplished by a single pointer without dragging. |
| 3.1.2 | Language of Parts | AA | Supports | Web: Screens of the product present content in a single language. |
| 3.2.4 | Consistent Identification | AA | Supports | Web: The product ensures that components with the same functionality are identified consistently across screens of the product. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | Web: 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. |
| 4.1.3 | Status Messages | AA | Does Not Support | Web: The product does not consistently provide status messages that can be presented to assistive technologies without receiving focus. Examples include: • On the My Library and Questions screen there are search results that appear but are not announced to screen reader users. • On the Exams list screen, the status message is not announced by the screen reader after choosing filter. • On the Results screen there are search results that appear but are not announced to screen reader users. |
Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.
Get told when this changes
This report is dated December 2024. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.
Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.