Highlights
Widget navigation
All Cevoid widgets support keyboard navigation and have tags aligned with WCAG standards.Language
Cevoid widgets are automatically localized with the correct language for your workspace markets. Localization includes all accessibility features.Alt text for photo and video posts
All approved posts automatically receive descriptive alt text, translated for all languages activated on your workspace.- Adjust alt text by opening the post and clicking Accessibility
- 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 by opening the post and clicking Accessibility
- Videos with music display [Music playing] as a caption
- Captions can be activated and deactivated in UGC widgets
- Captions are off by default but activate for all videos once a user enables them on one post
- Captions display as an overlay for videos in the widget popup
- Captions and translations are available through the API
Descriptions for videos without captions
Video posts without sound or meaningful captions automatically receive a summarizing description once approved. Descriptions are translated for all languages on your workspace.- Video descriptions display automatically in all UGC widgets in the correct language
- Video descriptions and translations are available through the API
WCAG breakdown
Applicable standards
| Standard | Included |
|---|---|
| Web Content Accessibility Guidelines 2.1 | Level A ✓, Level AA ✓, Level AAA ✗ |
Conformance levels
| Level | Meaning |
|---|---|
| Supports | Cevoid’s consumer-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 consumer-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-texts 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-only media includes descriptive text alternatives. Videos with sound have synchronized captions. Videos without sound have descriptions. No audio-only media is present. |
| 1.2.2 Captions (Prerecorded) | Prerecorded videos with sound must have captions | Supports | Prerecorded videos with audio include synchronized captions. |
| 1.2.3 Audio Description or Media Alternative | Videos with audio must have a text alternative or audio description | Supports | Prerecorded synchronized media includes a full text alternative. |
| 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 | Blinking, scrolling, or auto-updating content is not present. |
| 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 | Prerecorded video includes audio 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×24px | 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 | 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. |