Name of Product/Version: eCase 11.2.x

Product Description: Electronic Case Management System

Report Date: 12/20/2023

Evaluation Methods Used: Accessibility tests are integrated into the unit testing and integration testing protocols of developers. For this they are trained and equipped with state-of-the-art automated accessibility testing tools. Success criteria not covered by the automated tests are covererd by the manual testing protocols of our quality assurance testers, which include testing with assistive technologies. Key test methods used are listed below.

Tool Based Testing : SortSite 5.0 and Web Accessibilty Tool bar

Color Contrast Testing: Web Accessibilty Tool bar

Screen Reader Testing: JAWS 2020/Chrome

Screen Magnifier Testing: OS tools on Windows

Manual Accessiblity Tetsing : Keyboard testing with visual focus.

__________________________________

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.0

Level A (Yes)

Level AA (Yes)

Level AAA (No)

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

2018

(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.0 Level AAA.

WCAG 2.0 Report

Tables 1 and 2 also document conformance with Revised Section 508:

Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing
Chapter 6 – 602.3 Electronic Support Documentation

NOTE: When reporting on conformance with the WCAG 2.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Table 1: Success Criteria, Level A

Notes:

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Supports	Text alternatives are provided for non-text content for images and icons. Images and icons are associated with text alternative 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.
	Supports
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not Applicable
Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Not Applicable
1.2.2 Captions (Prerecorded) (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Not Applicable
	Not Applicable
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Not Applicable
1.3.1 Info and Relationships (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	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: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	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 through the user interface). 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: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Supports	eCase application does not have any sensory chracteristics.
1.4.1 Use of Color (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	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: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Not Applicable
eCase adequately supports keyboard functionality. Forms are accessi	eCase adequately supports keyboard functionality. Forms are accessi	eCase adequately supports keyboard functionality. Forms are accessi
2.1.2 No Keyboard Trap (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Supports	eCase does not have any Key board traps.
2.2.1 Timing Adjustable (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Supports	eCase users are prompted with warning and having the ability to extent the session.
2.2.2 Pause, Stop, Hide (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	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: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Not applicable	eCase does not have any flashes.

Criteria	Conformance Level	Remarks and Explanations
2.4.1 Bypass Blocks (Level A) Also applies to: 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	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.
	Supports
2.4.2 Page Titled (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Supports	eCase application pages have title, heading 1 and ARIA main landmark.
2.4.3 Focus Order (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	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: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Supports	eCase provides tool tips for the all the links which will explain the purpose and they are unique and contextual.
3.1.1 Language of Page (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	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: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	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: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Supports	eCase does not change any context when inputting a data.
3.3.1 Error Identification (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	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: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	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.
4.1.1 Parsing (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Supports	eCase Web pages are written to HTML5 specifications.
4.1.2 Name, Role, Value (Level A) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Supports	In eCase, all the user interface components can be programmatically dertermined.

Table 2: Success Criteria, Level AA

Notes:

Criteria	Conformance Level	Remarks and Explanations
1.2.4 Captions (Live) (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Not Applicable	eCase does not have any rela time presentations or audio.

1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable
Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)
1.4.3 Contrast (Minimum) (Level AA) Also applies to: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	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: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Supports	User account settings are available for adjusting font face and size. Icons and text resize with browser (and other technology) 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: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Supports	In eCase, all the images text are controlled by CSS for position of text, font, size etc.
2.4.5 Multiple Ways (Level AA) Also applies to: 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	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: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Supports	eCase application pages, controls are having proper headings and labels. Labels are unique and contextual.
3.2.4 Consistent Identification (Level AA) Also applies to: 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	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: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	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: Revised Section 508 501 (Web)(Software) 504.2 (Authoring Tool) 602.3 (Support Docs)	Not Applicable	eCase application does not have any Legal or fianancial data but still inout data can be checked before submmiting.

Table 3: Success Criteria, Level AAA

Notes: Deleted; Not Evala

Revised Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria

Conformance Level

Remarks and Explanations

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 ontextual 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.
Controls are assigned appropriate labels that allow perception of their function.
Standard interface elements are made evident through proper HTML mark up.

302.2 With Limited Vision

Supports

Supports when combined with Assistive Technology.

Criteria	Conformance Level	Remarks and Explanations
		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 other 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 these two mechanisms: o By controlling text sizes through user preferences. o By controlling icon sizes through browser zoom preferences.

Criteria	Conformance Level	Remarks and Explanations

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

Chapter 4: Hardware

Notes: Not Applicable

Criteria	Conformance Level	Remarks and Explanations
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	Not Applicable
402.2.2 Transactional Outputs	Not Applicable
402.2.3 Speech Delivery Type and Coordination	Not Applicable
402.2.4 User Control	Not Applicable
402.2.5 Braille Instructions	Not Applicable
*402.3 Volume*	Heading cell – no response required	Heading cell – no response required
402.3.1 Private Listening	Not Applicable
402.3.2 Non-private Listening	Not Applicable
402.4 Characters on Display Screens	Not Applicable
402.5 Characters on Variable Message Signs	Not Applicable
*403 Biometrics*	Heading cell – no response required	Heading cell – no response required
403.1 General	Not Applicable
*404 Preservation of Information Provided for Accessibility*	Heading cell – no response required	Heading cell – no response required
404.1 General	Not Applicable

Criteria	Conformance Level	Remarks and Explanations
*405 Privacy*	Heading cell – no response required	Heading cell – no response required
405.1 General	Not Applicable
*406 Standard Connections*	Heading cell – no response required	Heading cell – no response required
406.1 General	Not Applicable
*407 Operable Parts*	Heading cell – no response required	Heading cell – no response required
407.2 Contrast	Not Applicable
*407.3 Input Controls*	Heading cell – no response required	Heading cell – no response required
407.3.1 Tactilely Discernible	Not Applicable
407.3.2 Alphabetic Keys	Not Applicable
407.3.3 Numeric Keys	Not Applicable
407.4 Key Repeat	Not Applicable
407.5 Timed Response	Not Applicable
407.6 Operation	Not Applicable
407.7 Tickets, Fare Cards, and Keycards
*407.8 Reach Height and Depth*	Heading cell – no response required	Heading cell – no response required
407.8.1 Vertical Reference Plane	Not Applicable
407.8.1.1 Vertical Plane for Side Reach	Not Applicable
407.8.1.2 Vertical Plane for Forward Reach	Not Applicable
407.8.2 Side Reach	Not Applicable
407.8.2.1 Unobstructed Side Reach	Not Applicable
407.8.2.2 Obstructed Side Reach	Not Applicable
407.8.3 Forward Reach	Not Applicable
407.8.3.1 Unobstructed Forward Reach	Not Applicable
407.8.3.2 Obstructed Forward Reach	Not Applicable
407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach	Not Applicable
407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach	Not Applicable
*408 Display Screens*	Heading cell – no response required	Heading cell – no response required

Criteria	Conformance Level	Remarks and Explanations
408.2 Visibility	Not Applicable
408.3 Flashing	Not Applicable
*409 Status Indicators*	Heading cell – no response required	Heading cell – no response required
409.1 General	Not Applicable
*410 Color Coding*	Heading cell – no response required	Heading cell – no response required
410.1 General	Not Applicable
*411 Audible Signals*	Heading cell – no response required	Heading cell – no response required
411.1 General	Not Applicable
*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	Not Applicable
412.2.2 Volume Gain for Non-Wireline ICT	Not Applicable
*412.3 Interference Reduction and Magnetic Coupling*	Heading cell – no response required	Heading cell – no response required
412.3.1 Wireless Handsets	Not Applicable
412.3.2 Wireline Handsets	Not Applicable
412.4 Digital Encoding of Speech	Not Applicable
412.5 Real-Time Text Functionality	Reserved for future	Reserved for future
412.6 Caller ID	Not Applicable
412.7 Video Communication	Not Applicable
*412.8 Legacy TTY Support*	Heading cell – no response required	Heading cell – no response required
412.8.1 TTY Connectability	Not Applicable
412.8.2 Voice and Hearing Carry Over	Not Applicable
412.8.3 Signal Compatibility	Not Applicable
412.8.4 Voice Mail and Other Messaging Systems	Not Applicable
*413 Closed Caption Processing Technologies*	Heading cell – no response required	Heading cell – no response required
413.1.1 Decoding and Display of Closed Captions	Not Applicable
413.1.2 Pass-Through of Closed Caption Data	Not Applicable
*414 Audio Description Processing Technologies*	Heading cell – no response required	Heading cell – no response required

Criteria	Conformance Level	Remarks and Explanations
414.1.1 Digital Television Tuners	Not Applicable
414.1.2 Other ICT	Not Applicable
*415 User Controls for Captions and Audio Descriptions*	Heading cell – no response required	Heading cell – no response required
415.1.1 Caption Controls	Not Applicable
415.1.2 Audio Description Controls	Not Applicable

Chapter 5: Software

Criteria	Conformance Level	Remarks and Explanations
501.1 Scope – Incorporation of WCAG 2.0 AA	See WCAG 2.0 section	See information in WCAG 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 IE, 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

Criteria	Conformance Level	Remarks and Explanations
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, user is allowed to select preferences from browser or OOS for color, contrast, font type, size.
503.3 Alternative User Interfaces	Not Applicable	Alternative user interface not provided
*503.4 User Controls for Captions and Audio Description*	Heading cell – no response required	Heading cell – no response required
503.4.1 Caption Controls	Not Applicable	eCase does not hve cations and audio descriptions
503.4.2 Audio Description Controls	Not Applicable
*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.0 section	See information in WCAG 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	Not Applicable
504.4 Templates	Not Applicable

Chapter 6: Support Documentation and Services

Criteria	Conformance Level	Remarks and Explanations
*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 manauls are compatible with accessibility features.
602.3 Electronic Support Documentation	See WCAG 2.0 section	See information in WCAG 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.

Legal Disclaimer

casepoint software and documentation have been tested and reviewed. Nevertheless, casepoint makes no warranty or representation, either express or implied, with respect to the software and documentation included. In no event will casepoint be liable for direct, indirect, special, incidental, or consequential damages resulting from any defect in the software or documentation included with these products. In particular, casepoint shall have no liability for any programs or data used with these products, including the cost of recovering such programs or data.

Casepoint Accessibility Conformance Report VPAT® Version 2.4