Web Content Accessibility Guidelines 2.0

Level A (Yes)

Level AA (Yes)

Level AAA (No)

Web Content Accessibility Guidelines 2.1

Level A (Yes / No)

Level AA (Yes / No)

Level AAA (Yes / No)

Web Content Accessibility Guidelines 2.2

Level A (Yes / No)

Level AA (Yes / No)

Level AAA (Yes / No)

Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018

(Yes)

EN 301 549 Accessibility requirements for ICT products and services - V3.1.1 (2019-11) AND EN 301 549 Accessibility requirements for ICT products and services - V3.2.1 (2021-03)

(Yes / No)

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)

Web: Supports

Text alternatives are provided for non-text content for images and icons. Images and icons are associated with text alternatives to inform users with visual impairments of the intent and purpose of such non-text elements through their screen readers or similar assistive technologies. Controls and input fields have descriptive, contextual labels or title attributes.

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)

Web: Not Applicable

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)

Web: Not Applicable

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)

Web: Not Applicable

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)

Web: Supports

Assistive technologies can programmatically determine the information, structure and relationships conveyed through presentation. Headings and ARIA landmarks are used to help convey presentation. Links and images are unique and contextual making it easy for users to navigate options. Tables mostly use row and column headers. Table headers use scope attribute where appropriate.

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)

Web: Supports

The content on our eCase application is created such as to be understood by assistive technologies and to be presented in different ways. eCase supports navigation through use of tab key and shift + tab key (for backward navigation). Headings and ARIA landmarks are used to help convey relationships between content. Pages are linear and read clearly without style sheets.

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)

Web: Supports

eCase application does not have any sensory characteristics.

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)

Web: Supports

Information conveyed through font styling or color is also communicated through language. Electronic forms use standard HTML mark-up and item labeling. Invisible spans are added to provide selected text to areas. When color is used for warning and confirmation messages, the associated text communicates meaning clearly on its own. Tool menus and tabs use highlighting to indicate current location. This information is also communicated by headings and selected states.

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)

Web: Not Applicable

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)

Web: Supports

eCase adequately supports keyboard functionality. Forms are accessible by keyboard and assistive technologies. Some forms use a combination of fields, buttons, inline help, and links. Some menu lists require navigation using the tab key rather than the arrow keys.

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)

Web: Supports

eCase does not have any keyboard traps.

2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)

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

NA

NA

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)

Web: Supports

eCase users are prompted with warning and having the ability to extend the session.

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)

Web: Not Applicable

eCase application does not have any moving, blinking and scrolling 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)

Web: Not Applicable

eCase does not have any flashes.

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) – Does not apply to non-web software

• 504.2 (Authoring Tool)

• 602.3 (Support Docs) – Does not apply to non-web docs

Web: Supports

Skip to main content links, headings and ARIA landmarks help users avoid repetitive and non-essential content. The expanded/collapsed state of secondary form content is clearly indicated and the fields are accessible. Users control their own content.

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)

Web: Supports

eCase application pages have title, heading 1 and ARIA main landmark.

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)

Web: Supports

Each page has a logical tab order and visible tab stops. Users control their own content. Exception: The focus is lost when you sort a data grid by column.

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)

Web: Supports

eCase provides tool tips for all the links which will explain the purpose and they are unique and contextual.

2.5.1 Pointer Gestures (Level A 2.1 and 2.2)

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

NA

NA

2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)

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

NA

NA

2.5.3 Label in Name (Level A 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.2.5.3 (Web)

• 10.2.5.3 (Non-web document)

• 11.2.5.3.1 (Open Functionality Software)

• 11.2.5.3.2 (Closed Software)

• 11.8.2 (Authoring Tool)

• 12.1.2 (Product Docs)

• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Web: For check boxes & radio buttons we had implemented using the label tags by using the for attribute which references the id of the input. In case where label tag is not used we had applied aria-label and aria labelledby. For buttons, we had implemented using the text which becomes both visible label as well as its accessible name.

Success Criteria

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 (Level A 2.1 and 2.2)

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

NA

NA

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)

Web: Supports

Language of content is notified at start of page and when changed within 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)

Web: Supports

In eCase We have visible on-focus states that use a combination of colour and border effect to highlight the focused elements.

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)

Web: Supports

eCase does not change any context when inputting a data.

3.2.6 Consistent Help (Level A 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

NA

NA

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)

Web: Supports

Error messages are communicated using a combination of alerts, landmarks, headings and links. Where possible, error messages describe each error and link to the appropriate field for resolving the error.

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)

Web: Supports

Forms have clear headings, labels, field sets, and buttons. Inline help is provided as needed. The expanded/collapsed state of secondary form content is clearly indicated, and the fields are accessible.

3.3.7 Redundant Entry (Level A 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

NA

NA

4.1.1 Parsing (Level A)

Applies to:

WCAG 2.0 and 2.1 – Always answer ‘Supports’

WCAG 2.2 (obsolete and removed) - Does not apply

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

For WCAG 2.0, 2.1, EN 301 549, and Revised 508 Standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata.

Web: Pages doesn’t have any Duplicate IDs and attributes.

All the tags have been tagged properly.

Success Criteria

Web: Your website has no major code errors

• Ensure HTML elements have complete start (< >) and end (</ >) tags where needed.

• Nest all HTML elements correctly (for example, list objects within an ordered or unordered list).

• Use unique Ids.

• Check that HTML elements don’t contain duplicate attributes.

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) – 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)

Web: Supports

In eCase, all the user interface components can be programmatically determined.

1.2.4 Captions (Live) (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.1.2.4 (Web)

• 10.1.2.4 (Non-web document)

• 11.1.2.4 (Open Functionality Software)

• 11.1.2.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)

Web: Not Applicable

eCase does not have any real time presentations or audio.

1.2.5 Audio Description (Prerecorded) (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.1.2.5 (Web)

• 10.1.2.5 (Non-web document)

• 11.1.2.5 (Open Functionality Software)

• 11.1.2.5 (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)

Web: Not Applicable

1.3.4 Orientation (Level AA 2.1 and 2.2)

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

Web: Not Applicable

Web: Not Applicable

1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.1.3.5 (Web)

• 10.1.3.5 (Non-web document)

• 11.1.3.5.1 (Open Functionality Software)

• 11.1.3.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

Web: Not Applicable

Web: Not Applicable

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)

Web: Supports

eCase controls, Text and images contrast ratio 4:5:1 is maintained across the application.

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)

Web: Supports

User account settings are available for adjusting font face and size. Icons and text resize with browser scaling/zooming options up to 200%. All product functionalities perform well at this zoom level.

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)

Web: Supports

In eCase, all the images text are controlled by CSS for position of text, font, size etc.

1.4.10 Reflow (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.1.4.10 (Web)

• 10.1.4.10 (Non-web document)

• 11.1.4.10 (Open Functionality Software)

• 11.1.4.10 (Closed Software)

• 11.8.2 (Authoring Tool)

• 12.1.2 (Product Docs)

• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

NA

NA

1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)

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

NA

NA

1.4.12 Text Spacing (Level AA 2.1 and 2.2)

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

NA

NA

1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)

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

Web: Partially Supports

Web: We had implemented this using title attribute for browser tool tip and customized attribute data-ara-title for kendo tool tip component. Pressing the Esc key closes the tool tip.

Success Criteria

Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:

Dismissible

A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;

Hoverable

If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;

Persistent

The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.

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) – Does not apply to non-web software

• 504.2 (Authoring Tool)

• 602.3 (Support Docs) – Does not apply to non-web docs

Web: Supports

Headings, ARIA landmarks (such as navigation landmarks) and unique link and button names help users navigate pages quickly. Pages have consistent navigation areas. Many pages contain search fields with ARIA search landmarks. The system works well with search and find features built into assistive technologies.

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)

Web: Supports

eCase application pages, controls are having proper headings and labels. Labels are unique and contextual.

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)

Web: Supports

Success Criteria

Web: Ensure keyboard focus is visible and clear

Make the keyboard focus visible on all elements (menu items, form fields, links, etc…).

• Use CSS to apply a visual aid to keyboard focus – a border and/or underline is best.

2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

NA

NA

2.5.7 Dragging Movements (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

NA

NA

2.5.8 Target Size (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

NA

NA

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)

Web: Not Applicable

Web: We do not have any foreign language words in our application.

Success Criteria

Web: Tell users when the language on a page changes

If your website has content in a different language to its main language, you should tell your users about the change. This helps those who use assistive technology to read the full content.

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) – Does not apply to non-web software

• 504.2 (Authoring Tool)

• 602.3 (Support Docs) – Does not apply to non-web docs

Web: Supports with Exceptions

Web: Keyboard navigation is disciplined consistently the same except some pages like Processing configuration Page and some CSD organizations Pages.

Success Criteria

Web: Use menus in the same place across your website

Keep navigation menus in the same location on all pages

• Present the options in navigation menus in the same order on all pages; and

• Keep all other standard elements (for example, your search box) in the same location on all 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) – Does not apply to non-web software

• 504.2 (Authoring Tool)

• 602.3 (Support Docs) – Does not apply to non-web docs

Web: Supports

Icons use an icon grammar to facilitate learning. The same icon is used for the same action across all pages. Users may combine concepts they already understand to interpret new icons.

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)

Web: Supports

Error messages are communicated using a combination of alerts, landmarks, headings and links. Where possible, error messages describe each error and link to the appropriate field for resolving the error.

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

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)

Web: Not Applicable

eCase application does not have any Legal or financial data but still input data can be checked before submitting.

3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Supports

Web: Success Criteria

Web: A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following:

Alternative

Another authentication method that does not rely on a cognitive function test.

Mechanism

A mechanism is available to assist the user in completing the cognitive function test.

Object Recognition

The cognitive function test is to recognize objects.

Personal Content

The cognitive function test is to identify non-text content the user provided to the Web site.

4.1.3 Status Messages (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.4.1.3 (Web)

• 10.4.1.3 (Non-web document)

• 11.4.1.3 (Open Functionality Software)

• 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

Web: Partially Supports

Web: We had implemented this using role=alert for success message, warning message and informative message.

Success Criteria

In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

1.2.6 Sign Language (Prerecorded) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

1.2.7 Extended Audio Description (Prerecorded) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

1.2.8 Media Alternative (Prerecorded) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

1.2.9 Audio-only (Live) (Level AAA)

EN 301 549 Criteria– Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

1.3.6 Identify Purpose (Level AAA 2.1 and 2.2)

EN 301 549 Criteria– Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

1.4.6 Contrast (Enhanced) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

1.4.7 Low or No Background Audio (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

1.4.8 Visual Presentation (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

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

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

2.1.3 Keyboard (No Exception) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

2.2.3 No Timing (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

2.2.4 Interruptions (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

2.2.5 Re-authenticating (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

2.2.6 Timeouts (Level AAA 2.1 and 2.2)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

2.3.2 Three Flashes (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

2.3.3 Animation from Interactions (Level AAA 2.1 and 2.2)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

2.4.8 Location (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

2.4.9 Link Purpose (Link Only) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

2.4.10 Section Headings (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

2.4.12 Focus Not Obscured (Enhanced) (Level AAA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

2.4.13 Focus Appearance (Level AAA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

2.5.5 Target Size (Level AAA 2.1 and 2.2)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 and 2.2)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

3.1.3 Unusual Words (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

3.1.4 Abbreviations (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

3.1.5 Reading Level (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

3.1.6 Pronunciation (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

3.2.5 Change on Request (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

3.3.5 Help (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

3.3.6 Error Prevention (All) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

3.3.9 Accessible Authentication (Enhanced) (Level AAA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: Not Applicable

Web:

302.1 Without Vision

Partially Supports

Supports when combined with Assistive Technology. All interfaces are designed according to HTML5 standards. Images and icons are assigned contextual and meaningful text alternatives that can be announced by a screen reader. Images of text are not used in place of text. Controls such as buttons are labeled to indicate their function. Form fields are labeled to perceive their intent. Links are assigned meaningful texts that clearly indicate the link destination. Standard interface elements are made evident through proper HTML mark up.

302.2 With Limited Vision

Supports

Supports when combined with Assistive Technology. All product functionalities perform well at 200% zoom level. All pages are designed to wrap well when zoomed to 200%. User account settings are available for adjusting font size. Icons and text resize with browser and technology scaling/zooming options. Most pages have relative column widths. System text does not use full justification. Colour contrast of foreground text with background is maintained according to standard specifications.

302.3 Without Perception of Color

Supports

Color alone is not used to convey the information.

302.4 Without Hearing

Supports

No Auditory alerts are used.

302.5 With Limited Hearing

Supports

No Auditory alerts are used.

302.6 Without Speech

Not Applicable

Speech Input is not required.

302.7 With Limited Manipulation

Supports

Supports when combined with Assistive Technology. Keyboard-accessible alternatives are provided for tools that support drag-and-drop, upload, or reordering. Current tab location is made clearly visible. Users can make their click target size larger if needed via controlling text sizes through user preferences or controlling icon sizes through browser zoom preferences.

302.8 With Limited Reach and Strength

Supports

302.9 With Limited Language, Cognitive, and Learning Abilities

Supports

Simple language is used for text content.

402 Closed Functionality

Heading cell – no response required

Heading cell – no response required

402.1 General

Heading cell – no response required

Heading cell – no response required

402.2 Speech-Output Enabled

Heading cell – no response required

Heading cell – no response required

402.2.1 Information Displayed On-Screen

NA

NA

402.2.2 Transactional Outputs

NA

NA

402.2.3 Speech Delivery Type and Coordination

NA

NA

402.2.4 User Control

NA

NA

402.2.5 Braille Instructions

NA

NA

402.3 Volume

Heading cell – no response required

Heading cell – no response required

402.3.1 Private Listening

NA

NA

402.3.2 Non-private Listening

NA

NA

402.4 Characters on Display Screens

NA

NA

402.5 Characters on Variable Message Signs

NA

NA

403 Biometrics

Heading cell – no response required

Heading cell – no response required

403.1 General

NA

NA

404 Preservation of Information Provided for Accessibility

Heading cell – no response required

Heading cell – no response required

404.1 General

NA

NA

405 Privacy

Heading cell – no response required

Heading cell – no response required

405.1 General

NA

NA

406 Standard Connections

Heading cell – no response required

Heading cell – no response required

406.1 General

NA

NA

407 Operable Parts

Heading cell – no response required

Heading cell – no response required

407.2 Contrast

NA

NA

407.3 Input Controls

Heading cell – no response required

Heading cell – no response required

407.3.1 Tactilely Discernible

NA

NA

407.3.2 Alphabetic Keys

NA

NA

407.3.3 Numeric Keys

NA

NA

407.4 Key Repeat

NA

NA

407.5 Timed Response

NA

NA

407.6 Operation

NA

NA

407.7 Tickets, Fare Cards, and Keycards

NA

NA

407.8 Reach Height and Depth

Heading cell – no response required

Heading cell – no response required

407.8.1 Vertical Reference Plane

NA

NA

407.8.1.1 Vertical Plane for Side Reach

NA

NA

407.8.1.2 Vertical Plane for Forward Reach

NA

NA

407.8.2 Side Reach

NA

NA

407.8.2.1 Unobstructed Side Reach

NA

NA

407.8.2.2 Obstructed Side Reach

NA

NA

407.8.3 Forward Reach

NA

NA

407.8.3.1 Unobstructed Forward Reach

NA

NA

407.8.3.2 Obstructed Forward Reach

NA

NA

407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach

NA

NA

407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach

NA

NA

408 Display Screens

Heading cell – no response required

Heading cell – no response required

408.2 Visibility

NA

NA

408.3 Flashing

NA

NA

409 Status Indicators

Heading cell – no response required

Heading cell – no response required

409.1 General

NA

NA

410 Color Coding

Heading cell – no response required

Heading cell – no response required

410.1 General

NA

NA

411 Audible Signals

Heading cell – no response required

Heading cell – no response required

411.1 General

NA

NA

412 ICT with Two-Way Voice Communication

Heading cell – no response required

Heading cell – no response required

412.2 Volume Gain

Heading cell – no response required

Heading cell – no response required

412.2.1 Volume Gain for Wireline Telephones

NA

NA

412.2.2 Volume Gain for Non-Wireline ICT

NA

NA

412.3 Interference Reduction and Magnetic Coupling

Heading cell – no response required

Heading cell – no response required

412.3.1 Wireless Handsets

NA

NA

412.3.2 Wireline Handsets

NA

NA

412.4 Digital Encoding of Speech

NA

NA

412.5 Real-Time Text Functionality

Reserved for future

Reserved for future

412.6 Caller ID

NA

NA

412.7 Video Communication

NA

NA

412.8 Legacy TTY Support

Heading cell – no response required

Heading cell – no response required

412.8.1 TTY Connectability

NA

NA

412.8.2 Voice and Hearing Carry Over

NA

NA

412.8.3 Signal Compatibility

NA

NA

412.8.4 Voice Mail and Other Messaging Systems

NA

NA

413 Closed Caption Processing Technologies

Heading cell – no response required

Heading cell – no response required

413.1.1 Decoding and Display of Closed Captions

NA

NA

413.1.2 Pass-Through of Closed Caption Data

NA

NA

414 Audio Description Processing Technologies

Heading cell – no response required

Heading cell – no response required

414.1.1 Digital Television Tuners

NA

NA

414.1.2 Other ICT

NA

NA

415 User Controls for Captions and Audio Descriptions

Heading cell – no response required

Heading cell – no response required

415.1.1 Caption Controls

NA

NA

415.1.2 Audio Description Controls

NA

NA

501.1 Scope – Incorporation of WCAG 2.0 AA

See WCAG 2.x section

See information in WCAG 2.x section

502 Interoperability with Assistive Technology

Heading cell – no response required

Heading cell – no response required

502.2.1 User Control of Accessibility Features

Supports

Accessibility features native to the browser or operating system can be used with eCase application. When major version changes happen on Windows and browsers, eCase is tested with OS and browser accessibility features.

502.2.2 No Disruption of Accessibility Features

Supports

eCase does not disrupt any browser or OS accessibility features.

502.3 Accessibility Services

Heading cell – no response required

Heading cell – no response required

502.3.1 Object Information

Not Applicable

Not a platform software or tool.

502.3.2 Modification of Object Information

Not Applicable

502.3.3 Row, Column, and Headers

Not Applicable

502.3.4 Values

Not Applicable

502.3.5 Modification of Values

Not Applicable

502.3.6 Label Relationships

Not Applicable

502.3.7 Hierarchical Relationships

Not Applicable

502.3.8 Text

Not Applicable

502.3.9 Modification of Text

Not Applicable

502.3.10 List of Actions

Not Applicable

502.3.11 Actions on Objects

Not Applicable

502.3.12 Focus Cursor

Not Applicable

502.3.13 Modification of Focus Cursor

Not Applicable

502.3.14 Event Notification

Not Applicable

502.4 Platform Accessibility Features

Not Applicable

503 Applications

Heading cell – no response required

Heading cell – no response required

503.2 User Preferences

Not Applicable

eCase being a web application is not required to conform to 503.2. However, in some cases, users are allowed to select preferences from browser or OS for color, contrast, font type, and size.

503.3 Alternative User Interfaces

NA

NA

503.4 User Controls for Captions and Audio Description

Heading cell – no response required

Heading cell – no response required

503.4.1 Caption Controls

NA

NA

503.4.2 Audio Description Controls

NA

NA

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.x section

See information in WCAG 2.x section

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Not Applicable

HTML editor provided for creating content and discussion posts.

504.2.2 PDF Export

Supports

eCase provides PDF Export.

504.3 Prompts

NA

NA

504.4 Templates

NA

NA

601.1 Scope

Heading cell – no response required

Heading cell – no response required

602 Support Documentation

Heading cell – no response required

Heading cell – no response required

602.2 Accessibility and Compatibility Features

Supports

eCase manuals are compatible with accessibility features.

602.3 Electronic Support Documentation

See WCAG 2.x section

See information in WCAG 2.x section

602.4 Alternate Formats for Non-Electronic Support Documentation

Not Applicable

Support documentation is provided electronically.

603 Support Services

Heading cell – no response required

Heading cell – no response required

603.2 Information on Accessibility and Compatibility Features

Supports

603.3 Accommodation of Communication Needs

Supports

Accessible support services are provided via phone and email.

4.2.1 Usage without vision

Partially Supports

Support is provided using screen readers.

4.2.2 Usage with limited vision

Supports

Support is provided using screen readers.

4.2.3 Usage without perception of colour

Supports

Color contrast is supported.

4.2.4 Usage without hearing

Supports

Support is provided using keyboard navigation functionality.

4.2.5 Usage with limited hearing

Supports

Support is provided using keyboard navigation functionality.

4.2.6 Usage with no or limited vocal capability

Supports

Support is provided using keyboard navigation functionality.

4.2.7 Usage with limited manipulation or strength

Supports

Support is provided using keyboard navigation functionality.

4.2.8 Usage with limited reach

Supports

Support is provided using keyboard navigation functionality.

4.2.9 Minimize photosensitive seizure triggers

NA

NA

4.2.10 Usage with limited cognition, language or learning

Supports

User support is provided.

4.2.11 Privacy

Supports

Casepoint does not impede usage of standard privacy controls alongside assistive technologies. Users can connect a headset for private listening to screen reader announcements.

5.1 Closed functionality

Heading cell – no response required

Heading cell – no response required

5.1.2 General

Heading cell – no response required

Heading cell – no response required

5.1.2.1 Closed functionality

See 5.2 through 13

See information in 5.2 through 13

5.1.2.2 Assistive technology

See 5.1.3 through 5.1.6

See information in 5.1.3 through 5.1.6

5.1.3 Non-visual access

Heading cell – no response required

Heading cell – no response required

5.1.3.1 Audio output of visual information

NA

NA

5.1.3.2 Auditory output delivery including speech

NA

NA

5.1.3.3 Auditory output correlation

NA

NA

5.1.3.4 Speech output user control

NA

NA

5.1.3.5 Speech output automatic interruption

NA

NA

5.1.3.6 Speech output for non-text content

NA

NA

5.1.3.7 Speech output for video information

NA

NA

5.1.3.8 Masked entry

NA

NA

5.1.3.9 Private access to personal data

NA

NA

5.1.3.10 Non-interfering audio output

NA

NA

5.1.3.11 Private listening volume

NA

NA

5.1.3.12 Speaker volume

NA

NA

5.1.3.13 Volume reset

NA

NA

5.1.3.14 Spoken languages

NA

NA

5.1.3.15 Non-visual error identification

NA

NA

5.1.3.16 Receipts, tickets, and transactional outputs

NA

NA

5.1.4 Functionality closed to text enlargement

NA

NA

5.1.5 Visual output for auditory information

NA

NA

5.1.6 Operation without keyboard interface

Heading cell – no response required

Heading cell – no response required

5.1.6.1 Closed functionality

See 5.1.3.1 through 5.1.3.16

See information in 5.1.3.1 through 5.1.3.16

5.1.6.2 Input focus

NA

NA

5.1.7 Access without speech

NA

NA

5.2 Activation of accessibility features

NA

NA

5.3 Biometrics

NA

NA

5.4 Preservation of accessibility information during conversion

NA

NA

5.5 Operable parts

Heading cell – no response required

Heading cell – no response required

5.5.1 Means of operation

NA

NA

5.5.2 Operable parts discernibility

NA

NA

5.6 Locking or toggle controls

Heading cell – no response required

Heading cell – no response required

5.6.1 Tactile or auditory status

NA

NA

5.6.2 Visual status

NA

NA

5.7 Key repeat

NA

NA

5.8 Double-strike key acceptance

NA

NA

5.9 Simultaneous user actions

NA

NA

6.1 Audio bandwidth for speech

NA

NA

6.2 Real-time text (RTT) functionality

Heading cell – no response required

Heading cell – no response required

6.2.1.1 RTT communication

NA

NA

6.2.1.2 Concurrent voice and text

NA

NA

6.2.2.1 Visually distinguishable display

NA

NA

6.2.2.2 Programmatically determinable send and receive direction

NA

NA

6.2.2.3 Speaker identification

NA

NA

6.2.2.4 Visual indicator of Audio with RTT

NA

NA

6.2.3 Interoperability

NA

NA

6.2.4 RTT responsiveness

NA

NA

6.3 Caller ID

NA

NA

6.4 Alternatives to voice-based services

NA

NA

6.5 Video communication

Heading cell – no response required

Heading cell – no response required

6.5.1 General (informative)

Heading cell – no response required

Heading cell – no response required

6.5.2 Resolution

NA

NA

6.5.3 Frame rate

NA

NA

6.5.4 Synchronization between audio and video

NA

NA

6.5.5 Visual indicator of audio with video

NA

NA

6.5.6 Speaker identification with video (sign language) communication

NA

NA

6.6 Alternatives to video-based services (advisory only)

Advisory – no response required

Advisory – no response required

7.1 Caption processing technology

Heading cell – no response required

Heading cell – no response required

7.1.1 Captioning playback

NA

NA

7.1.2 Captioning synchronization

NA

NA

7.1.3 Preservation of captioning

NA

NA

7.1.4 Captions characteristics

NA

NA

7.1.5 Spoken subtitles

NA

NA

7.2.1 Audio description playback

NA

NA

7.2.2 Audio description synchronization

NA

NA

7.2.3 Preservation of audio description

NA

NA

7.3 User controls for captions and audio description

NA

NA

8.1.1 Generic requirements

Heading cell – no response required

Heading cell – no response required

8.1.2 Standard connections

NA

NA

8.1.3 Colour

NA

NA

8.2 Hardware products with speech output

Heading cell – no response required

Heading cell – no response required

8.2.1.1 Speech volume range

NA

NA

8.2.1.2 Incremental volume control

NA

NA

8.2.2.1 Fixed-line devices

NA

NA

8.2.2.2 Wireless communication devices

NA

NA

8.3 Stationary ICT

Heading cell – no response required

Heading cell – no response required

8.3.2.1 Unobstructed high forward reach

NA

NA

8.3.2.2 Unobstructed low forward reach

NA

NA

8.3.2.3.1 Clear space

NA

NA

8.3.2.3.2 Obstructed (< 510 mm) forward reach

NA

NA

8.3.2.3.3 Obstructed (< 635 mm) forward reach

NA

NA

8.3.2.4 Knee and toe clearance width

NA

NA

8.3.2.5 Toe clearance

NA

NA

8.3.2.6 Knee clearance

NA

NA

8.3.3.1 Unobstructed high side reach

NA

NA

8.3.3.2 Unobstructed low side reach

NA

NA

8.3.3.3.1 Obstructed (≤ 255 mm) side reach

NA

NA

8.3.3.3.2 Obstructed (≤ 610 mm) side reach

NA

NA

8.3.4.1 Change in level

NA

NA

8.3.4.2 Clear floor or ground space

NA

NA

8.3.4.3.2 Forward approach

NA

NA

8.3.4.3.3 Parallel approach

NA

NA

8.3.5 Visibility

NA

NA

8.3.6 Installation instructions

NA

NA

8.4 Mechanically Operable parts

Heading cell – no response required

Heading cell – no response required

8.4.1 Numeric keys

NA

NA

8.4.2.1 Means of operation of mechanical parts

NA

NA

8.4.2.2 Force of operation of mechanical parts

NA

NA

8.4.3 Keys, tickets and fare cards

NA

NA

8.5 Tactile indication of speech mode

NA

NA

10.0 General (informative)

Heading cell – no response required

Heading cell – no response required

10.1.1.1 through 10.4.1.3

See WCAG 2.x section

See information in WCAG 2.x section

10.5 Caption positioning

NA

NA

10.6 Audio description timing

NA

NA

11.0 General (informative)

Heading cell – no response required

Heading cell – no response required

11.1.1.1 through 11.4.1.3

See WCAG 2.x section

See information in WCAG 2.x section

11.5 Interoperability with assistive technology

Heading cell – no response required

Heading cell – no response required

11.5.1 Closed functionality

Heading cell – no response required

Heading cell – no response required

11.5.2 Accessibility services

Heading cell – no response required

Heading cell – no response required

11.5.2.1 Platform accessibility service support for software that provides a user interface

See 11.5.2.5 through 11.5.2.17

See information in 11.5.2.5 through 11.5.2.17

11.5.2.2 Platform accessibility service support for assistive technologies

See 11.5.2.5 through 11.5.2.17

See information in 11.5.2.5 through 11.5.2.17

11.5.2.3 Use of accessibility services

See information in 11.5.2.5 through 11.5.2.17

See information in 11.5.2.5 through 11.5.2.17

11.5.2.4 Assistive technology

NA

NA

11.5.2.5 Object information

Partially Supports

Casepoint uses ARIA attributes to describe the role, state, and description of user interface elements to Assistive Technologies

11.5.2.6 Row, column, and headers

Partially Supports

Rows, columns, and any headers associated with those rows or columns, are programmatically determinable through assistive technologies.

11.5.2.7 Values

Supports

Casepoint uses standard HTML or and ARIA object attributes.

11.5.2.8 Label relationships

Supports

Casepoint uses standard HTML and ARIA attributes to describe label relationships of user interface elements to assistive technologies. This includes the use of “” element and “aria-labelledby” and “aria-label” attributes.

11.5.2.9 Parent-child relationships

Partially Supports

Casepoint uses standard HTML markup to express hierarchical relationships

11.5.2.10 Text

Supports

The content of text objects, text attributes, and the boundary of text rendered to the screen, is programmatically determinable through DOM.

11.5.2.11 List of available actions

Supports

Casepoint uses standard HTML and ARIA object attributes for actions such as search and filter

11.5.2.12 Execution of available actions

Partially Supports

Casepoint allows assistive technology to programmatically execute available actions on objects with the exception of interactive stats charts.

11.5.2.13 Tracking of focus and selection attributes

Supports

Focus, text insertion point, and selection attributes of user interface elements are programmatically determinable by assistive technologies.

11.5.2.14 Modification of focus and selection attributes

Partially Supports

Casepoint allows keyboards and

assistive technologies to

programmatically modify focus,

text insertion point, and selection attributes of user interface

elements

11.5.2.15 Change notification

Supports

Notification of events relevant to user interactions, including but not limited to, changes in the component’s state(s), value, name, description, or boundary, are available to assistive technology through DOM

11.5.2.16 Modifications of states and properties

Supports

All user-set states and properties are capable of being set programmatically, including through assistive technologies.

11.5.2.17 Modifications of values and text

Supports

All user-set input is capable of being set programmatically, including through assistive technologies

11.6 Documented accessibility usage

Heading cell – no response required

Heading cell – no response required

11.6.1 User control of accessibility features

Partially Supports

Casepoint user can able to turn on or off accessibility feature from the user configuration settings.

11.6.2 No disruption of accessibility features

Partially Supports

Casepoint platform is compatible with operating system and browser accessibility features configured by the user.

11.7 User preferences

Supports

Casepoint respects user preferences from platform.

11.8 Authoring tools

Heading cell – no response required

Heading cell – no response required

11.8.1 Content technology

Heading cell – no response required

Heading cell – no response required

11.8.2 Accessible content creation

See WCAG 2.x section

(If not authoring tool, enter “Not Applicable”)

See information in WCAG 2.x section

11.8.3 Preservation of accessibility information in transformations

NA

NA

11.8.4 Repair assistance

NA

NA

11.8.5 Templates

NA

NA

12.1 Product documentation

Heading cell – no response required

Heading cell – no response required

12.1.1 Accessibility and compatibility features

Does not support

12.1.2 Accessible documentation

See WCAG 2.x section

See information in WCAG 2.x section

12.2 Support Services

Heading cell – no response required

Heading cell – no response required

12.2.2 Information on accessibility and compatibility features

Does not support

12.2.3 Effective communication

Does not support

12.2.4 Accessible documentation

See WCAG 2.x section

See information in WCAG 2.x section

13.1 Relay services requirements

Heading cell – no response required

Heading cell – no response required

13.1.2 Text relay services

NA

NA

13.1.3 Sign relay services

NA

NA

13.1.4 Lip-reading relay services

NA

NA

13.1.5 Captioned telephony services

NA

NA

13.1.6 Speech to speech relay services

NA

NA

13.2 Access to relay services

NA

NA

13.3 Access to emergency services

NA

NA