VPAT® Version 2.4
Date: March 2024
Compliance level: WCAG 2.1 AA
Platforms: Web (Chrome, Edge, Firefox, Safari)
Contact: support@captivoice.com
Conformance to the listed accessibility standards has been evaluated by Charmtech Labs using manual testing with assistive technologies.
This report covers the degree of conformance for the following accessibility standard/guidelines:
| Standard/Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.1, at https://www.w3.org/TR/WCAG21/ |
Level A – Yes Level AA – Yes Level AAA – Yes |
| Section 508 as published in 2017, at http://www.Section508.gov | Yes |
| EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe, at http://mandate376.standards.eu/standard | Yes |
The terms used in the Conformance Level information are defined as follows:
Tables 1 and 2 also document conformance with:
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
|
1.1.1 Non-text Content (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti uses standard HTML and WAI-ARIA techniques for providing text equivalents of non-text elements. This includes the use of “alt” attributes for images and the use of “aria-label” or “aria-describedby” attributes for other visual elements. |
|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Not Applicable |
Capti does not includes prerecorded audio or video content. |
|
1.2.2 Captions (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Not Applicable |
Capti does not includes prerecorded audio content. |
|
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Not Applicable |
Capti does not use synchronized media. |
|
1.3.1 Info and Relationships (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti uses semantically-correct markup so that information, structure, and relationships can be understood independent of presentation. |
|
1.3.2 Meaningful Sequence (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti uses semantically-correct markup to allow assistive technologies to interpret the meaning of content and controls. |
|
1.3.3 Sensory Characteristics (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti uses WAI-ARIA techniques and textual representation to ensure that that knowledge of sensory characteristics is not required. |
|
1.4.1 Use of Color (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
|
|
1.4.2 Audio Control (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Capti Accommodate, Capti Higher Ed Supports Capti ReadBasix Not Applicable |
Capti Accommodate and Capti Higher Ed provide capabilities for controlling when synthetically generated speech is started and paused, which voice will be used and what will be the speech rate. Capti ReadBasix does not provides synthetically generated speech as it is not applicable by design (screeen-reader tools can be used). |
|
2.1.1 Keyboard (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti supports standard keyboard navigation and provides built-in shortcuts for commonly accessed functionality. Capti does not require specific timing for individual keystrokes. |
|
2.1.2 No Keyboard Trap (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti supports standard keyboard navigation and ensures that keyboard users cannot be trapped in a subset of content. |
|
2.1.4 Character Key Shortcuts (Level A) |
Supports |
|
|
2.2.1 Timing Adjustable (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti has no time limits except in one case: Capti will synchronize with server every 15 minutes to update user's access permissions to content. This is done under real-time event exception. |
|
2.2.2 Pause, Stop, Hide (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti does not include moving, blinking, scrolling, or auto-updating information. |
|
2.3.1 Three Flashes or Below Threshold (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti does not use flashing interface elements. |
|
2.4.1 Bypass Blocks (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
A hidden link (available to screen readers) allows users to jump to the main content of each page. |
|
2.4.2 Page Titled (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Screens and web pages in Capti have titles that indicate the topic or purpose of each screen or page. |
|
2.4.3 Focus Order (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti uses a semantically meaningful tab order through interactive elements. |
|
2.4.4 Link Purpose (In Context) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
The purpose of each link in Capti can be determined from the link text alone. |
|
2.5.1 Pointer Gestures (Level A) |
Not Applicable |
Capti is not using multipoint or path-based gestures. |
|
2.5.2 Pointer Cancellation (Level A) |
Supports |
|
|
2.5.3 Label in Name (Level A) |
Supports |
|
|
2.5.4 Motion Actuation (Level A) |
Not Applicable |
Capti has no functionality that can be operated by device motion or user motion. |
|
3.1.1 Language of Page (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Language of page can be programmatically determined. |
|
3.2.1 On Focus (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
When a component in Capti user interface receives focus, it does not initiate a change of context. |
|
3.2.2 On Input (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Changing the setting of a component in Capti user interface does not initiate a change of context. |
|
3.3.1 Error Identification (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
If an input error is detected Capti shows a dialog with error description. |
|
3.3.2 Labels or Instructions (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti provides labels, placeholders and additional instructions when user input is required. |
|
4.1.1 Parsing (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti uses semantically-correct and standards compliant markup for all interface elements. |
|
4.1.2 Name, Role, Value (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
|
1.2.4 Captions (Live) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Not Applicable |
Capti does not use synchronized media. |
|
1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Not Applicable |
Capti does not use synchronized media. |
|
1.3.4 Orientation (Level AA) |
Supports |
|
|
1.3.5 Identify Input Purpose (Level AA) |
Supports |
|
|
1.4.3 Contrast (Minimum) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports with Exception |
Capti visual presentation provides adequate contrast, with rare exceptions. In addition, Capti Accommodate and Capti Higher Ed users can choose among multiple color schemes for textual content they add to Capti. The color schemes are designed to cover a wide range of preferences of individuals with print dissabilities. |
|
1.4.4 Resize text (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti user interfaces support standard zoom capabilities built into modern web browsers and operating systems. In addition, Capti Accommodate and Capti Higher Ed users can separately change zoom level of textual content they add to Capti. |
|
1.4.5 Images of Text (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti user interface does not include images of text. Capti Accommodate and Capti Higher Ed users can add images of text to Capti and use Capti built-in OCR feature to convert them into accessible text. |
|
1.4.10 Reflow (Level AA) |
Supports |
|
|
1.4.11 Non-text Contrast (Level AA) |
Supports |
|
|
1.4.12 Text Spacing (Level AA) |
Supports |
|
|
1.4.13 Content on Hover or Focus (Level AA) |
Supports with Exception |
Some non-essential information that is replicated on screen without hover may appear in the administrative user interface. No such exceptions exist in the student user interface. |
|
2.4.5 Multiple Ways (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti website web pages are interlinked in multiple ways. |
|
2.4.6 Headings and Labels (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti uses semantically-correct markup for all interface elements, including headings and labels. Headings in textual content added to Capti by users are defined by content authors and will be presented within Capti as defined. |
|
2.4.7 Focus Visible (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti uses visual changes to elements to indicate the current position of focus. |
|
3.1.2 Language of Parts (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports with Exception |
In Capti, the language of the interface can be programmatically determined. In addition, Capti Accommodate and Capti Higher Ed programmatically determines language of content added by the user in order to read it using correct text-to-speech voice. Users can translate portions of content they added into 100+ languages and then listen to the translation using text-to-speech voice. However, there is no mechanism for specifying different languages for portions of the same textual content added by the user. |
|
3.2.3 Consistent Navigation (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
Capti uses the same navigation mechanisms and navigation design patterns across all pages. |
|
3.2.4 Consistent Identification (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
|
|
3.3.3 Error Suggestion (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
If an input error is automatically detected, Capti will identify the reason for the error in text. |
|
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Supports |
On Web pages that cause legal commitments or financial transactions Capti interface provides opportunity to reverse incompleted submission, verify and correct errors, and confirm the final submission. |
|
4.1.3 Status Messages (Level AA) |
Supports |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
|
1.2.6 Sign Language (Prerecorded) (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Not Applicable |
Capti does not use synchronized media. |
|
1.2.7 Extended Audio Description (Prerecorded) (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Not Applicable |
Capti does not use synchronized media. |
|
1.2.8 Media Alternative (Prerecorded) (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Not Applicable |
Capti does not use synchronized media. |
|
1.2.9 Audio-only (Live) (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Not Applicable |
Capti does not use time-based media. |
|
1.3.6 Identify Purpose (Level AAA) |
Supports with Exception |
Purpose of some of the user interface components may not be programmatically identifiable. |
|
1.4.6 Contrast Enhanced (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Does Not Support |
|
|
1.4.7 Low or No Background Audio (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Not Applicable |
|
|
1.4.8 Visual Presentation (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Capti Accommodate and Capti Higher Ed Supports with Exception Capti ReadBasix Does Not Support |
Capti Accommodate and Capti Higher Ed provide students with the following mechanisms for adjusting visual presentation of blocks of text
|
|
1.4.9 Images of Text (No Exception) Control (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Supports |
|
|
2.1.3 Keyboard (No Exception) (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Does Not Support |
|
|
2.2.3 No Timing (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Capti Accommodate and Capti Higher Ed Supports Capti ReadBasix Does Not Support |
Capti Accommodate and Capti Higher Ed have no time limits except in one case: Capti will synchronize with server every 15 minutes to update user's access permissions to content. This is done under real-time event exception. |
|
2.2.4 Interruptions (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Not Applicable |
Capti does not use interruptions except those involving an emergency. |
|
2.2.5 Re-authenticating (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Supports with Exception |
When answering questions in ReadBasix or other tests, the latest question or questions on latest screen presented to the student that hasn't been submitted will have to be answered again. All other data will be retained without loss. |
|
2.2.6 Timeouts (Level AAA) |
Not Applicable |
There is no data loss due to timeout in Capti. |
|
2.3.2 Three Flashes (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Not Applicable |
Capti does not use flashing interface elements. |
|
2.3.3 Animation from Interactions (Level AAA) |
Supports |
Capti does not use animations. |
|
2.4.8 Location (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Supports with Exception |
Most pages in Capti include location information. |
|
2.4.9 Link Purpose (Link Only) (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Supports |
The purpose of each link in Capti can be determined from the link text alone. |
|
2.4.10 Section Headings (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Supports |
Headings in textual content added to Capti by users are defined by content authors and will be presented within Capti as defined. |
|
2.5.5 Target Size (Level AAA) |
Supports |
|
|
2.5.6 Concurrent Input Mechanisms (Level AAA) |
Supports |
|
|
3.1.3 Unusual Words (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Capti Accommodate and Capti Higher Ed Supports with Exception Capti ReadBasix Not Applicable |
Capti Accommodate and Capti Higher Ed provide a mechanism for looking up definitions and translations of words, phrases and passeges. Capti Accommodate and Capti Higher Ed use the following techniques to maximize correctness of provided translation or definition:
|
|
3.1.4 Abbreviations (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Capti Accommodate and Capti Higher Ed Does Not Support Capti ReadBasix Not Applicable |
|
|
3.1.5 Reading Level (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Not Applicable |
Capti does not includes built-in reading materials, except when used as part of an assessment or a test. |
|
3.1.6 Pronunciation (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Capti Accommodate and Capti Higher Ed Supports Capti ReadBasix Not Applicable |
Capti Accommodate and Capti Higher Ed provide users with mechanism to view word's phonetic transcription and listen to how the word (or a phrase) should be pronounced. This feature is supported for 26+ languages. |
|
3.2.5 Change on Request (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Does Not Support |
|
|
3.3.5 Help (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Supports |
Most interfaces in Capti are straighforward and do not require contextual help. In some cases contextual help is available. |
|
3.3.6 Error Prevention (All) (Level AAA) Also applies to: EN 301 549 Criteria – Does not apply 2017 Section 508 – Does not apply |
Supports with Exception |
Capti interface provides opportunity to reverse incompleted submission, verify and correct errors, and confirm the final submission. Exception 1: in cases when completed action is reversible the users are not required to confirm final submission (instead users are encouraged to reverse the submission). Exception 2: in case when completed action is not intended to be reversible, such as answering a question and opening the next question, the users are not allowed to reverse their action. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
302.1 Without Vision |
Supports |
|
302.2 With Limited Vision |
Supports |
|
302.3 Without Perception of Color |
Supports |
Color is only used as a decorative or supplemental attribute of user interface elements. A textual representation is always used as the primary mechanism for conveying information. |
302.4 Without Hearing |
Supports |
Capti does not include audio-only features that require hearing to be used. |
302.5 With Limited Hearing |
Supports |
Capti does not include audio-only features that require hearing to be used. |
302.6 Without Speech |
Supports |
Capti does not require speech input. |
302.7 With Limited Manipulation |
Supports |
Capti supports standard input mechanisms such as user-provided keyboards and pointing devices. Usage of the product does not require fine motor controls nor simultaneous actions. |
302.8 With Limited Reach and Strength |
Supports |
|
| 302.9 With Limited Language, Cognitive, and Learning Abilities |
Supports |
Capti ReadBasix is designed to test language abilities. |
Notes: Capti has no hardware component and is not subject to the requirements of this section.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
501.1 Scope – Incorporation of WCAG 2.1 AA |
See WCAG 2.1 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 |
Not Applicable |
Capti is not considered platform software as defined by Section 508. |
502.2.2 No Disruption of Accessibility Features |
Supports |
Capti is compatible with operating system and browser accessibility features configured by the user. |
502.3 Accessibility Services |
Heading cell – no response required |
Heading cell – no response required |
502.3.1 Object Information |
Supports |
Capti uses WAI-ARIA attributes to describe the role, state, and description of user interface elements to Assistive Technologies. |
502.3.2 Modification of Object Information |
Supports |
Capti uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies. |
502.3.3 Row, Column, and Headers |
Supports |
Capti uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies. |
502.3.4 Values |
Supports |
Capti uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies. |
502.3.5 Modification of Values |
Supports |
Capti uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies. |
502.3.6 Label Relationships |
Supports |
Capti uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies. |
502.3.7 Hierarchical Relationships |
Supports |
Capti uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies. |
502.3.8 Text |
Supports |
Capti uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies. |
502.3.9 Modification of Text |
Supports |
Capti renders strings as plain text values in HTML for maximum compatibility with assistive technologies. |
502.3.10 List of Actions |
Supports |
Capti uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies. |
502.3.11 Actions on Objects |
Supports |
Capti uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies. |
502.3.12 Focus Cursor |
Supports |
Capti uses visual changes to elements to indicate the current position of focus. |
502.3.13 Modification of Focus Cursor |
Supports |
Capti uses standard HTML elements with standard cursor controls for user input. |
502.3.14 Event Notification |
Supports |
|
502.4 Platform Accessibility Features |
Not Applicable |
Capti is not considered platform software as defined by Section 508. |
503 Applications |
Heading cell – no response required |
Heading cell – no response required |
503.2 User Preferences |
Supports |
Capti respects user preferences from platform or OS settings. |
503.3 Alternative User Interfaces |
Not Applicable |
Capti does not provide any alternative user interfaces that function as assistive technology. |
503.4 User Controls for Captions and Audio Description |
Heading cell – no response required |
Heading cell – no response required |
503.4.1 Caption Controls |
Does Not Support |
Capti does not provide capabilities for captioning or defining audio descriptions of designer-specified video content. |
503.4.2 Audio Description Controls |
Does Not Support |
Capti does not provide capabilities for captioning or defining audio descriptions of designer-specified video content. |
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.1 section |
See information in WCAG section |
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Not Applicable |
|
504.2.2 PDF Export |
Not Applicable |
|
504.3 Prompts |
Not Applicable |
|
504.4 Templates |
Not Applicable |
Notes: This report covers accessibility conforance for the Appian product and does not discuss Documentation or Support Services.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
4.2.1 Usage without vision |
Supports |
Capti uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies |
4.2.2 Usage with limited vision |
Supports |
Capti supports standard browser magnification and contrast adjustments. Capti Accommodate and Capti Higher Ed enable users to magnify font size of the textual content they added to Capti. |
4.2.3 Usage without perception of colour |
Supports |
Capti always uses textual representation as the primary mechanism for conveying information. In addition, Capti Accommodate and Capti Higher Ed users can change color scheme of textual content they add to Capti. |
4.2.4 Usage without hearing |
Not Applicable |
Capti does not include audio-only features that require hearing to be used |
4.2.5 Usage with limited hearing |
Not Applicable |
Capti does not include audio-only features that require hearing to be used |
4.2.6 Usage without vocal capability |
Not Applicable |
Capti does not require speech input |
4.2.7 Usage with limited manipulation or strength |
Supports |
Capti supports standard input mechanisms such as user-provided keyboards and pointing devices |
4.2.8 Usage with limited reach |
Not Applicable |
|
4.2.9 Minimize photosensitive seizure triggers |
Supports |
Capti does not include features that could trigger seizures |
4.2.10 Usage with limited cognition |
Supports |
Capti uses a logical focus order and informs users of errors using text and earcons |
4.2.11 Privacy |
Supports |
Capti does not impede usage of standard privacy controls alongside assistive technologies. For example, users can connect a headset for private listening to screen reader announcements. |
Notes: Capti supports standard assistive technologies and is therefore not subject to the Closed Functionality criteria described in this Chapter.
Notes: Capti does not offer two-way voice communication and is therefore not subject to the requirements of this section.
Notes: Capti does not include video content.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
7.1 Caption processing technology |
Heading cell – no response required |
Heading cell – no response required |
7.1.1 Captioning playback |
Does Not Support |
|
7.1.2 Captioning synchronization |
Does Not Support |
|
7.1.3 Preservation of captioning |
Does Not Support |
|
7.2.1 Audio description playback |
Does Not Support |
|
7.2.2 Audio description synchronization |
Does Not Support |
|
7.2.3 Preservation of audio description |
Does Not Support |
|
7.3 User controls for captions and audio description |
Does Not Support |
Notes: Capti does not include a hardware component and is not subject to the requirements of this section.
Notes: Capti does not include non-web documents and is therefore not subject to the requirements of this section.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
11.2.1 Software success criteria (excluding closed functionality) |
See WCAG 2.1 section |
See information in WCAG section |
11.2.2 Software success criteria (closed functionality) |
See WCAG 2.1 section |
See information in WCAG section |
11.3 Interoperability with assistive technology |
Heading cell – no response required |
Heading cell – no response required |
11.3.1 Closed functionality (informative) |
Heading cell – no response required |
Heading cell – no response required |
11.3.2 Accessibility services |
Heading cell – no response required |
Heading cell – no response required |
11.3.2.1 Platform accessibility service support for software that provides a user interface |
See 11.3.2.5 through 11.3.2.17 |
See information in 11.3.2.5 through 11.3.2.17 |
11.3.2.2 Platform accessibility service support for assistive technologies |
See 11.3.2.5 through 11.3.2.17 |
See information in 11.3.2.5 through 11.3.2.17 |
11.3.2.3 Use of accessibility services |
Supports |
Capti uses standard platform accessibility services. |
11.3.2.4 Assistive technology |
Not Applicable |
Capti is not itself an assistive technology. |
11.3.2.5 Object information |
Supports |
Capti uses WAI-ARIA attributes to describe the role, state, and description of user nterface elements to Assistive Technologies. The includes the use of “role”, “aria-invalid”, and “aria-required” attributes. |
11.3.2.6 Row, column, and headers |
Supports |
Capti uses standard HTML attributes to define table structure and relationships, including column headers, to Assistive Technologies. |
11.3.2.7 Values |
Supports |
|
11.3.2.8 Label relationships |
Supports |
Capti uses standard HTML and WAI-ARIA attributes to describe label relationships of user interface elements to Assistive Technologies. This includes the use of “<label>” and “aria-labelledby” attributes. |
11.3.2.9 Parent-child relationships |
Supports |
|
11.3.2.10 Text |
Supports |
|
11.3.2.11 List of available actions |
Supports |
|
11.3.2.12 Execution of available actions |
Supports |
|
11.3.2.13 Tracking of focus and selection attributes |
Supports |
|
11.3.2.14 Modification of focus and selection attributes |
Supports |
|
11.3.2.15 Change notification |
Supports |
|
11.3.2.16 Modifications of states and properties |
Supports |
|
11.3.2.17 Modifications of values and text |
Supports |
|
11.4 Documented accessibility usage |
Heading cell – no response required |
Heading cell – no response required |
11.4.1 User control of accessibility features |
Not Applicable |
Capti is not considered platform software as defined by EN 301 549. |
11.4.2 No disruption of accessibility features |
Supports |
|
11.5 User preferences |
Supports |
Capti respects user preferences from platform or OS settings. |