Skip to main content
Version: 5.34.0

Accessibility

Keyboard Support

The Tab and Shift + Tab keys can be used to navigate between the Form elements.

Buttons can be activated using the Space key.

The Up, Down, Left, Right arrows to change the selected segmented item.

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.

GuidelinesLevelCompatibilityRemarks
1.1 Text Alternatives1.1.1 Non-text ContentASupportedname, label, and aria-label can be specified
1.2 Time-based Media1.2.1 Audio-only and Video-only (Prerecorded)ANot Applicable-
1.2.2 Captions (Prerecorded)ANot Applicable-
1.2.3 Audio Description or Media Alternative (Prerecorded)ANot Applicable-
1.2.4 Captions (Live)AANot Applicable-
1.2.5 Audio Description (Prerecorded)AANot Applicable-
1.2.6 Sign Language (Prerecorded)AAANot Applicable-
1.2.7 Extended Audio Description (Prerecorded)AAANot Applicable-
1.2.8 Media Alternative (Prerecorded)AAANot Applicable-
1.2.9 Audio-only (Live)AAANot Applicable-
1.3 Adaptable1.3.1 Info and RelationshipsASupported-
1.3.2 Meaningful SequenceASupported-
1.3.3 Sensory CharacteristicsASupported-
1.3.4 OrientationAASupportedresponsiveness works with all orientations
1.3.5 Identify Input PurposeAASupportedinput type, autocomplete, icon, and description can be specified
1.3.6 Identify PurposeAAASupported-
1.4 Distinguishable1.4.1 Use of ColorASupported-
1.4.2 Audio ControlANot Applicable-
1.4.3 Contrast (Minimum)AANot fully supportedby building a height contrast theme
1.4.4 Resize TextAASupported-
1.4.5 Images of TextAANot Applicable-
1.4.6 Contrast (Enhanced)AAANot fully supportedby building a height contrast theme
1.4.7 Low or No Background AudioAAANot Applicable-
1.4.8 Visual PresentationAAASupportedby building a custom theme or custom CSS
1.4.9 Images of Text (No Exception)AAANot Applicable-
1.4.10 ReflowAASupported-
1.4.11 Non-text ContrastAASupported-
1.4.12 Text SpacingAASupportedcan be modified with custom CSS
1.4.13 Content on Hover or FocusAANot Applicable-

2. Operable

User interface components and navigation must be operable.

GuidelinesLevelCompatibilityRemarks
2.1 Keyboard Accessible2.1.1 KeyboardASupported-
2.1.2 No Keyboard TrapASupported-
2.1.3 Keyboard (No Exception)AAASupported-
2.1.4 Character Key ShortcutsANot Applicable-
2.2 Enough Time2.2.1 Timing AdjustableANot applicable-
2.2.2 Pause, Stop, HideANot Applicable-
2.2.3 No TimingAAASupported-
2.2.4 InterruptionsAAANot Applicable-
2.2.5 Re-authenticatingAAANot Applicable-
2.2.6 TimeoutsAAANot Applicable-
2.3 Seizures and Physical Reactions2.3.1 Three Flashes or Below ThresholdASupported-
2.3.2 Three FlashesAAASupported-
2.3.3 Animation from InteractionsAAANot fully supportedanimations for the Switch and Segmented button can't be turned off
2.4 Navigable2.4.1 Bypass BlocksANot Applicable-
2.4.2 Page TitledANot Applicable-
2.4.3 Focus OrderASupported-
2.4.4 Link Purpose (In Context)ANot Applicable-
2.4.5 Multiple WaysAANot Applicable-
2.4.6 Headings and LabelsAASupported-
2.4.7 Focus VisibleAASupported-
2.4.8 LocationAAANot Applicable-
2.4.9 Link Purpose (Link Only)AAANot Applicable-
2.4.10 Section HeadingsAAANot Applicable-
2.4.11 Focus Not Obscured (Minimum)AASupported-
2.4.12 Focus Not Obscured (Enhanced)AAASupported-
2.4.13 Focus AppearanceAAANot fully supported-
2.5 Input Modalities2.5.1 Pointer GesturesASupported-
2.5.2 Pointer CancellationASupported-
2.5.3 Label in NameASupported-
2.5.4 Motion ActuationANot Applicable-
2.5.5 Target Size (Enhanced)AAASupported-
2.5.6 Concurrent Input MechanismsAAASupported-
2.5.7 Dragging MovementsAASupported-
2.5.8 Target Size (Minimum)AASupported-

3. Understandable

Information and the operation of user interface must be understandable.

GuidelinesLevelCompatibilityRemarks
3.1 Readable3.1.1 Language of PageANot Applicable-
3.1.2 Language of PartsAANot Applicable-
3.1.3 Unusual WordsAAANot Applicable-
3.1.4 AbbreviationsAAANot Applicable-
3.1.5 Reading LevelAAANot Applicable-
3.1.6 PronunciationAAANot Applicable-
3.2 Predictable3.2.1 On FocusASupported-
3.2.2 On InputANot Applicable-
3.2.3 Consistent NavigationAANot Applicable-
3.2.4 Consistent IdentificationAANot Applicable-
3.2.5 Change on RequestAAANot Applicable-
3.2.6 Consistent HelpANot Applicable-
3.3 Input Assistance3.3.1 Error IdentificationASupportedusing the `error` and `error-message` options
3.3.2 Labels or InstructionsASupportedcan be defined through `label`, `aria-label`, and `description` options
3.3.3 Error SuggestionAASupportedusing the `error` and `error-message` options
3.3.4 Error Prevention (Legal, Financial, Data)AANot Applicable-
3.3.5 HelpAAANot Applicable-
3.3.6 Error Prevention (All)AAANot Applicable-
3.3.7 Redundant EntryANot Applicable-
3.3.8 Accessible Authentication (Minimum)AANot Applicable-
3.3.9 Accessible Authentication (Enhanced)AAANot Applicable-

4. Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

GuidelinesLevelCompatibility
4.1 Compatible4.1.1 Parsing (Obsolete and removed)--
4.1.2 Name, Role, ValueASupported
4.1.3 Status MessagesAANot Applicable