Human API Connect Accessibility Conformance Report
Based on VPAT® Version 2.4
Product Information
Name of Product/Version: Human API Connect
Report Date: February 10, 2021
Product Description: Consumers use Human API Connect to find and connect their providers, as well as authorize secure access to their electronic health information to entities of their choosing.
Contact Information: support@humanapi.co
Notes: The information contained in this report applies to the product itself. Testing was done on key user journeys including searching for a provider and entering login credentials to connect a provider account.
Evaluation Methods Used: Testing Human API Connect involved extensive use of widely-used assistive technology, including screen readers, screen magnifiers, and speech recognition software, as well exclusive use of the keyboard. Native platform accessibility tools were also used during testing. These were supplemented with techniques such as manual inspection of Human API Connect.
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 |
| Web Content Accessibility Guidelines 2.1 | Level A: Yes Level AA: Yes Level AAA: No |
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.1 Report
Note: When reporting on conformance with the WCAG 2.1 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
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) | Supports | Web: All non-text content has a text alternative unless it is decorative or a control/input that has a name to describe its purpose. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Supports | Web: The product does not contain pre-recorded audio-only or pre-recorded video-only media. |
| 1.2.2 Captions (Prerecorded) (Level A) | Supports | Web: The product does not contain any pre-recorded audio content in synchronized media. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Supports | Web: The product does not provide its own prerecorded video content that would require audio description. |
| 1.3.1 Info and Relationships (Level A) | Partially Supports | Web: Information, structure, and relationships can be programmatically determined or are available in text. Exceptions include:
|
| 1.3.2 Meaningful Sequence (Level A) | Supports | Web: The product presents content in a meaningful sequence. |
| 1.3.3 Sensory Characteristics (Level A) | Supports | Web: Instructions do not rely solely on sensory characteristics. |
| 1.4.1 Use of Color (Level A) | Supports | Web: The product does not convey information through color alone. |
| 1.4.2 Audio Control (Level A) | Supports | Web: The product does not contain any audio. |
| 2.1.1 Keyboard (Level A) | Supports | Web: This product is operable through a keyboard interface. |
| 2.1.2 No Keyboard Trap (Level A) | Supports | Web: The product does not contain any keyboard traps. |
| 2.1.4 Character Key Shortcuts (Level A 2.1 only) | Supports | Web: The product does not contain any character key shortcuts. |
| 2.2.1 Timing Adjustable (Level A) | Supports | Web: The product does not include any content that has a time limit. |
| 2.2.2 Pause, Stop, Hide (Level A) | Supports | Web: The product does not include elements which move, blink, scroll, or auto-update. |
| 2.3.1 Three Flashes or Below Threshold (Level A) | Supports | Web: The product does not include any flashing content. |
| 2.4.1 Bypass Blocks (Level A) | Supports | Web: Mechanisms are available to bypass blocks of content that are repeated on multiple Web pages. |
| 2.4.2 Page Titled (Level A) | Supports | Web: Product pages have titles that describe topic or purpose. |
| 2.4.3 Focus Order (Level A) | Supports | Web: Components receive focus in a meaningful order. |
| 2.4.4 Link Purpose (In Context) (Level A) | Supports | Web: The purpose of link text can be determined in context. |
| 2.5.1 Pointer Gestures (Level A 2.1 only) | Supports | Web: The product does not rely on multipoint or path-based gestures. |
| 2.5.2 Pointer Cancellation (Level A 2.1 only) | Supports | Web: Product functions that use a single pointer are completed when the user releases the pointer. |
| 2.5.3 Label in Name (Level A 2.1 only) | Supports | Web: The product uses the name used in labels where text is presented. |
| 2.5.4 Motion Actuation (Level A 2.1 only) | Supports | Web: The product does not have functionality operated by device motion or user motion. |
| 3.1.1 Language of Page (Level A) | Supports | Web: The default human language of each product page can be programmatically determined. |
| 3.2.1 On Focus (Level A) | Supports | Web: Components do not initiate a change of context when focused. |
| 3.2.2 On Input (Level A) | Supports | Web: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. |
| 3.3.1 Error Identification (Level A) | Supports | Web: The product identifies input errors and describes them in text. |
| 3.3.2 Labels or Instructions (Level A) | Supports | Web: The product provides labels/instructions when content requires user input. |
| 4.1.1 Parsing (Level A) | Supports | Web: The product contains elements that are fully parseable and unique, where necessary. |
| 4.1.2 Name, Role, Value (Level A) | Supports | Web: The product provides the names, roles, and values programmatically for all user interface components. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) | Supports | Web: The product does not contain live synchronized media. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Supports | Web: The product does not contain prerecorded video content in synchronized media. |
| 1.3.4 Orientation (Level AA 2.1 only) | Supports | Web: Content does not restrict its view and operation to a single display orientation. |
| 1.3.5 Identify Input Purpose (Level AA 2.1 only) | Supports | Web: The purpose of each input field collecting information about the user can be programmatically determined. |
| 1.4.3 Contrast (Minimum) (Level AA) | Partially Supports | Web: Most text meets minimum contrast requirements. Exceptions include:
|
| 1.4.4 Resize text (Level AA) | Supports | Web: The product allows for the resizing of text. |
| 1.4.5 Images of Text (Level AA) | Supports | Web: The product uses text instead of images of text. |
| 1.4.10 Reflow (Level AA 2.1 only) | Supports | Web: The product contains content that can be presented without loss of information or functionality. |
| 1.4.11 Non-text Contrast (Level AA 2.1 only) | Partially Supports | Web: Most meaningful non-text content elements have
sufficient contrast. Exceptions include:
|
| 1.4.12 Text Spacing (Level AA 2.1 only) | Supports | Web: No loss of content or functionality occurs by setting all of the following and by changing no other style property:
|
| 1.4.13 Content on Hover or Focus (Level AA 2.1 only) | Supports | Web: When content is triggered by hover or focus, it becomes visible and then hidden in a manner which meets this criterion. |
| 2.4.5 Multiple Ways (Level AA) | Supports | Web: The product contains multiple ways to locate a web page. |
| 2.4.6 Headings and Labels (Level AA) | Supports | Web: The product contains headings and labels that describe topic or purpose. |
| 2.4.7 Focus Visible (Level AA) | Supports | Web: The product is operable by keyboard anywhere the keyboard focus indicator is visible. |
| 3.1.2 Language of Parts (Level AA) | Supports | Web: The language can be programmatically determined within the product. |
| 3.2.3 Consistent Navigation (Level AA) | Supports | Web: Repeated navigational components occur in the same relative order each time they are repeated. |
| 3.2.4 Consistent Identification (Level AA) | Supports | Web: Components that have the same functionality are identified consistently throughout the product. |
| 3.3.3 Error Suggestion (Level AA) | Supports | Web: Where input errors are automatically detected, such as an invalid date, items in error are identified, error messages are provided as text, and the error(s) are associated with the field for assistive technology to convey to the user. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | Supports | Web: The product ensures that when legal commitments occur, users have the ability to correct validated input errors, review and confirm submission prior to submitting data, or reverse the submission. |
| 4.1.3 Status Messages (Level AA 2.1 only) | Supports | Web: Status messages can be programmatically determined through roles or properties such that they can be presented to the user by assistive technologies without receiving focus. |
Table 3: Success Criteria, Level AAA
Level AAA not evaluated
