Accessibility and WCAG
See how Cevoid's customer-facing solutions align with WCAG 2.1 requirements for ADA and EAA compliance.
Cevoid's customer-facing solutions comply with WCAG 2.1 Level AA requirements. This helps brands using Cevoid meet digital accessibility standards where customers interact with widgets, forms on Cevoid URLs, and parts of the Cevoid API. The widgets and forms covered are galleries, cards, the UGC popup, upload forms, program widgets, review widgets, and review forms.
Highlights
Keyboard and screen readers
Visitors can use Cevoid widgets with a keyboard and a screen reader.
- Galleries: Visitors reach each post with Tab and open it with Enter or Space. Screen readers name a post by what a click does, such as Open larger image, Open video, or View product, and then read its alt text or video description.
- Load more: Loading more posts from the keyboard moves focus to the first new post, and screen readers announce how many loaded
- UGC popup: Focus stays in the popup until it closes. Escape closes it, and the arrow keys move between posts. Its videos have a pause button, and videos with sound have buttons to mute and turn on captions.
- Program widgets: Focus stays in a popup until it closes, and Escape closes it
- Review widgets and review forms: A popup takes focus, keeps it until it closes, and then returns it to where the shopper was. Escape closes it, or first asks Discard your review? when a review form has unsaved input. In the review form, Tab reaches each star, and Space or Enter picks it. Fields have labels, and screen readers announce errors.
- Focus rings: Review widgets and review forms show a focus ring when a shopper moves with the keyboard, in the Focus ring color of the BrandKit color scheme
Motion
Some widgets move on their own. Each has a setting that keeps it still.
| Widget | What moves on its own | To keep it still |
|---|---|---|
| Galleries | Videos, muted and with a pause button, when Autoplay video is Yes (the default) | Set Autoplay video to No. See Advanced settings |
| Collage galleries | The first image changes every 10 seconds when Animate is Yes (the default) | Set Animate to No. See Gallery layouts |
| Cards | The video, muted, when Autoplay is Yes (the default) | Set Autoplay to No. See Video settings |
| Program widgets | A video background in the Hero section, muted | Use images as the Desktop and Mobile backgrounds. See Hero |
| Review widgets | Carousels with Motion set to Autoplay, and tickers | Set Motion to Off, or select a Layout other than Ticker. See Review list layout |
When a visitor's device is set to reduce motion, galleries don't autoplay videos, review carousels don't play on their own, and review tickers stand still. Review carousels also stop while a shopper tabs through them, and a ticker's Hover setting slows or pauses it under the pointer.
Language
Cevoid widgets are automatically localized with the correct language for your workspace markets. Localization includes all accessibility features.
Alt text for photo posts
Approved photo posts automatically receive descriptive alt text, translated for all languages activated on your workspace. A video's alt text is its description: see Descriptions for video posts.
- Adjust alt text in the post's Alt-text field. See Edit accessibility fields.
- Alt text displays automatically in all UGC widgets in the correct language
- Alt text and translations are available through the API
Captions for video posts
Video posts with speech automatically receive captions once approved. Captions are translated for all languages activated on your workspace.
- Adjust captions in the post's Video captions field. See Edit accessibility fields.
- Videos with only music get "[Music playing]" as their caption
- Visitors turn captions on and off with the captions button on a video in the UGC popup, where they show over the video. The button shows on videos that have captions and sound.
- Captions are off by default but activate for all videos in that widget once a visitor enables them on one post
- Captions and translations are available through the API
Descriptions for video posts
Video posts automatically receive a summarizing description once approved. Descriptions are translated for all languages on your workspace.
- Video descriptions are the videos' alt text in all UGC widgets, in the correct language
- Adjust the description of a video without sound in the post's Video description field. See Edit accessibility fields.
- Video descriptions and translations are available through the API
Alt text, captions, and descriptions for review photos and videos
When a review comes in, Reviews AI writes alt text for each photo. For each video, it writes alt text for the thumbnail, a description, and captions when the video has sound, or "[Music playing]" when it has only music. The text is translated for all languages activated on your workspace.
- Review widgets use the alt text of a photo, and of a video's thumbnail, in the shopper's language
- Alt text, video descriptions, captions, and their translations are available through the API
- Your team can read the text, but not edit it: open the review and click the photo or video. See Review details.
WCAG breakdown
Applicable standards
| Standard | Included |
|---|---|
| Web Content Accessibility Guidelines 2.1 | Level A ✓, Level AA ✓, Level AAA ✗ |
The tables also list the Level A and AA criteria that WCAG 2.2 added: 2.4.11, 2.5.7, 2.5.8, 3.2.6, 3.3.7, and 3.3.8.
Conformance levels
| Level | Meaning |
|---|---|
| Supports | Cevoid's customer-facing solutions meet the criterion |
| Partially Supports | Some functionality does not meet the criterion |
| Does Not Support | The majority of functionality does not meet the criterion |
| Not Applicable | The criterion is not relevant to Cevoid's customer-facing solutions |
Level A criteria
| Criteria | Explanation | Conformance | Remarks |
|---|---|---|---|
| 1.1.1 Non-text Content | All icons, images, and visuals must have text descriptions or be hidden from assistive tech if decorative | Partially Supports | All non-text content is labeled with meaningful text alternatives or marked decorative. Program widgets are missing contextual alt text for images uploaded by the company. |
| 1.2.1 Audio-only and Video-only | Audio-only needs a transcript. Video-only needs a description or audio explanation | Supports | Video posts without sound have descriptions, and video posts with sound have synchronized captions. No audio-only media is present. |
| 1.2.2 Captions (Prerecorded) | Prerecorded videos with sound must have captions | Supports | Video posts with audio include synchronized captions in the UGC popup. |
| 1.2.3 Audio Description or Media Alternative | Videos with audio must have a text alternative or audio description | Supports | Video posts include a description, and captions when they have sound. |
| 1.3.1 Info and Relationships | Visual structure must be encoded for assistive tech | Supports | Semantic HTML and ARIA roles expose structure and relationships to assistive technologies. |
| 1.3.2 Meaningful Sequence | Content must be in logical order recognizable by assistive tech | Supports | DOM order matches visual presentation and ensures correct reading sequence. |
| 1.3.3 Sensory Characteristics | Instructions can't rely only on color, shape, or position | Supports | Instructions avoid referring only to visual or sensory cues. |
| 1.4.1 Use of Color | Color alone can't be the only way to show meaning | Supports | Color is not used as the sole method of conveying information. |
| 1.4.2 Audio Control | Auto-playing audio must be controllable | Supports | No audio content plays automatically. |
| 2.1.1 Keyboard | Everything must be usable with keyboard only | Supports | All functionality is operable via keyboard navigation. |
| 2.1.2 No Keyboard Trap | Users must be able to move focus in and out of all components | Supports | Keyboard trapping does not occur except in modal windows. |
| 2.1.4 Character Key Shortcuts | Single key shortcuts must be configurable | Supports | Character key shortcuts are not present. |
| 2.2.1 Timing Adjustable | Time limits must be adjustable | Supports | Timeout content is not present. |
| 2.2.2 Pause, Stop, Hide | Moving content must be controllable | Supports | Gallery videos have a pause button. Every widget that moves on its own has a setting that keeps it still, and gallery videos and review carousels and tickers stand still when the visitor's device is set to reduce motion. See Motion. |
| 2.3.1 Three Flashes | Nothing should flash more than 3 times per second | Supports | Flashing content is not present. |
| 2.4.1 Bypass Blocks | Users must be able to skip repeated content | Supports | Content blocks are not present. |
| 2.4.2 Page Titled | Pages must have descriptive titles | Supports | Unique page titles are supplied by default. |
| 2.4.3 Focus Order | Focus must move in logical order | Supports | Focus moves in a logical, expected order. |
| 2.4.4 Link Purpose | Link purpose must be clear from text or context | Supports | The purpose of each link can be determined from the link text. |
| 2.5.1 Pointer Gestures | Complex gestures must have simple alternatives | Supports | Simple alternatives are provided. |
| 2.5.2 Pointer Cancellation | Pointer actions must be cancellable | Supports | Pointer interactions can be canceled before completing. |
| 2.5.3 Label in Name | Visible labels must be in accessible names | Supports | Controls and links feature accessible names matching the visual portion. |
| 2.5.4 Motion Actuation | Motion triggers must have alternatives | Supports | No motion-based input is required. |
| 3.1.1 Language of Page | Pages must define their main language | Supports | Default page language is supplied in the head section. |
| 3.2.1 On Focus | Focus should not cause unexpected changes | Supports | Focusing on components does not trigger context changes. |
| 3.2.2 On Input | Input changes shouldn't cause major changes without warning | Supports | Input changes do not trigger significant changes without notice. |
| 3.2.6 Consistent Help | Help should be available consistently | Supports | Help options are provided consistently across applicable views. |
| 3.3.1 Error Identification | Errors must be clearly indicated with descriptions | Supports | Errors are clearly indicated with textual descriptions. |
| 3.3.2 Labels or Instructions | Forms must include clear labels | Supports | Form fields include descriptive labels and/or placeholder instructions. |
| 3.3.7 Redundant Entry | Users shouldn't re-enter the same info | Supports | Previously entered information is retained and reused when possible. |
| 4.1.2 Name, Role, Value | UI components must expose correct info to assistive tech | Supports | All UI elements expose correct name, role, and value using semantic HTML or ARIA. |
Level AA criteria
| Criteria | Explanation | Conformance | Remarks |
|---|---|---|---|
| 1.2.4 Captions (Live) | Live audio must have real-time captions | Not Applicable | Live video content is not present. |
| 1.2.5 Audio Description | Videos must include audio descriptions for visual content | Supports | Video posts include descriptions of important visual elements. |
| 1.3.4 Orientation | Content must work in portrait and landscape | Supports | Content is responsive and works in both orientations. |
| 1.3.5 Identify Input Purpose | Form fields must have autocomplete attributes | Supports | Form fields include autocomplete attributes to identify input purpose. |
| 1.4.3 Contrast (Minimum) | Text must have sufficient contrast (4.5:1) | Partially Supports | Some elements may have insufficient contrast due to company-modifiable design. |
| 1.4.4 Resize Text | Text must resize up to 200% without losing functionality | Supports | Text resizes up to 200% without loss of content or functionality. |
| 1.4.5 Images of Text | Use real text instead of images | Supports | Text is displayed using actual text elements, not images. |
| 1.4.10 Reflow | Content should reflow without horizontal scrolling | Supports | Content reflows at any viewport size. |
| 1.4.11 Non-text Contrast | UI components must meet contrast requirements | Partially Supports | Focus rings may have insufficient contrast. Contrast may vary due to company-modifiable design. |
| 1.4.12 Text Spacing | Adjusting spacing shouldn't break layout | Supports | Adjusting text spacing does not break layout or functionality. |
| 1.4.13 Content on Hover or Focus | Hover/focus content must be dismissible and persistent | Supports | Hover and focus content is persistent and dismissible. |
| 2.4.5 Multiple Ways | Provide multiple ways to find pages | Supports | Users can navigate using menus, arrows, and search. |
| 2.4.6 Headings and Labels | Headings and labels must be descriptive | Supports | Headings and labels clearly describe content structure and purpose. |
| 2.4.7 Focus Visible | Focus must be visually clear | Partially Supports | Focus rings may be inconsistent or difficult to see in some High Contrast themes. |
| 2.4.11 Focus Not Obscured | Focused elements must be visible | Supports | Focused elements remain at least partially visible. |
| 2.5.7 Dragging Movements | Dragging must have simpler alternatives | Supports | All dragging functionality includes tap or click alternatives. |
| 2.5.8 Target Size | Clickable areas must be at least 24×24 px | Supports | All pointer targets meet or exceed the 24×24 pixel minimum. |
| 3.1.2 Language of Parts | Different language content must be marked with lang | Partially Supports | Widgets support full translation. Fallback English text in non-English contexts is not marked with a lang attribute, which may affect screen reader pronunciation. |
| 3.2.3 Consistent Navigation | Navigation must be consistent across pages | Supports | Navigation elements appear consistently across pages. |
| 3.2.4 Consistent Identification | Same functions should be identified consistently | Supports | Components with the same function are identified consistently. |
| 3.3.3 Error Suggestion | Suggest how to fix errors | Supports | Suggestions are provided to help users correct errors. |
| 3.3.4 Error Prevention | Users must be able to review and correct critical inputs | Partially Supports | Review forms show the review on a Summary step before it's submitted, and reviewers can change it later. The upload form has clear steps but no final review before submission. |
| 3.3.8 Accessible Authentication | Login shouldn't require puzzles | Supports | Authentication does not rely solely on cognitive tasks. |
| 4.1.3 Status Messages | Status messages must be announced without stealing focus | Supports | Status messages are announced to assistive technologies without disrupting focus. |