Skip to main content
Intellum

Outline

This article details a point in the Web Content Accessibility Guidelines and what the implications are for creating accessible course content in Evolve and is part of a larger path.

To view the full guidelines, please visit the Accessibility: WCAG 2.1 and Evolve path.

Guideline 2.5.1


Pointer Gestures Level A All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

Explanation


This isn’t very applicable to eLearning; instead, it’s more concerned with mobile (or sometimes desktop) applications where more complex or multiple gestures are used to make something happen, for instance, pinch and zoom on a map application on a touch screen device.

What does this mean for your content in Evolve?


With regards to touch screen devices, Evolve is fully responsive. A learner shouldn't need to pinch and zoom in to access content, it should all be legible and accessible in its default view. The only component that fails this criterion is the Drag and Drop Component - but you can use the Card Drop Component instead, which has the same functionality but is fully accessible on touch screen devices.

Guideline 2.5.2


Pointer Cancellation Level A For functionality that can be operated using a single pointer, at least one of the following is true:

  • No Down-Event: The down-event of the pointer is not used to execute any part of the function;
  • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is essential*.*

Explanation


This refers to actions being caused either by the initial mouse click - the ‘down’ event, e.g. before your finger has lifted up from your mouse button, and the ability to stop the action happening. This is to aid users who may be more likely to click or press something in error, and ensuring there’s a way to stop the action happening of not intended.

What does this mean for your content in Evolve?


Nothing happens in Evolve solely on a down click - it's always on the up event (e.g. when you release your finger from the mouse). If a learner clicks a button in error, they can then move their mouse away from that object before the up event, and that action will not happen.

Guideline 2.5.3


Label in Name Level A For user interface components with labels that include text or images of text, the name contains the text that is presented visually.

Explanation


This refers to making sure buttons, such as navigational elements, have the same name programmatically as any text label on them. For instance, if a menu button for a section is labelled ‘View’ then assistive technologies will also recognise the button name as ‘View’.

What does this mean for your content in Evolve?


This is not an issue in Evolve content - everything should be represented with the same name, and allow users to manually change the visual name as well as enter corresponding aria labels.

Guideline 2.5.4


Motion Actuation Level A Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when:

  • Supported Interface: The motion is used to operate functionality through an accessibility-supported interface;
  • Essential: The motion is essential for the function and doing so would invalidate the activity.

Explanation


This refers to touchscreen devices having functions caused by moving the device in a certain way of gesturing in a certain way to cause actions to happen.

What does this mean for your content in Evolve?


This isn’t applicable to Evolve content — there is nothing that requires a motion or gesture to work.

Guideline 2.5.5


Target Size Level AAA The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when:

  • Equivalent: The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels;
  • Inline: The target is in a sentence or block of text;
  • User Agent Control: The size of the target is determined by the user agent and is not modified by the author;
  • Essential: A particular presentation of the target is essential to the information being conveyed.

Explanation


This refers to buttons or links on screen, and that they should have a minimum size of 44 x 44 pixels.

What does this mean for your content in Evolve?


In the default themes available in Evolve, the default sizes of all buttons will meet these criteria. If users create their own themes, they need to check the theme editor to ensure that those items still meet the minimum requirements.

Guideline 2.5.6


Concurrent Input Mechanisms Level AAA Web content does not restrict the use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings.

Explanation


This refers to not restricting learners to one particular form of input - e.g. being able to only perform an action on screen with a mouse.

What does this mean for your content in Evolve?


Everything in Evolve output can be operated by the keyboard, and the user can switch between mouse and keyboard seamlessly, should they need to.

Did this article help?

Let us know by leaving a star rating or review at the top of this article.

Skills
0