Nyheter 17 december, 2020

Mobile accessibility: WCAG principles and how it improves UX (Part 3)

As WCAG 2.0 puts it, this principle encourages “information and the operation of user interface must be understandable.” Not only must a digital product be easily perceived (see part 1 of this series) and operated (see part 2 of this series) by a user with physical limitations, it must also be easy to digest the information. This includes elements like making text readable, making app screens or web pages predictable, and allowing for more cushion for inadvertent mistakes.

Principle 3:  Understandable

Changing Screen Orientation 

Consider users that have their mobile devices mounted in a fixed position and that they may not have the option of changing display orientation. Make sure to support both landscape and portrait.

Consistent  Layout

Repeated components appearing across multiple screens should be presented consistently in its placements regardless of screen size, type or orientation.

Positioning important page elements before the page scroll

Placing important elements before the page scroll, consistent and predictable location of elements, makes it possible to locate content without performing an interaction.  assists people with cognitive impairments and low vision.

Grouping operable elements that perform the same action

When elements execute the same action or go land on the same destination, these should be contained within the same actionable element reduces redundant targets.

 

It improves touch target size that helps users with dexterity limitations.

Provide clear indication that elements are actionable

Make it obvious that elements are actionable like buttons or links. Ensure that it is distinguishable in terms of its visual features that include shape, color, style, positioning, text label for an action, and conventional iconography.

 

These benefits all users, but especially users with vision impairments.

Provide instructions for custom touchscreen and device manipulation gestures

Supply a brief ´how to´ instructions on what gestures to navigate through the interface and specify alternatives, if any.

 

These instructions should be easily accessible across the application for it to be beneficial.