WCAG 2.x Report
Tables 1 and 2 also document conformance with:
-
EN 301 549: Clause 9 - Web, Clauses 10.1-10.4 of Clause 10 - Non-Web documents, Clauses 11.1-11.4 and 11.8.2 of Clause 11 - Software, and Clauses 12.1.2 and 12.2.4 of Clause 12 - Documentation and support services
-
Revised Section 508: Chapter 5 - 501.1 Scope and 504.2 Content Creation or Editing, and Chapter 6 - 602.3 Electronic Support Documentation
Note: When reporting on conformance with the WCAG 2.x 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
Notes: WCAG 2.2 Success Criteria and levels used.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) | Supports | Non-text content that is presented to the user has a text alternative that serves the equivalent purpose |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Not Applicable | Prerecorded audio-only files are not present. |
| 1.2.2 Captions (Prerecorded) (Level A) | Not Applicable | Prerecorded videos are not present. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Not Applicable | Prerecorded videos are not present, so audio description is not required. |
| 1.3.1 Info and Relationships (Level A) | Supports | Information, structure, and relationships conveyed through presentation can be programmatically determined |
| 1.3.2 Meaningful Sequence (Level A) | Supports | The reading and navigation order is logical and intuitive. |
| 1.3.3 Sensory Characteristics (Level A) | Partially Supports | Most instructions do not rely on sensory characteristics of components such as shape, color, size, or visual location. Exception is some references in Help documentation to main navigation menu as "left hand" navigation, to distinguish from global / user account navigation in header. Recommended for change to "application navigation" and "global navigation". |
| 1.4.1 Use of Color (Level A) | Partially Supports, see Note | Color is not generally used as the only method to convey information, prompt a response, or distinguish visual elements. Charts and color coding, such in dashboards, need remediation in several places, however the information conveyed in the charts (such as number of failures) is accessible and presented in text. |
| 1.4.2 Audio Control (Level A) | Not Applicable | Audio is not present. |
| 2.1.1 Keyboard (Level A) | Supports | Functionality is available using the keyboard. |
| 2.1.2 No Keyboard Trap (Level A) | Supports | Keyboard focus is not locked or trapped. |
| 2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2) | Not Applicable | Character key shortcuts are not present. |
| 2.2.1 Timing Adjustable (Level A) | Partially Supports, see Note | Administrator roles can adjust session time periods if necessary for checkout; if a checkout expires another checkout can be done. |
| 2.2.2 Pause, Stop, Hide (Level A) | Not Applicable | Moving, blinking and scrolling information is not present. |
| 2.3.1 Three Flashes or Below Threshold (Level A) | Not Applicable | Product does not contain flashing content. |
| 2.4.1 Bypass Blocks (Level A) | Supports | Supports via "Skip To" menu, with navigation and main landmarks. |
| 2.4.2 Page Titled (Level A) | Supports | Pages use descriptive titles that accurate describe the contents. |
| 2.4.3 Focus Order (Level A) | Supports | The navigation order of interactive elements (such as links, buttons or form elements) is logical and preserves meaning and operability. Exception of application "left hand" navigation as described in Notes Section |
| 2.4.4 Link Purpose (In Context) (Level A) | Supports | The purpose of links can be determined from the link text alone or from the context in which it appears. |
| 2.5.1 Pointer Gestures (Level A 2.1 and 2.2) | Not Applicable | No multipoint gestures have been identified in the product. |
| 2.5.2 Pointer Cancellation (Level A 2.1 and 2.2) | Not Applicable | |
| 2.5.3 Label in Name (Level A 2.1 and 2.2) | Supports | Visible text labels match accessible names. |
| 2.5.4 Motion Actuation (Level A 2.1 and 2.2) | Not Applicable | No motion-triggered functionality has been identified in the product. |
| 3.1.1 Language of Page (Level A) | Supports | The language of each page can be determined programmatically. |
| 3.2.1 On Focus (Level A) | Supports | |
| 3.2.2 On Input (Level A) | Supports | |
| 3.2.6 Consistent Help (Level A 2.2 only) | Supports | The global help menu is consistently placed in the header. The contextual help links are consistently placed following the page title. |
| 3.3.1 Error Identification (Level A) | Supports | Form error messages identify the field or control where the error occurred. |
| 3.3.2 Labels or Instructions (Level A) | Supports | Form labels and instructions are provided so users know what input data is expected. |
| 3.3.7 Redundant Entry (Level A 2.2 only) | Supports | Redundant entry of information is not required. |
| 4.1.2 Name, Role, Value (Level A) | Partially Supports | The name, role, state and value of most user interface components can be programmatically determined. Some dynamic content and updates may not be announced properly. Further ARIA supports are implemented for clarity when issues are identified or reported. |
Table 2: Success Criteria, Level AA
Notes: WCAG 2.2 Success Criteria and levels used.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) | Not Applicable | No live presentations hosted. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Not Applicable | Pre-recorded media files are not present. |
| 1.3.4 Orientation (Level AA 2.1 and 2.2) | Not Applicable | |
| 1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2) | Supports | The purpose of input fields can be determined. |
| 1.4.3 Contrast (Minimum) (Level AA) | Supports | Text content in the application meets the required contrast ratios. |
| 1.4.4 Resize text (Level AA) | Supports | Text can be resized without loss of content or functionality up to 400% zoom of original size. Data tables require horizontal scrolling within Success Criteria parameters. |
| 1.4.5 Images of Text (Level AA) | Supports | Images of text are not used apart from in allowed logo images. |
| 1.4.10 Reflow (Level AA 2.1 and 2.2) | Supports | Data tables might require horizontal scrolling depending on size of browser window/viewport. Data tables are an exception to the 1.4.10 rule as noted by WCAG Success Criteria parameters. |
| 1.4.11 Non-text Contrast (Level AA 2.1 and 2.2) | Supports | Non-text content in the application meets required contrast ratios. |
| 1.4.12 Text Spacing (Level AA 2.1 and 2.2) | Supports | The spacing between letters, words, lines of text and paragraphs can be adjusted without loss of content or functionality. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) | Supports | See "Known Issues" regarding known ARIA improvements. |
| 2.4.5 Multiple Ways (Level AA) | Supports | Multiple ways to navigate to content are provided. |
| 2.4.6 Headings and Labels (Level AA) | Supports | User-defined report categories display has been improved. Screen reader announcement of user-named folders has been addressed. |
| 2.4.7 Focus Visible (Level AA) | Supports | It is visually apparent which page element is receiving keyboard focus. The secret view panel introduced in version 11.9 includes enhanced keyboard access with visible focus indicators. |
| 2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) | Supports | Keyboard focus does not hide content. |
| 2.5.7 Dragging Movements (Level AA 2.2 only) | Partially Supports | Some drag to reorder functionality still exists where an alternative method is not provided (Password Change Commands, Discovery rules). |
| 2.5.8 Target Size (Minimum) (Level AA 2.2 only) | Supports | Touch targets are at least 24 by 24 pixels in size. |
| 3.1.2 Language of Parts (Level AA) | Supports | The human language of each phrase in the content can be programmatically determinable, except for proper names and technical terms. |
| 3.2.3 Consistent Navigation (Level AA) | Supports | Navigation link order is consistent |
| 3.2.4 Consistent Identification (Level AA) | Supports | As allowed by 3.2.4, different text alternatives are sometimes used when the same non-text content serves multiple functions. |
| 3.3.3 Error Suggestion (Level AA) | Supports | Error messages are displayed on forms when fields are empty or improperly formatted. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Not Applicable | Product does not create legal commitments or financial transactions. |
| 3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) | Supports | A range of authentication options are provided and do not rely on cognitive function tests. |
| 4.1.3 Status Messages (Level AA 2.1 and 2.2) | Supports | Status messages can be programmatically determined and presented. |
Table 3: Success Criteria, Level AAA
Notes: Level AAA criteria are not being used for evaluation; therefore, the table of Level AAA criteria is not included here.
