Wooclap Logo
Homepage

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.

NameLvlStatusComment
Principle 1 - Perceivable
1.1.1 Non-text ContentAPartial SupportThere are only a few elements in the interface that lack alt-text (logo, profile picture, language flags, participant log in illustration). All author-generated content can contain an alt-text.
1.2.1 Audio-only and Video-only (Prerecorded)ANo SupportFor author-generated content (such as audio or video files attached to a presentation), presenters have the option to add an audio/video transcript, with the exception of adding sounds to questions titles and options in the Participant pace mode.
1.2.2 Captions (Prerecorded)ASupportPresenters can add videos using media platforms (YouTube, Vimeo, Dailymotion…) which support captions.
1.2.3 Audio Description or Media AlternativeANot applicableThe participant interface does not contain any synchronized media.
1.2.4 Captions (Live)AANot ApplicableThere is no Live content in the application.
1.2.5 Audio Description (Prerecorded)AANot applicableSee 1.2.3
1.2.6 Sign Language (Prerecorded)AAANot applicableSee 1.2.3
1.2.7 Extended Audio Description (Prerecorded)AAANot applicableSee 1.2.3
1.2.8 Media Alternative (Prerecorded)AAASupportSee 1.2.1 & 1.2.3
1.2.9 Audio-only (Live)AAANot applicableSee 1.2.4
1.3.1 Info and RelationshipsASupportWhen necessary, ARIA landmarks and labels are included for interactive elements.
1.3.2 Meaningful SequenceASupportDOM order matches the visual order
1.3.3 Sensory CharacteristicsASupportThe instructions provided for understanding and operating content are always combined with text.
1.3.4 OrientationAASupportWooclap works for all device orientations.
1.3.5 Identify Input PurposeAASupportInput fields are correctly labelled
1.3.6 Identify PurposeAAASupportThe purpose of user interface components, icons, and regions can be programmatically determined.
1.4.1 Use of ColorASupportColor is never used as the only visual means of conveying information.
1.4.2 Audio ControlASupportAll possible audio sources contain pause/stop controls.
1.4.3 Contrast (Minimum)AASupportText and background color have been chosen to remain above the contrast threshold.
1.4.4 Resize textAANo SupportText is resizable using the web browser controls, although doing so may incur a loss of functionality in some modals and sidebar.
1.4.5 Images of TextAASupportThere is no such text in our interface (except for author-uploaded content or logos)
1.4.6 Contrast (Enhanced)AAANo SupportCertain combinations of text & background only achieve an AA ratio.
1.4.7 Low or No Background AudioAAANot applicableThere is no sound in the interface, except for presenter-uploaded content.
1.4.8 Visual PresentationAAANo SupportThere is no mechanism available for the user to change text & background color, nor line spacing.
1.4.9 Images of Text (No Exception)AAASupportThere is no such text in our interface (except for presenter-uploaded content or logos).
1.4.10 ReflowAASupportText stays in one column (no horizontal scroll) even when zoomed
1.4.11 Non-text ContrastAASupportColors have been chosen to remain above the contrast threshold
1.4.12 Text SpacingAASupportThe interface supports the required text style properties.
1.4.13 Content on Hover or FocusAANo SupportWhen logged in on the /public page on a desktop, the profile can be hovered, but cannot be dismissed without moving the mouse.
Principle 2 - Operable
2.1.1 KeyboardASupportAll features are operable with a keyboard-only setup.
2.1.2 No Keyboard TrapASupportThere are no keyboard traps.
2.1.3 Keyboard (No Exception)AAANo SupportSome questions (like “Find on image”) require a precise position pinning that cannot be achieved through keyboard.
2.1.4 Character Key ShortcutsANot ApplicableThere are no such shortcuts: letter (including upper- and lower-case letters), punctuation, number, or symbol characters
2.2.1 Timing AdjustableANot ApplicableThere are no such timing constraints, except as an optional timer to answer questions controlled by the presenter
2.2.2 Pause, Stop, HideANot ApplicableThere is no moving, blinking or scrolling animation. There are no auto-updating elements, except for essential (real-time) items
2.2.3 No TimingAAASupportThere are no such timing constraints, except as an optional timer to answer questions controlled by the presenter.
2.2.4 InterruptionsAAASupportThere are no interruptions, other than flow of the event determined by the presenter, which can prevent a user to answer to a question.
2.2.5 Re-authenticatingAAANo SupportPreviously submitted answers will be kept, but answers that have not been submitted yet will be lost when logging out, and will require the user to re-submit them.
2.2.6 TimeoutsAAASupportThere is no timeout due to user inactivity.
2.3.1 Three Flashes or Below ThresholdASupportThe interface does not flash.
2.3.2 Three FlashesAAASupportThe interface does not flash.
2.3.3 Animation from InteractionsAAANot applicableThere are no motion animations on the participant interface.
2.4.1 Bypass BlocksANot applicableThere is no significant repeated content in the participant interface.
2.4.2 Page TitledANo SupportSubpages of events, such as participant pace questionnaires, are not identifiable via a title tag.
2.4.3 Focus OrderASupportTab order follows semantical order.
2.4.4 Link Purpose (In Context)ASupportLinks are correctly labelled.
2.4.5 Multiple WaysAASupportThe participant interface works as a Single-Page application, so pages are always part of a process.
2.4.6 Headings and LabelsAASupportHeading and labels are used to structure the page content
2.4.7 Focus VisibleAASupportAll interactive components have a visible focus state
2.4.8 LocationAAANot applicableThe participant interface works as a Single-Page application.
2.4.9 Link Purpose (Link Only)AAASupportLinks are correctly labelled.
2.4.10 Section HeadingsAAANot applicableThe participant interface is not segmented into different sections of content.
2.4.11 Focus Not Obscured (Minimum)AASupportAuthor-created content never obscures user interface components that can be interacted with, even partially.
2.4.12 Focus Not Obscured (Enhanced)AAASupportAuthor-created content never obscures user interface components that can be interacted with, even partially.
2.4.13 Focus AppearanceAAANo SupportSome legacy components still do not conform to this restriction.
2.5.1 Pointer GesturesADoes Not applicableThere are no features that requires path-based gestures.
2.5.2 Pointer CancellationASupportButtons do not execute on the mousedown event.
2.5.3 Label in NameASupportName is used very little in the code, so cannot match with visible labels.
2.5.4 Motion ActuationANot applicableThere is no such feature in Wooclap.
2.5.5 Target Size (Enhanced)AAANo SupportSome components can be as small as 32x32px.
2.5.6 Concurrent Input MechanismsAAASupportThere are no restrictions on the use of input modalities.
2.5.7 Dragging MovementsAASupportFeatures that require dragging movements can be achieved by a single pointer without dragging.
2.5.8 Target Size (Minimum)AASupportAll interactive components are more than 24x24 pixels.
Principle 3 - Understandable
3.1.1 Language of PageASupportThe “lang” attribute in the HTML always follows the language selected by the user.
3.1.2 Language of PartsAASupportThe human language of each passage or phrase in the content can be programmatically determined.
3.1.3 Unusual WordsAAANo SupportNo such mechanism is available in the application.
3.1.4 AbbreviationsAAANo SupportNo such mechanism is available in the application.
3.1.5 Reading LevelAAANo SupportNo such mechanism is available in the application.
3.1.6 PronunciationAAANo SupportNo such mechanism is available in the application.
3.2.1 On FocusASupportFocus never changes the context (state).
3.2.2 On InputASupportInput never changes the context (state).
3.2.3 Consistent NavigationAASupportAs a single-page application, navigational mechanisms that are repeated occur in the same relative order.
3.2.4 Consistent IdentificationAANo SupportLack of accessible names hinder this criterion.
3.2.5 Change on RequestAAAPartial SupportUsers are always in control of changes in context, except when the presenter changes the question being presented.
3.2.6 Consistent HelpANot applicableThere is no help mechanism on the participant interface.
3.3.1 Error IdentificationANo SupportError message are not always accessible or in context.
3.3.2 Labels or InstructionsANo SupportUser inputs sometimes lack labels or instructions.
3.3.3 Error SuggestionAANo SupportError message on input error are not always accessible.
3.3.4 Error Prevention (Legal, Financial, Data)AASupportUser-controllable data such as profile information can be updated without restriction.
3.3.5 HelpAAANo SupportContext-sensitive help is not always available.
3.3.6 Error Prevention (All)AAANo SupportSubmissions are not always reversible.
3.3.7 Redundant EntryANot applicableThere is no redundant input in the participant interface.
3.3.8 Accessible Authentication (Minimum)AASupportSupport for password entry by password managers, as well as copy & paste, are available to input passwords. 3rd party authentication is also available.
3.3.9 Accessible Authentication (Enhanced)AAASupportSee 3.3.8
Principle 4 - robust
4.1.1 ParsingANot applicableThis criterion is obsolete and was removed from WCAG 2.2
4.1.2 Name, Role, ValueASupportARIA properties are used when relevant
4.1.3 Status MessagesAANo SupportStatus 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 16 June 2024