Accessibility
Keyboard Support
The Eventcalendar supports different views for different jobs and each of these views support keyboard navigation.
Focus can be moved with the Tab
key. Focusable elements depend on the displayed view (more details below).
Buttons can be triggered using the Space
key when focused.
Rendered events act like buttons. When an event is focused, the event click event can be triggered using the Space
or Enter
keys.
Calendar view
Focusable elements are:
- the header buttons: navigation, prev, next and today buttons
- the events rendered on the calendar view
- the currently selected day
When the selected day is focused, the focus can be moved using the Up
, Down
, Left
and Right
arrow keys and set with the Space
or Enter
keys.
When the popover is enabled on events, it can be toggled using the Space
and Esc
keys.
Agenda
Focusable elements are:
- the header buttons: navigation, prev, next and today buttons
- the currently selected day
- the events listed in the agenda
Scheduler
Focusable elements are:
- the header buttons: navigation, prev, next and today buttons
- the events rendered in the scheduler
Timeline
Focusable elements are:
- the header buttons: navigation, prev, next and today buttons
- the events rendered on the timeline
WCAG 2.2
The Web Content Accessibility Guidelines (WCAG) provide guidelines developed by the World Wide Web Consortium (W3C) to ensure web content is accessible to people with disabilities. WCAG 2.2 establishes a framework of accessibility principles and their associated success criteria. The level of accessibility conformance achieved by a web application is determined by the extent to which it meets these success criteria, categorized into three levels: A, AA, and AAA.
While Mobiscroll components are not fully compliant with WCAG 2.2 at this time, we are committed to enhancing their accessibility. We are actively working on improving compliance and continuously making progress.
The guidelines and success criteria are organized around the following four principles:
1. Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
Guidelines | Level | Compatibility | Remarks | |
---|---|---|---|---|
1.1 Text Alternatives | 1.1.1 Non-text Content | A | Supported | aria-label on icon buttons, aria-hidden on decoration elements |
1.2 Time-based Media | 1.2.1 Audio-only and Video-only (Prerecorded) | A | Not Applicable | - |
1.2.2 Captions (Prerecorded) | A | Not Applicable | - | |
1.2.3 Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | - | |
1.2.4 Captions (Live) | AA | Not Applicable | - | |
1.2.5 Audio Description (Prerecorded) | AA | Not Applicable | - | |
1.2.6 Sign Language (Prerecorded) | AAA | Not Applicable | - | |
1.2.7 Extended Audio Description (Prerecorded) | AAA | Not Applicable | - | |
1.2.8 Media Alternative (Prerecorded) | AAA | Not Applicable | - | |
1.2.9 Audio-only (Live) | AAA | Not Applicable | - | |
1.3 Adaptable | 1.3.1 Info and Relationships | A | Supported | - |
1.3.2 Meaningful Sequence | A | Supported | - | |
1.3.3 Sensory Characteristics | A | Supported | - | |
1.3.4 Orientation | AA | Supported | responsiveness works with all orientations | |
1.3.5 Identify Input Purpose | AA | Not applicable | - | |
1.3.6 Identify Purpose | AAA | Supported | - | |
1.4.1 Use of Color | A | Supported | - | |
1.4.2 Audio Control | A | Not Applicable | - | |
1.4.3 Contrast (Minimum) | AA | Not fully supported | by building a height contrast theme | |
1.4.4 Resize Text | AA | Supported | - | |
1.4.5 Images of Text | AA | Not Applicable | - | |
1.4.6 Contrast (Enhanced) | AAA | Not fully supported | by building a height contrast theme | |
1.4.7 Low or No Background Audio | AAA | Not Applicable | - | |
1.4.8 Visual Presentation | AAA | Supported | by building a custom theme or custom CSS | |
1.4.9 Images of Text (No Exception) | AAA | Not Applicable | - | |
1.4.10 Reflow | AA | Supported | in case of Scheduler and Timeline two dimensional scrolling could be necessary but these views are data tables | |
1.4.11 Non-text Contrast | AA | Supported | borders | |
1.4.12 Text Spacing | AA | Supported | can be modified with custom CSS | |
1.4.13 Content on Hover or Focus | AA | Supported | title attribute on event hover |
2. Operable
User interface components and navigation must be operable.
Guidelines | Level | Compatibility | Remarks | |
---|---|---|---|---|
2.1 Keyboard Accessible | 2.1.1 Keyboard | A | Supported | D&D works with mouse and touch control but keyboard alternatives can be implemented ex. add/edit popup |
2.1.2 No Keyboard Trap | A | Supported | - | |
2.1.3 Keyboard (No Exception) | AAA | Supported | D&D works with mouse and touch control but keyboard alternatives can be implemented ex. add/edit popup. In case of the Scheduler and Timeline the onCellClick event is not fired when using the keyboard | |
2.1.4 Character Key Shortcuts | A | Not Applicable | - | |
2.2 Enough Time | 2.2.1 Timing Adjustable | A | Not applicable | - |
2.2.2 Pause, Stop, Hide | A | Not Applicable | - | |
2.2.3 No Timing | AAA | Supported | - | |
2.2.4 Interruptions | AAA | Not Applicable | - | |
2.2.5 Re-authenticating | AAA | Not Applicable | - | |
2.2.6 Timeouts | AAA | Not Applicable | - | |
2.3 Seizures and Physical Reactions | 2.3.1 Three Flashes or Below Threshold | A | Supported | - |
2.3.2 Three Flashes | AAA | Supported | - | |
2.3.3 Animation from Interactions | AAA | Not supported | Calendar view page change animation, all views navigation popup animation | |
2.4 Navigable | 2.4.1 Bypass Blocks | A | Not Applicable | - |
2.4.2 Page Titled | A | Not Applicable | - | |
2.4.3 Focus Order | A | Supported | - | |
2.4.4 Link Purpose (In Context) | A | Not Applicable | - | |
2.4.5 Multiple Ways | AA | Not Applicable | - | |
2.4.6 Headings and Labels | AA | Supported | event structure ex. title, time, etc. | |
2.4.7 Focus Visible | AA | Supported | - | |
2.4.8 Location | AAA | Not Applicable | - | |
2.4.9 Link Purpose (Link Only) | AAA | Not Applicable | - | |
2.4.10 Section Headings | AAA | Not Applicable | - | |
2.4.11 Focus Not Obscured (Minimum) | AA | Supported | - | |
2.4.12 Focus Not Obscured (Enhanced) | AAA | Supported | - | |
2.4.13 Focus Appearance | AAA | Not supported | - | |
2.5 Input Modalities | 2.5.1 Pointer Gestures | A | Supported | - |
2.5.2 Pointer Cancellation | A | Supported | - | |
2.5.3 Label in Name | A | Supported | - | |
2.5.4 Motion Actuation | A | Not Applicable | - | |
2.5.5 Target Size (Enhanced) | AAA | Not fully supported | exception the resize handle | |
2.5.6 Concurrent Input Mechanisms | AAA | Supported | - | |
2.5.7 Dragging Movements | AA | Supported | D&D works with mouse and touch control but keyboard alternatives can be implemented ex. add/edit popup | |
2.5.8 Target Size (Minimum) | AA | Not fully supported | exception the resize handle |
3. Understandable
Information and the operation of user interface must be understandable.
Guidelines | Level | Compatibility | |
---|---|---|---|
3.1 Readable | 3.1.1 Language of Page | A | Not Applicable |
3.1.2 Language of Parts | AA | Not Applicable | |
3.1.3 Unusual Words | AAA | Not Applicable | |
3.1.4 Abbreviations | AAA | Supported | |
3.1.5 Reading Level | AAA | Not Applicable | |
3.1.6 Pronunciation | AAA | Not Applicable | |
3.2 Predictable | 3.2.1 On Focus | A | Supported |
3.2.2 On Input | A | Not Applicable | |
3.2.3 Consistent Navigation | AA | Not Applicable | |
3.2.4 Consistent Identification | AA | Not Applicable | |
3.2.5 Change on Request | AAA | Not Applicable | |
3.2.6 Consistent Help | A | Not Applicable | |
3.3 Input Assistance | 3.3.1 Error Identification | A | Not Applicable |
3.3.2 Labels or Instructions | A | Not Applicable | |
3.3.3 Error Suggestion | AA | Not Applicable | |
3.3.4 Error Prevention (Legal, Financial, Data) | AA | Not Applicable | |
3.3.5 Help | AAA | Not Applicable | |
3.3.6 Error Prevention (All) | AAA | Not Applicable | |
3.3.7 Redundant Entry | A | Not Applicable | |
3.3.8 Accessible Authentication (Minimum) | AA | Not Applicable | |
3.3.9 Accessible Authentication (Enhanced) | AAA | Not Applicable |
4. Robust
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Guidelines | Level | Compatibility | |
---|---|---|---|
4.1 Compatible | 4.1.1 Parsing (Obsolete and removed) | - | - |
4.1.2 Name, Role, Value | A | Supported | |
4.1.3 Status Messages | AA | Not Applicable |