To meet accessibility standards, Mobile Authenticator Studio not only has in-built accessibility features but also supports platform features such as screen readers like TalkBack (Android) and VoiceOver (iOS).
As of version 5.4.0, Mobile Authenticator Studio complies with the minimum requirements foreseen in the European Accessibility Act (EAA) and Level A and AA Conformance of the Web Content Accessibility Guidelines (WCAG) by the World Wide Web Consortium (W3C).
The main focus areas to enhance accessibility verify if an app has the following characteristics:
Perceivable
Is the app adaptable? Are the app contents distinguishable?
Operable
Is a device-external keyboard accessible? Is the app navigable? Does the user have sufficient time to perform tasks?
Understandable
Is the app behavior predictable? Is input assistance provided?
Robust
Can assistive technology properly present page content?
The following is a non-exhaustive list of accessibility requirements and the features with which Mobile Authenticator Studio complies with these requirements.
Adaptability
The Mobile Authenticator Studio app includes the following adaptability features to enhance accessibility:
Portrait and landscape screen orientation
The Mobile Authenticator Studio app can be used in portrait or landscape orientation. The app flows and features function in both screen orientation modes, its contents are not locked to a specific screen orientation. The user chooses the screen orientation on their device.
Because the available screen space is limited in landscape mode, the user will have to scroll to view all screen content.
Meaningful order of the content
Where applicable, the app contents are presented according to the order in which the user must process them. This is also true if screen readers are used.
Distinguishable content
To make it easier for users to see and hear the app contents, Mobile Authenticator Studio supports the following:
Colors and contrast
The default component colors of the Mobile Authenticator Studio app are designed to ensure the contrast is always sufficient. If you customize any of those colors, it is your responsibility to define the main app color and verify if this selected color complies with the requirements foreseen in the European Accessibility Act.
Text resize and content reflow
Text can be maximally resized without loss of information or functionality, and content can be enlarged without increasing the line length. This prevents that the user has to scroll in two dimensions (horizontally and vertically). This also applies to the generated one-time password (OTP). Depending on the font size the user selects in their device settings (medium, big, very big, etc.), the texts in the app will resize to reflect the user’s system preference, and all graphical components will adjust accordingly.
Keyboard Accessible
Mobile Authenticator Studio supports the usage of a device-external keyboard, plugged in via cable or connected via Bluetooth. The user is able to do most actions via this external keyboard and navigate the app content in a correct order. This includes support for the following:
Everything except freehand movements can be done via the external keyboard
No specific timings required for individual keystrokes
Content does not “trap” the user
The keyboard focus does not get stuck on a specific section, screen, or component, and the user is always able to navigate away.
Only the clickable elements of the app (menus, input fields, buttons, links, etc.) can be focused with an external keyboard.
Timing Adjustable
Mobile Authenticator Studio ensures that users have enough time to complete tasks. Specifically, it informs the user about the remaining time the generated one-time password (OTP) is valid, ensuring they are able to perform the required actions in the remaining time.
Navigability
Mobile Authenticator Studio facilitates navigation, finding content, and user orientation across app pages and makes the app screens appear and operate in predictable ways with the following features:
Screen titles
Each screen has a meaningful title which describes the topic or purpose of the screen.
App content can be navigated in the correct order
Where contents can or must be navigated in a given sequence for operability and/or meaningful app use, the user can navigate the content in the correct order.
Headings and labels
Descriptive headings and labels are used to describe the topic or purpose of a screen.
Keyboard focus indicator
The app supports a keyboard focus indicator to ensure the user knows on which element the keyboard is focused.
Predictability
Consistent navigation
Repeated content is displayed in the same places across the app.
Consistent identification
Elements that have the same functionality and are available on several screens are identified consistently.
Consistent help
Help is located in the same place where provided on multiple pages. See also Locating the app version and Help.
Input assistance
Labels or instructions
Labels and/or instructions in the content ensure that users know what information they must enter. The Mobile Authenticator Studio input controls such as fields, checkboxes etc. provide labels or instructions where content requires user input.
Screen readers
The Mobile Authenticator Studio app supports platform features such as TalkBack (Android) and VoiceOver (iOS) and enables its users to navigate through all app screens with gestures and voice control. With the screen readers, components that have the same functionality are identified consistently to make actions more predictable across pages, and labels or instructions are read out aloud when content requires user input so that users know what information to enter.
The one-time password (OTP) generated with the Mobile Authenticator Studio app is also read out aloud.
The following is a selection of user interface elements and screen activities the screen reader reads aloud:
Menu items (e.g. the items of the Settings menu)
Screen contents
Updates on the Home screen for all activated user accounts
Buttons and icons
Actions and actions of the app controls
Workflows (e.g. Offline activation, Scan&Sign, Push&Sign, Change PIN, etc.)
Errors when choosing and confirming the PIN in the corresponding screens
Elements are read in the order they appear. Content descriptions describe the element itself and the context around it. If a screen can be navigated sequentially, the screen elements are read from top left to bottom right.
Gesture-based actions include swipe and finger-tap actions to navigate through the app, activate elements, read screen contents, etc.
The screen readers do not read any elements with small icons (e.g., Pending Request icon, Scan Code icon, Request List icons etc.), or any images at the top of transaction screens (e.g., Approve Request screen image, Request Details screen image etc.).