Discover the Wooclap templates!
Get started in a few seconds with Wooclap thanks to templates created for you ✨
Accessibility Statement for Wooclap
Accessibility Statement for Wooclap
Wooclap is committed to ensuring digital accessibility for people with disabilities. Wooclap is a web application which helps teachers and speakers interact with their audience using the participant’s devices. By design, Wooclap offers two different experiences: one for presenters and one for participants. Presenters have the option to create and configure interactive presentations, while participants use a simplified interface which allows them to quickly participate and answer or ask questions.
We are continually improving the user experience for everyone, and applying the relevant accessibility standards. The Participant Interface meets WCAG 2.1 at the AA level with some limitations listed below. We will focus on the Presenter Interface at a later stage.
Conformance status
The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. Wooclap Participant Interface is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.
The following table shows the efforts which still need to be done to comply with all WCAG criteria for the participant interface.
| Name | Lvl | Status | Comment |
|---|---|---|---|
| Principle 1 - Perceivable | |||
| 1.1.1 Non-text Content | A | Support | For user generated content (such as question image attachments), presenters have the option to add a textual alternative. |
| 1.1.1 Non-text Content | A | Support | For user generated content (such as question image attachments), presenters have the option to add a textual alternative. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | Support | For user generated content (such as audio or video files attached to a presentation), presenters have the option to add a video transcript |
| 1.2.2 Captions (Prerecorded) | A | Support | Presenter can add videos using the Youtube platforms, which supports captions. |
| 1.2.3 Audio Description or Media Alternative | A | Does Not Support | See 1.2.1 |
| 1.2.4 Captions (Live) | AA | Not Applicable | No Live content |
| 1.2.5 Audio Description (Prerecorded) | AA | Does Not Support | See 1.2.1 |
| 1.3.1 Info and Relationships | A | Support | ARIA landmark and labels are included for interactive elements when necessary |
| 1.3.2 Meaningful Sequence | A | Support | DOM order matches the visual order |
| 1.3.3 Sensory Characteristics | A | Support | ARIA labels or visible textual labels are included for components. |
| 1.3.4 Orientation | AA | Support | Wooclap works for all device orientations |
| 1.3.5 Identify Input Purpose | AA | Support | Input fields are correctly labelled |
| 1.4.1 Use of Color | A | Support | Color is never used as the only visual means of conveying information |
| 1.4.2 Audio Control | A | Support | All possible audio sources contain pause/stop controls |
| 1.4.3 Contrast (Minimum) | AA | Support | Text and background color have been chosen to remain above the contrast threshold. |
| 1.4.4 Resize text | AA | Partially Support | Text is resizable using the web browser controls, however zooming is currently disabled for smartphones. |
| 1.4.5 Images of Text | AA | Support | No such text in our interface (except for presenter-uploaded content or logos) |
| 1.4.10 Reflow | AA | Support | Text does stays in one column (no horizontal scroll) even when zoomed |
| 1.4.11 Non-text Contrast | AA | Support | Colors have been chosen to remain above the contrast threshold |
| 1.4.12 Text Spacing | AA | Support | The interface supports the required text style properties. |
| 1.4.13 Content on Hover or Focus | AA | Not Applicable | No additional content on hover or focus |
| Principle 2 - Operable | |||
| 2.1.1 Keyboard | A | Support | All functionalities are operable with a keyboard-only setup. |
| 2.1.2 No Keyboard Trap | A | Support | There are no keyboard traps. |
| 2.1.4 Character Key Shortcuts | A | Not Applicable | No such shortcuts: letter (including upper- and lower-case letters), punctuation, number, or symbol characters |
| 2.2.1 Timing Adjustable | A | Not Applicable | No such timing constraints, except for an optional timer to answer questions controlled by the presenter |
| 2.2.2 Pause, Stop, Hide | A | Not Applicable | No moving, blinking or scrolling animation. No auto-updating part except for essential (real-time) parts |
| 2.3.1 Three Flashes or Below Threshold | A | Not Applicable | The interface does not flashe |
| 2.4.1 Bypass Blocks | A | Support | Repeated content is skippable using ARIA landmarks |
| 2.4.2 Page Titled | A | Support | Relevant title are provided to each page |
| 2.4.3 Focus Order | A | Support | Tab order follows semantical order |
| 2.4.4 Link Purpose (In Context) | A | Support | Links are correctly labelled |
| 2.4.5 Multiple Ways | AA | Does Not Apply | Wooclap works as a Single-Page application |
| 2.4.6 Headings and Labels | AA | Support | Heading and labels are used to structure the page content |
| 2.4.7 Focus Visible | AA | Support | All interactive components have a visible focus state |
| 2.5.1 Pointer Gestures | A | Does Not Apply | No functionality requires path-based gestures |
| 2.5.2 Pointer Cancellation | A | Support | Buttons never executes on the mousedown event |
| 2.5.3 Label in Name | A | Support | Visual names and Accessible names are the same |
| 2.5.4 Motion Actuation | A | Does Not Apply | No such functionalities in Wooclap |
| Principle 3 - Understandable | |||
| 3.1.1 Language of Page | A | Partially Support | The “lang” attribute in the HTML is always set to English, but the language of the content will be correctly identified with lower-level attributes.. |
| 3.1.2 Language of Parts | AA | Support | The language of the interface is configurable by the user, and the chosen language will be correctly applied to the interface with a “lang” attribute |
| 3.2.1 On Focus | A | Support | Focus never changes the context (state) |
| 3.2.2 On Input | A | Support | Input never changes the context (state) |
| 3.2.3 Consistent Navigation | AA | Support | |
| 3.2.4 Consistent Identification | AA | Support | |
| 3.3.1 Error Identification | A | Does Not Support | Error message are not always accessible |
| 3.3.2 Labels or Instructions | A | Support | User inputs are always labelled in an accessible way |
| 3.3.3 Error Suggestion | AA | Does not Supports | Error message on input error are not always accessible |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Not Applicable | No such content |
| Principle 4 - robust | |||
| 4.1.1 Parsing | A | Support | Valid HTML is used |
| 4.1.2 Name, Role, Value | A | Support | ARIA properties are used when relevant |
| 4.1.3 Status Messages | AA | Does Not Support | Status message cannot be correctly interpreted by assistive technologies |
Feedback
We welcome your feedback on the accessibility of Wooclap Participant Interface. Please let us know if you encounter accessibility barriers on Wooclap Participant Interface: info@wooclap.com.
This statement was last updated on 21 June 2020