CaptionSync Web User Interface (CaptionSync), Version 12.0
Accessibility Conformance Report published by Verbit
Partial extraction. We read 28 of 31 Level A and 20 of 24 Level AA criteria from this document (87% coverage). The remainder are missing from our extraction, not necessarily from Verbit's report — their table layout defeated our parser. Treat the figures below as incomplete and read the source document for the full picture.
Conformance by level
Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.
Level A — 28 criteria
- Supports
- 27
- Partially supports
- 0
- Does not support
- 0
- Not applicable
- 1
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 18
- Partially supports
- 2
- Does not support
- 0
- Not applicable
- 0
- Not evaluated
- 0
Level AAA — 28 criteria
- Supports
- 3
- Partially supports
- 0
- Does not support
- 0
- Not applicable
- 2
- Not evaluated
- 23
Source: View the original report published by Verbit.
These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.
All reported criteria (96)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Supports | Web: The CaptionSync web UI is primarily text-based. There are a small number of icons that are used, such as the “help” question mark and a pencil-shaped “edit” icon are are used in place of text as their visible button labels. All of these icons have titles and alternative text that can be interpreted by assistive technology such as screen readers. This criterion was validated via code inspection, verifying that each non-text control had appropriate and relevant alternative text. Note that the explanations for this criterion apply only to the CaptionSync web UI itself, not the video content supplied by customers. Please see the Notes section on pages 1 - 2 for details on how video or audio content is made accessible using CaptionSync. |
| 1.2.2 | Captions (Prerecorded) | A | Supports | Web: The CaptionSync web UI does not have any video components, but it does reference and play customer- supplied prerecorded video files. This was validated via manual inspection and code inspection of CaptionSync web pages. When using CaptionSync with prerecorded video content, customers should request transcription and captioning via the CaptionSync service to meet this success criterion. Please see the Notes section on pages 1 - 2 for details on how video content is made accessible using CaptionSync. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Supports | Web: The CaptionSync web UI does not have any video components, but it does reference and play customer- supplied prerecorded video files. This was validated via manual inspection and code inspection of CaptionSync web pages. When using the CaptionSync with prerecorded video content, customers should request our audio description services via the CaptionSync to meet this success criterion. CaptionSync audio description services |
| 1.3.2 | Meaningful Sequence | A | Supports | Web: Content in the CaptionSync web UI is presented in a meaningful sequence, and sequence that affects meaning can be programmatically determined. This was validated via code inspection of CaptionSync web pages, and by viewing each page without CSS. |
| 1.3.3 | Sensory Characteristics | A | Supports | Web: Instructions do not rely on sensory characteristics of the components. The function of all icons can be determined via their title element, which can be accessed via assistive technology such as screen readers. This criterion was tested via manual inspection and code inspection of CaptionSync web pages. |
| 1.4.1 | Use of Color | A | Supports | Web: Color is not used as the only means of conveying information. This was tested via manual inspection and code inspection of CaptionSync web pages, including inspection after testing of each feature of the web UI. |
| 1.4.2 | Audio Control | A | Supports | Web: Audio does not play automatically; audio/video is played only on user request (following Technique G171). This was tested via manual inspection and code inspection of CaptionSync web pages, including inspection after testing of each feature of the web UI. |
| 2.1.1 | Keyboard | A | Supports | Web: All functionality is available from the keyboard. Keys required are Tab (to move focus), Enter (to select), up, down, left and right arrows (for sliders), Esc (to exit modals), and alphanumeric keys to enter search terms. There are no controls in the web UI that require simultaneous keystrokes. This was tested manually by using the keyboard to access all supported features of the CaptionSync web UI. |
| 2.1.2 | No Keyboard Trap | A | Supports | Web: Focus can be moved using only a keyboard interface, with no keyboard traps. This was tested by |
| 2.1.4 | Character Key Shortcuts | A | Supports | Web: There are no character key shortcuts in the CaptionSync web UI. |
| 2.2.1 | Timing Adjustable | A | Supports | Web: There are no time limits or timeouts in the web UI. The only function with a timing element is the Play/Pause feature of the caption editor. Video/audio will play until completion when the Play control is used, unless the user pauses using the corresponding Pause control. This was validated via code inspection, and through manual testing of each supported feature. |
| 2.2.2 | Pause, Stop, Hide | A | Supports | Web: The user can pause or stop media playback in the caption editor. This was validated via code inspection, and through manual testing of each supported feature. |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | Web: The CaptionSync web UI itself does not include anything that flashes. This was validated through manual testing of each supported feature. Video producers should ensure that their video content conforms to flash thresholds. |
| 2.4.1 | Bypass Blocks | A | Supports | Web: ARIA landmarks are used to identify regions of the page (such as “nav” and “main”), as per Technique ARIA11. These features allow assistive technology users to skip quickly to the desired section of a page. This was validated via manual inspection and code inspection of CaptionSync web pages. |
| 2.4.2 | Page Titled | A | Supports | Web: CaptionSync pages are titled in a way that describe their purpose. This was validated via code inspection of all CaptionSync web pages. |
| 2.4.3 | Focus Order | A | Supports | Web: Focus order preserves the meaning and operability of the CaptionSync web UI. This was validated via code inspection, and through manual testing of all CaptionSync pages. |
| 2.4.4 | Link Purpose (In Context) | A | Supports | Web: The purpose of each link in CaptionSync can be determined from the link text alone, except where the purpose of the link would be ambiguous in general, as per SC 2.4.4. The main challenge that we are working on in this area is a general usability challenge, resulting from use of terms that may not be familiar to users who do not have experience with all of our features and names for those features. We are working to make the names of features (and their corresponding links) more intuitive in the next major release of the CaptionSync web UI. |
| 2.5.1 | Pointer Gestures | A | Supports | Web: There are no path-based or multipoint that cannot be operated with a single point gesture. |
| 2.5.2 | Pointer Cancellation | A | Supports | Web: For pointer actions, activation occurs on up events. |
| 2.5.3 | Label in Name | A | Supports | Web: The names of CaptionSync UI components are based on the visible labels. |
| 2.5.4 | Motion Actuation | A | Not Applicable | Web: There is no motion actuation in the CaptionSync web UI. |
| 3.1.1 | Language of Page | A | Supports | Web: CaptionSync UI pages are currently always presented in English, and this can be programmatically determined (<html lang="en"> is included in the code |
| 3.2.1 | On Focus | A | Supports | Web: Components do not change context when they receive focus. This was validated via code inspection, and through manual testing of each component in the CaptionSync web UI. |
| 3.2.2 | On Input | A | Supports | Web: When components of the CaptionSync web UI receive focus they do not initiate a change in context. This was validated via code inspection, and through manual testing of each component of the CaptionSync web UI. |
| 3.3.1 | Error Identification | A | Supports | Web: Input errors are identified to the user in text form. This criterion was evaluated via code inspection, and through manual testing of each component of the CaptionSync web UI. |
| 3.3.2 | Labels or Instructions | A | Supports | Web: All form input fields include labels and relevant instructions. This criterion was evaluated via code inspection, and through manual testing of each component of the CaptionSync web UI. |
| 4.1.1 | Parsing | A | Supports | Web: All elements have complete start and end tags, are nested according to their specifications, they do not contain duplicate attributes, and IDs are unique, except where the specifications allow these features. This criterion was evaluated via code inspection of all of the CaptionSync web UI compenents. |
| 4.1.2 | Name, Role, Value | A | Supports | Web: The names and roles of user interface components can be programmatically determined and set. Notification of changes is available to user agents, including assistive technology. This criterion was evaluated via code inspection of all of the CaptionSync web UI compenents. |
| 1.2.4 | Captions (Live) | AA | Supports | Web: The CaptionSync web UI is not used for live video (but it can be used to schedule live captioning sessions). Please see the Notes section on pages 1 - 2 for details on how video or audio content is made accessible using the CaptionSync web UI. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Supports | Web: CaptionSync supports audio description via two methods: a) via a text track (Technique H96), and b) a secondary audio file that contains descriptions created using Text-to-Speech. Customers can request audio description services via CaptionSync in the same way that they request captions. Please see the Notes section on pages 1 - 2 for details on how video or audio content is made accessible using the CaptionSync web UI. This was validated via code inspection, and through manual testing of CaptionSync web UI pages for numerous video submissions for which CaptionSync audio description services have been requested. |
| 1.3.4 | Orientation | AA | Supports | |
| 1.3.5 | Identify Input Purpose | AA | Supports | Web: The purpose of all input fields can be programmatically determined. |
| 1.4.3 | Contrast (Minimum) | AA | Supports | Web: All text meets Level AA minimum contrast ratios. This criterion was tested using the WebAIM WAVE tool on CaptionSync web UI pages. |
| 1.4.4 | Resize text | AA | Partially Supports | Web: All text can be resized up to 200 percent without loss of content or functionality using standard browser page zoom controls. Currently we do not support the "Change font size" feature in browsers that would allow users to change text size independent of other UI elements. However, our user interfaces are designed in a "responsive" manner, meaning that elements adjust automatically to the available screen space, thus making zoom an effective workaround for resizing text. |
| 1.4.5 | Images of Text | AA | Supports | Web: With the exception of the CaptionSync logo, images of text are not used in the CaptionSync web UI. The CaptionSync logo falls under the “essential presentation” exception of SC 1.4.5, and the logo text is included in an alt tag. This was validated via code inspection, and through manual testing of CaptionSync web UI pages (all of which use the same components). Note that customers may use the CaptionSync web UI to caption videos that include images of text that is not described in the dialog. To ensure accessibility in this scenario, customers should request CaptionSync audio description services, as described in the Notes section on pages 1 – 2 of this report. |
| 1.4.10 | Reflow | AA | Partially Supports | Web: The CaptionSync web UI is designed to reflow content in a responsive manner to avoid scrolling in two directions. However, the minimum screen width required to retain full visibility of both the menu and input field labels is 770px. We are evaluating how a width of 320 px can best be supported, and hope to implement this in the next major update of the CaptionSync web UI. This functionality was tested using Chrome Developer tools with the viewport width and heights specified above. |
| 1.4.11 | Non-text Contrast | AA | Supports | Web: Active controls and their associated icons have a contrast ratio of 3:1 or higher. This feature was tested using WebAIM’s WAVE testing tool. |
| 1.4.12 | Text Spacing | AA | Supports | Web: The CaptionSync web UI is designed with |
| 1.4.13 | Content on Hover or Focus | AA | Supports | Web: Pointer hover and keyboard focus does not trigger additional content, except for content controlled by the browser (e.g., display of the title element). |
| 2.4.5 | Multiple Ways | AA | Supports | Web: In order to keep the web UI simple and maximize usability, CaptionSync was designed such that only the most commonly needed features are enabled when an account is initially created. Users can enable new features when they need them. For the most commonly used features, there are multiple ways to access them, such as through the Dashboard Quick Links and also through the navigation menu. There are also breadcrumbs on each page, allowing easy access to other levels of the navigation hierarchy. The CaptionSync UI also conforms to technique G185, linking to all pages from the home page. This criterion was evaluated through manual testing and through user feedback. Usability and proposed design improvements are being assessed through test sessions with actual users. |
| 2.4.6 | Headings and Labels | AA | Supports | Web: There is only one heading for each CaptionSync page, and they describe the purpose of the pages. There are often several buttons and form controls on CaptionSync web UI pages, and they provide descriptive text labels for the function. This was validated via code inspection, and through evaluation of each CaptionSync web UI page to determine if the labels appropriately indicate the function of the controls. |
| 2.4.7 | Focus Visible | AA | Supports | Web: The keyboard focus is always visible. This was tested by using the keyboard to access all supported features of the CaptionSync web UI, tabbing through the entire interface for each page. |
| 3.1.2 | Language of Parts | AA | Supports | Web: The CaptionSync web UI is currently only offered in English, and each page indicates lang=”en”. There are no parts of CaptionSync pages that are presented in a different language than that of the page as a whole. This was tested via code inspection of CaptionSync web UI user interface components. |
| 3.2.3 | Consistent Navigation | AA | Supports | Web: Navigation and content on CaptionSync web UI pages is presented consistently in the same order. This was tested manually by navigating through each page of the CaptionSync UI, and noting the order of content and navigation menus. |
| 3.2.4 | Consistent Identification | AA | Supports | Web: Functional components of the CaptionSync web UI are consistently identified and labeled on all pages of the user interface. This was tested manually by navigating through each page of the CaptionSync UI, and noting the order of content and navigation menus. |
| 3.3.3 | Error Suggestion | AA | Supports | Web: Error correction suggestions are provided when possible. In some cases the user is prompted to click on a link to an article in our Support Center for more |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | Web: The CaptionSync web UI’s web pages do not cause legal or financial commitments or allow data changes or deletions. |
| 4.1.3 | Status Messages | AA | Supports | Web: The only place in the CaptionSync web UI where status messages are displayed without a change of contest is the upload progress indicator, which is used to notify the user of progress during the upload of a media file. This progress indicator complies with SC 4.1.3 by using role=progressbar and the aria-valuenow attribute. |
| 1.2.6 | Sign Language (Prerecorded) | AAA | Not Evaluated | |
| 1.2.7 | Extended Audio Description (Prerecorded) | AAA | Supports | Web: The CaptionSync web UI supports extended audio description. The CaptionSync Smart Player can be used with CaptionSync outputs to automatically pause the video, playing each description and resuming the video when the description playback is complete. This allows for more comprehensive descriptions than with standard audio description techniques, which is especially valuable for educational video content. Please see the Notes section on pages 1 - 2 for details on how video content is made accessible for use with the CaptionSync web UI through supporting CaptionSync services. This was validated through manual testing of CaptionSync web UI pages for numerous video submissions for which CaptionSync audio description services have been requested. |
| 1.2.8 | Media Alternative (Prerecorded) | AAA | Supports | Web: The CaptionSync Smart Player includes a transcript pane that includes an interleaved script containing both the captions and the descriptions of the video. This can be accessed via a screen reader, and is especially useful for users whose vision does not allow them to reliably read captions and whose hearing does not allow them reliably hear the dialog. Please see the Notes section on |
| 1.2.9 | Audio-only (Live) | AAA | Not Applicable | Product is not used for live audio. |
| 1.3.6 | Identify Purpose | AAA | Not Evaluated | |
| 1.4.6 | Contrast Enhanced | AAA | Not Evaluated | |
| 1.4.7 | Low or No Background Audio | AAA | Not Evaluated | |
| 1.4.8 | Visual Presentation | AAA | Not Evaluated | |
| 1.4.9 | Images of Text (No Exception) Control | AAA | Not Evaluated | |
| 2.1.3 | Keyboard (No Exception) | AAA | Not Evaluated | |
| 2.2.3 | No Timing | AAA | Not Evaluated | |
| 2.2.4 | Interruptions | AAA | Not Evaluated | |
| 2.2.5 | Re-authenticating | AAA | Not Evaluated | |
| 2.2.6 | Timeouts | AAA | Not Evaluated | |
| 2.3.2 | Three Flashes | AAA | Supports | Web: CaptionSync web UI does not contain anything that flashes more than three times per second (in fact, there are no components of the CaptionSync web UI that flash at all). Note that content providers would need to evaluate their video content to ensure that the video also meet this criterion. Please see the Notes section on pages 1 – 2 of this report for details on how video content can be made accessible for use with the CaptionSync web UI. This was validated via code inspection, and also through manual testing of the CaptionSync web UI and each of its user interface components. |
| 2.3.3 | Animation from Interactions | AAA | Not Evaluated | |
| 2.4.8 | Location | AAA | Not Evaluated | |
| 2.4.9 | Link Purpose (Link Only) | AAA | Not Evaluated | |
| 2.4.10 | Section Headings | AAA | Not Applicable | |
| 2.5.5 | Target Size | AAA | Not Evaluated | |
| 2.5.6 | Concurrent Input Mechanisms | AAA | Not Evaluated | |
| 3.1.3 | Unusual Words | AAA | Not Evaluated | |
| 3.1.4 | Abbreviations | AAA | Not Evaluated | |
| 3.1.5 | Reading Level | AAA | Not Evaluated | |
| 3.1.6 | Pronunciation | AAA | Not Evaluated | |
| 3.2.5 | Change on Request | AAA | Not Evaluated | |
| 3.3.5 | Help | AAA | Not Evaluated | |
| 3.3.6 | Error Prevention (All) | AAA | Not Evaluated | |
| 502.2.1 | User Control of Accessibility Features | - | Not Applicable | The CaptionSync web UI is not considered platform software as defined by Section 508. |
| 502.2.2 | No Disruption of Accessibility Features | - | Supports | The CaptionSync web UI does not interfere with operation system or browser accessibility features configured by the user. |
| 502.3.1 | Object Information | - | Supports | The CaptionSync web UI uses standard HTML and ARIA attributes to describe state, role, and description of UI elements. All criteria in this section were tested via code inspection. |
| 502.3.2 | Modification of Object Information | - | Supports | States and properties in the CaptionSync web UI that can be set by users can also be set using assistive technology. |
| 502.3.3 | Row, Column, and Headers | - | Supports | Rows, columns, and headers of data tables |
| 502.3.4 | Values | - | Supports | The CaptionSync web UI uses standard HTML and ARIA attributes to maximize compatibility with assistive technology. |
| 502.3.5 | Modification of Values | - | Supports | The CaptionSync web UI uses standard HTML and ARIA attributes to maximize compatibility with assistive technology. |
| 502.3.6 | Label Relationships | - | Supports | The CaptionSync web UI 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. |
| 502.3.7 | Hierarchical Relationships | - | Supports | The CaptionSync UI uses standard HTML markup to express hierarchical relationships. |
| 502.3.8 | Text | - | Supports | The CaptionSync UI renders strings as HTML plain text values to maximize compatibility with assistive technology. |
| 502.3.9 | Modification of Text | - | Supports | Text that can be modified in the CaptionSync UI can also be modified using assistive technology as it is exposed using standard HTML markup. |
| 502.3.10 | List of Actions | - | Supports | The CaptionSync web UI uses standard HTML and ARIA attributes to maximize compatibility with assistive technology. |
| 502.3.11 | Actions on Objects | - | Supports | The CaptionSync web UI uses standard HTML and ARIA attributes to maximize compatibility with assistive technology. |
| 502.3.12 | Focus Cursor | - | Supports | Keyboard and cursor focus is shown visually and can be moved using the keyboard or assistive technology. |
| 502.3.13 | Modification of Focus Cursor | - | Supports | The CaptionSync web UI uses standard |
| 502.3.14 | Event Notification | - | Supports | The CaptionSync web UI uses HTML and ARIA attributes such as aria-now and aria- live assertions to notify users of events and state changes in a way that is compatible with assistive technology. |
| 503.4.1 | Caption Controls | - | Supports | Caption controls are included in the same menu as volume selection. |
| 503.4.2 | Audio Description Controls | - | Supports | Audio description controls are included in the same menu as volume selection. |
| 504.2.1 | Preservation of Information Provided for Accessibility in Format Conversion | - | Not Applicable | The CaptionSync web UI is not considered an authoring tool as defined by Section 508. |
| 504.2.2 | PDF Export | - | Not Applicable | The CaptionSync web UI is not considered an authoring tool as defined by Section |
Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.
Get told when this changes
This report is dated July 2021. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.
Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.