VISIARC Progress™
Accessability Statement
VISIARC Progress Voluntary Product Accessibility Template (VPAT)
This Voluntary Product Accessibility Template, or VPAT, is a tool that administrators and decision-makers can use to evaluate VISIARC Progress conformance with the accessibility standards under US GCA's Section 508 of the Rehabilitation Act and WCAG 2.2. As well, VISIARC Progress is conformant with the Directive (EU) 2016/2102 of the European Parliament and of the Council.WCAG 2.2 A & AA Conformance Report
This table below documents the conformance of VISIARC Progress (including web content, electronic documents, software components, and authoring systems) with WCAG 2.2.
Principle 1: Perceivable. | ||
| Criteria | Conformance | Level Remarks & Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supported | Non-text content that is presented to the user has a text alternative that serves the equivalent purpose. |
| 1.2.1 Prerecorded Audio-only and Video-only | Not Applicable | Prerecorded audio or video are not provided by VISIARC Progress. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | Prerecorded audio or video are not provided by VISIARC Progress. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | Prerecorded audio or video are not provided by VISIARC Progress. |
| 1.2.4 Captions (Live) | Not Applicable | Prerecorded audio or video are not provided by VISIARC Progress. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | Prerecorded audio or video are not provided by VISIARC Progress. |
| 1.3.1 Info and Relationships | Supported | Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. |
| 1.3.2 Meaningful Sequence | Supported | When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. |
| 1.3.3 Sensory Characteristics | Supported | Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound. |
| 1.3.4 Orientation | Supported | Content does not restrict its view and operation to a single display orientation, such as portrait or landscape. |
| 1.3.5 Identify Input Purpose | Not Applicable | Input fields are not provided by VISIARC Progress. |
| 1.4.1 Use of Color | Supported | Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. |
| 1.4.2 Audio Control | Not Applicable | Prerecorded audio is not provided by VISIARC Progress. |
| 1.4.3 Contrast (Minimum) | Supported | The visual presentation of text and images of text has a contrast ratio of at least 4.5:1. |
| 1.4.4 Resize text | Supported | Except for captions, text can be resized without assistive technology up to 200 percent without loss of content or functionality. |
| 1.4.5 Images of Text | Not Applicable | Images of text are not provided by VISIARC Progress. |
| 1.4.10 Reflow | Supported | Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions. |
| 1.4.11 Non-text Contrast | Supported | The visual presentation of graphical objects and user interface elements have a contrast ratio of at least 3:1 against adjacent color(s). |
| 1.4.12 Text Spacing | Supported | VISIARC Progress users can change text style properties without loss of content or functionality. |
| 1.4.13 Content on Hover or Focus | Supported | VISIARC Progress content appearing while hovered is dismissible via the escape key and persistent while hovered. |
Principle 2: Operable. | ||
| Criteria | Conformance | Level Remarks & Explanations |
|---|---|---|
| 2.1.1 Keyboard | Supported | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. |
| 2.1.2 No Keyboard Trap | Supported | Focus can be moved to a component of the page using a keyboard interface and focus can be moved away from that component using only a keyboard interface. |
| 2.1.4 Character Key Shortcuts | Not Applicable | No Keyboard Shortcuts exist in VISIARC Progress. |
| 2.2.1 Timing Adjustable | Not Applicable | VISIARC Progress does not time-out interface elements or content. |
| 2.2.2 Pause, Stop, Hide | Not Applicable | VISIARC Progress does not contain moving, blinking, scrolling, or auto-updating content that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content. |
| 2.3.1 Three Flashes or Below Threshold | Not Applicable | VISIARC Progress does not contain any blinking content. |
| 2.4.1 Bypass Blocks | Not Applicable | VISIARC Progress does not contain content that is repeated on multiple Web pages. |
| 2.4.2 Page Titled | Not Applicable | VISIARC Progress does not contain web pages with titles. |
| 2.4.3 Focus Order | Supported | VISIARC Progress can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. |
| 2.4.4 Link Purpose (In Context) | Supported | The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. |
| 2.4.5 Multiple Ways | Not Applicable | VISIARC Progress does not contain multiple pages. |
| 2.4.6 Headings and Labels | Supported | Headings and labels describe topic or purpose. |
| 2.4.7 Focus Visible | Supported | Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. |
| 2.5.1 Pointer Gestures | Not Applicable | VISIARC Progress does not contain navigation by multipoint or path-based gestures. |
| 2.5.2 Pointer Cancellation | Supported | No actions in VISIARC Progress complete on mouse-down, and thus can be aborted by moving the mouse away from the button or target area before mouse-up. |
| 2.5.3 Label in Name | Supported | For 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 | Not Applicable | VISIARC Progress does not contain any motion operations. |
Principle 3: Understandable. | ||
| Criteria | Conformance | Level Remarks & Explanations |
|---|---|---|
| 3.1.1 Language of Page | Not Applicable | VISIARC Progress operates within Canvas Web pages, which have a language set which can be programmatically determined. |
| 3.1.2 Language of Parts | Not Applicable | Multi-language content is not provided by VISIARC Progress. |
| 3.2.1 On Focus | Supported | When any user interface component receives focus, it does not initiate a change of context. |
| 3.2.2 On Input | Not Applicable | VISIARC Progress does not contain any input components. |
| 3.2.3 Consistent Navigation | Supported | Repeated components are presented in the same relative order each time they appear. |
| 3.2.4 Consistent Identification | Supported | Components that have the same functionality are identified consistently. |
| 3.3.1 Error Identification | Not Applicable | VISIARC Progress does not contain input elements. |
| 3.3.2 Labels or Instructions | Not Applicable | VISIARC Progress does not contain input elements. |
| 3.3.3 Error Suggestion | Not Applicable | VISIARC Progress does not contain input elements. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Not Applicable | VISIARC Progress does not contain input elements. |
Principle 4: Robust. | ||
| Criteria | Conformance | Level Remarks & Explanations |
|---|---|---|
| 4.1.1 Parsing | Supported | In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. |
| 4.1.2 Name, Role, Value | Supported | For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. |
| 4.1.3 Status Messages | Not Applicable | Status messages are not used in VISIARC Progress. |
Functional Performance Criteria (FPC) | ||
| Criteria | Conformance | Level Remarks & Explanations |
|---|---|---|
| Without Vision | Supported | VISIARC Progress works well with screen readers. |
| With Limited Vision | Supported | VISIARC Progress supports screen magnification and browser-provided zoom functionality. |
| Without Perception of Color | Supported | VISIARC Progress does not require color perception for operation. |
| Without Hearing | Not Applicable | VISIARC Progress does not use any audio for its default operation. |
| With Limited Hearing | Not Applicable | VISIARC Progress does not use any audio for its default operation. |
| Without Speech | Not Applicable | VISIARC Progress does not require speech for operation. |
| With Limited Manipulation | Supported | VISIARC Progress does not require fine motor control or simultaneous actions. It is accessible via keyboard and touch devices. |
| With Limited Reach and Strength | Supported | VISIARC Progress does not require fine motor control or simultaneous actions. It is accessible via keyboard and touch devices. |
| With Limited Language, Cognitive, and Learning Abilities | Supported | VISIARC Progress provides an easy-to-use interface for users with cognitive or learning disabilities. |
