Pluxee Mobile Application - VPAT

Accessibility Conformance Report

(Based on VPAT® Version 2.5Rev)

Scope and Methodology

Name of Product/Version:

EVA for Android and iOS 1.4.6

Report Date:

October 2025

Product Description:

An employee benefit app that lets you manage your employee benefits effortlessly in one secure place. You can check balances, track spending, and discover where to use your benefits. Pay easily with Apple Pay or Google Pay. And finally, unlock exclusive offers and make your benefits go further.

Contact Information:

Evaluation Methods Used:

The evaluation has been conducted by an accessibility professional, through manual and functional testing:

  • Colour Contrast Analyzer
  • Device display settings (text resizing, magnifying, color preferences, screen rotation)
  • Talkback screen reader (Android)
  • Voice Over screen reader for iOS
  • Keyboard navigation

The Mobile Application Accessibility Assessment Framework (RAAM 1.1) provided by the government of Luxemburg has been followed to assess more specifically the European directives (EN 301 549).

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Standard/Guideline Included In Report
Web Content Accessibility Guidelines 2.0

Level A: Yes

Level AA: Yes

Level AAA: No
Web Content Accessibility Guidelines 2.1

Level A: Yes

Level AA: Yes

Level AAA: No
Web Content Accessibility Guidelines 2.2

Level A: Yes

Level AA: Yes

Level AAA: No

EN 301 549 Accessibility requirements for ICT products and services - V3.1.1 (2019-11)

AND

EN 301 549 Accessibility requirements for ICT products and services - V3.2.1 (2021-03)

 Yes

Terms

The terms used in the Conformance Level information are defined as follows:

  • Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
  • Partially Supports: Some functionality of the product does not meet the criterion.
  • Does Not Support: The majority of product functionality does not meet the criterion.
  • Not Applicable: The criterion is not relevant to the product.
  • Not Evaluated: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.

WCAG 2.x Report

Tables 1 and 2 also document conformance with EN 301 549:

  • Clause 9 - Web
  • Clauses 10.1-10.4 of Clause 10 - Non-Web documents
  • Clauses 11.1-11.4 and 11.8.2 of Clause 11 - Software
  • Clauses 12.1.2 and 12.2.4 of Clause 12 - Documentation and support services

Note: When reporting on conformance with the WCAG 2.2 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.

Table 1: Success Criteria, Level A

Criteria Conformance Level Remarks and Explanations

1.1.1 Non-text Content

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.1.1.1 (Web)
  • 10.1.1.1 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Partially supports

The app provides sufficient text alternatives for most instances of non-text content and hide most instances of decorative elements to assistive technologies.

Exceptions include:

  • The warning symbol used to distinguish failed transactions in the Transaction Listing is not returned to assistive technologies. Reviewing the Transaction Details retrieves access to this information.
  • The "/" characters used for remaining credits in the Card Listing are not rendered (iOS) or literally rendered (Android) by the screen reader. Accessible indication about the remaining credits is available, either on the dashboard or the Card Details.
  • A few decorative images are exposed to Assistive Technologies (AT). These images provide accurate but redundant information to AT users.

1.2.1 Audio-only and Video-only (Prerecorded)

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.1.2.1 (Web)
  • 10.1.2.1 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)
 Not Applicable The application includes neither prerecorded audio-only or video-only media.

1.2.2 Captions (Prerecorded)

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.1.2.2 (Web)
  • 10.1.2.2 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)
 Not Applicable The application includes no prerecorded synchronized media.

1.2.3 Audio Description or Media Alternative (Prerecorded)

(Level A)

 Not Applicable The application includes no prerecorded video content that would require audio description or a media alternative.

1.3.1 Info and Relationships

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.1.3.1 (Web)
  • 10.1.3.1 (non-web document)
  • 2.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Partially supports

Most visual structure and relationship information is provided through object information or is available in text.

Exceptions include:

  • The account creation stepper is not structured as a list.

1.3.2 Meaningful Sequence

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.1.3.2 (Web)
  • 10.1.3.2 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Partially supports

In most cases, contents are presented in a meaningful sequence.

Exceptions include:

  • Inside the Transaction Details, the “name” and “date” labels are accessed before their respective data.
  • Inside the Card Listing, the text “Blocked” is not immediately preceded or followed by the name of the closed card.
  • Inside the Account, the label of the Gender field is exposed after the field.

1.3.3 Sensory Characteristics

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.1.3.3 (Web)
  • 10.1.3.3 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 Information does not rely solely on sensory characteristics.

1.4.1 Use of Color

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.1.4.1 (Web)
  • 10.1.4.1 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 Contents and functionalities do not convey information through color alone.

1.4.2 Audio Control

(Level A)

 Not Applicable The application includes no audio that plays automatically.

2.1.1 Keyboard

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.2.1.1 (Web)
  • 10.2.1.1 (non-web document)
  • 2.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Partially supports

Most application functionality can be accessed and operated using a keyboard.

Exceptions include:

  • In both Android and iOS web views, the link to reset the password is not focusable. Until this exception is fixed, beneficiaries are invited to use the features on the web application.
  • In iOS web views, merchant places cannot be browsed, searched or consulted using a keyboard. Switch Control can be used as a workaround, otherwise beneficiaries are invited to use these features on the web application.

2.1.2 No Keyboard Trap

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.2.1.2 (Web)
  • 10.2.1.2 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 The application contains no keyboard trap.

2.1.4 Character Key Shortcuts

(Level A 2.1 and 2.2)

 Not Applicable The application includes no character key shortcut.

2.2.1 Timing Adjustable

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.2.2.1 (Web)
  • 10.2.2.1 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Partially supports

For most interactions, the application imposes no time limit.

Exceptions include:

  • The time to retrieve the authentication code sent by email or SMS is limited to 5 minutes. Once configured, biometric authentication may be used as an alternative method.
  • The time to copy-paste the PIN code of the benefit card is limited to 30 seconds.

Note: These constraints are set for security reasons to protect the beneficiary's data.

2.2.2 Pause, Stop, Hide

(Level A)

 Not Applicable The application includes no element that moves, blinks, scrolls, or auto-updates.

2.3.1 Three Flashes or Below Threshold

(Level A)

 Not Applicable The application includes no flashing content.

2.4.1 Bypass Blocks

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.2.4.1 (Web)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

The application provides several ways to bypass blocks, depending on the screen:

  • Section headings
  • Collapsible panels
  • ARIA landmarks (web views)

2.4.2 Page Titled

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.2.4.2 (Web)
  • 10.2.4.2 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

 

Android (PDF): Partially supports

iOS (PDF): Partially supports

 

Most web views and PDF documents hosted in the application have a relevant title.

Exceptions include:

  • Pluxee Connect Privacy Policy (PDF document)

2.4.3 Focus Order

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.2.4.3 (Web)
  • 10.2.4.3 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Partially supports

The application’s components receive focus in a meaningful order.

Exceptions include :

  • In the “Merchant Map” web view, users can navigate through the hidden elements of the carrousel
  • The focus can navigate out of the cookie modal.

2.4.4 Link Purpose (In Context)

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.2.4.4 (Web)
  • 10.2.4.4 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 The purpose of each link in the application can be determined from the link text alone or from the programmatic context of the link.

2.5.1 Pointer Gestures

(Level A 2.1 and 2.2)

Also applies to EN 301 549 Criteria:

  • 9.2.5.1 (Web)
  • 10.2.5.1 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Partially supports

Most multi-point or path-based gestures included by the application can be operated with a single-point action.

Exceptions include:

  • Swipe is used to rotate carousels on the application dashboard, with no alternative single-point action. However, a “see all” button provides access to the carousel elements, with a standard scrolling behavior.

2.5.2 Pointer Cancellation

(Level A 2.1 and 2.2)

Also applies to EN 301 549 Criteria:

  • 9.2.5.2 (Web)
  • 10.2.5.2 (non-web document)
  • 112.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 Every single-point action included in the application is completed when the user releases the pointer.

2.5.3 Label in Name

(Level A 2.1 and 2.2)

Also applies to EN 301 549 Criteria:

  • 9.2.5.3 (Web)
  • 10.2.5.3 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 The accessible name of every user interface component that includes a visible text label corresponds to that label text.

2.5.4 Motion Actuation

(Level A 2.1 and 2.2)

 Not Applicable The application includes no functionality operated by device motion or user motion.

3.1.1 Language of Page

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.3.1.1 (Web)
  • 10.3.1.1 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 The default language of the application’s screens, web views and PDF documents is properly identified.

3.2.1 On Focus

(Level A)

 Not Applicable The application’s components do not initiate a change of context when focused.

3.2.2 On Input

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.3.2.2 (Web)
  • 10.3.2.2 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 The application initiates no change of context upon user input.

3.2.6 Consistent Help

(Level A 2.2 only)

 Android (web views): Supports
iOS (web views): Supports		 Every help mechanism (contact details, FAQ, suggestions) is presented and reachable the same way across the screens.

3.3.1 Error Identification

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.3.3.1 (Web)
  • 10.3.3.1 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 Where errors are automatically detected, the error is identified, and an error message is provided as text.

3.3.2 Labels or Instructions

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.3.3.2 (Web)
  • 10.3.3.2 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Partially supports

Most of the application’s input fields have an explicit label. Relevant instruction is given about mandatory fields and expected formats.

Exceptions include:

  • The identification of required fields by an asterisk is not always preceded by a visible definition.

3.3.7 Redundant Entry

(Level A 2.2 only)

 Not Applicable The application does not require the user to enter the same data twice inside the same process.

4.1.1 Parsing

(Level A)

Applies to WCAG 2.0 and 2.1
Always answer ‘Supports’

WCAG 2.2 (obsolete and removed) - Does not apply

EN 301 549 Criteria:

  • 9.4.1.1 (Web)
  • 10.4.1.1 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

For WCAG 2.0, 2.1 and EN 301 549, the September 2023 errata update indicates this criterion is always supported.

See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata.

4.1.2 Name, Role, Value

(Level A)

Also applies to EN 301 549 Criteria:

  • 9.4.1.2 (Web)
  • 10.4.1.2 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Partially supports

Most user interface components in the application provide programmatic name, role, and/or state information.

Exceptions include:

  • Some buttons do not expose their role explicitly to assistive technologies, but a hint is provided by the OS.
  • Modal dialogs have no accessible name
  • Closing buttons in modal dialogs and notification bars are inconsistently named across the application.
  • The label and field of toggle controls are associated visually but not programmatically.
  • Dropdown lists are exposed as buttons but do not expose their collapsible property or state.
  • Throughout the account creation process, the status of the different steps is not exposed..
  • Inside the Personal Information form, the Gender combobox is not controllable when using a mobile screen reader.

Until this exception is fixed, users are invited to modify their data in the web application.

Table 2: Success Criteria, Level AA

Criteria Conformance Level Remarks and Explanations

1.2.4 Captions (Live)

(Level AA)

Also applies to EN 301 549 Criteria:

  • 9.1.2.4 (Web)
  • 10.1.2.4 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)
 Not Applicable The application includes no live synchronized media.

1.2.5 Audio Description (Prerecorded)

(Level AA)

Also applies to EN 301 549 Criteria:

  • 9.1.2.5 (Web)
  • 10.1.2.5 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)
 Not Applicable The application includes no prerecorded video content that requires audio description.

1.3.4 Orientation

(Level AA 2.1 and 2.2)

Also applies to EN 301 549 Criteria:

  • 9.1.3.4 (Web)
  • 10.1.3.4 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Does not support

iOS: Does not support

On Android, the application can be consulted in both screen orientations.

The content of the application can be consulted only in portrait mode.

1.3.5 Identify Input Purpose

(Level AA 2.1 and 2.2)

Also applies to EN 301 549 Criteria:

  • 9.1.3.5 (Web)
  • 10.1.3.5 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 The application includes no input field that requires the user to enter personally identifiable information.

1.4.3 Contrast (Minimum)

(Level AA)

Also applies to EN 301 549 Criteria:

  • 9.1.4.3 (Web)
  • 10.1.4.3 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Partially supports

Most text in the application meets minimum contrast requirements.

Exceptions include inside hosted PDF documents:

  • blue links over a white background (1,9:1)
  • blue headings over a white background (1,9:1)
  • white table headers over a blue background (1,9:1)

1.4.4 Resize text

(Level AA)

Also applies to EN 301 549 Criteria:

  • 9.1.4.4 (Web)
  • 10.1.4.4 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 The application’s content and user interfaces support standard zoom capabilities built into modern web browsers and operating systems (tested with a 200% zoom).

1.4.5 Images of Text

(Level AA)

 Not Applicable The application uses text instead of images of text.

1.4.10 Reflow

(Level AA 2.1 and 2.2)

Also applies to EN 301 549 Criteria:

  • 9.1.4.10 (Web)
  • 10.1.4.10 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 The content of the application can be consulted without horizontal scrolling when the viewport is 320-pixels wide.

1.4.11 Non-text Contrast

(Level AA 2.1 and 2.2)

Also applies to EN 301 549 Criteria:

  • 9.1.4.11 (Web)
  • 10.1.4.11 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 Every meaningful non-text content in the application has sufficient contrast.

1.4.12 Text Spacing

(Level AA 2.1 and 2.2)

Also applies to EN 301 549 Criteria:

  • 9.1.4.12 (Web)
  • 10.1.4.12 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Partially supports

On most of the application’s web views, the spacing between letters, words, lines of text and/or paragraphs can be adjusted.

Exceptions include:

  • Part of the merchant address is hidden inside the merchant listing when the text spacing is increased. The complete address is retrievable by going to the Merchant details.

1.4.13 Content on Hover or Focus

(Level AA 2.1 and 2.2)

Also applies to EN 301 549 Criteria:

  • 9.1.4.13 (Web)
  • 10.1.4.13 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 The application includes no content element triggered by hover or focus.

2.4.5 Multiple Ways

(Level AA)

Also applies to EN 301 549 Criteria:

  • 9.2.4.5 (Web)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)
 Not Applicable There is no set of pages in the application which requires multiple ways of navigation.

2.4.6 Headings and Labels

(Level AA)

Also applies to EN 301 549 Criteria:

  • 9.2.4.6 (Web)
  • 10.2.4.6 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Partially supports

All the labels inside the application are structured and descriptive. The same for most headings.

Exceptions include:

  • A few headings are descriptive, but they do not expose their role to assistive technologies

2.4.7 Focus Visible

(Level AA)

Also applies to EN 301 549 Criteria:

  • 9.2.4.7 (Web)
  • 10.2.4.7 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Supports

On iOS, all the focusable elements in the application have a visible keyboard focus indicator.

On Android, exceptions include:

  • Carrousel cards in the application dashboard
  • FAQ expandable buttons

External tools (such as Switch Access on Android) may help by applying an outline to focused elements.

2.4.11 Focus Not Obscured (Minimum)

(Level AA 2.2 only)

Android: Supports

iOS: Supports

 The application’s components are not entirely hidden when they are focused.

2.5.7 Dragging Movements

(Level AA 2.2 only)

Android: Supports

iOS: Supports

 The application provides a single-pointer alternative when a functionality uses a dragging movement.

2.5.8 Target Size (Minimum)

(Level AA 2.2 only)

Android: Supports

iOS: Supports

 The size of every target for pointer inputs in the application (buttons, links, etc.) is 24 by 24 CSS pixels or more.

3.1.2 Language of Parts

(Level AA)

Also applies to EN 301 549 Criteria:

  • 9.3.1.2 (Web)
  • 10.3.1.2 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Partially supports

For most texts inside web views or PDF documents, the language can be programmatically determined.

Exceptions include:

  • Some accessible names are not translated from English to the current language setting.

3.2.3 Consistent Navigation

(Level AA)

Also applies to EN 301 549 Criteria:

  • 9.3.2.3 (Web)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 The application provides consistent and repeatable navigation.

3.2.4 Consistent Identification

(Level AA)

Also applies to EN 301 549 Criteria:

  • 9.3.2.4 (Web)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

 Components that have the same functionality within the application are identified consistently.

3.3.3 Error Suggestion

(Level AA)

Also applies to EN 301 549 Criteria:

  • 9.3.3.3 (Web)
  • 10.3.3.3 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Partially supports

In most cases, when an error is detected inside a form and additional guidance is needed, the error message provides suggestions.

Exceptions include:

  • There is no suggestion when an invalid e-mail is entered.

3.3.4 Error Prevention (Legal, Financial, Data)

(Level AA)

Also applies to EN 301 549 Criteria:

  • 9.3.3.4 (Web)
  • 10.3.3.4 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Supports

iOS: Supports

When the user modifies or deletes their stored data and this action relates to legal commitment or financial transactions:

  • Either the submission is reversible;
  • Or the entered data is checked for errors, and the user is provided with an opportunity to correct them;
  • Or a mechanism is available for reviewing, confirming, andcorrecting information before finalizing the submission.

3.3.8 Accessible Authentication (Minimum)

(Level AA 2.2 only)

Android: Supports

iOS: Supports

 The application offers an accessible, non-cognitive alternative (biometrical authentication).

4.1.3 Status Messages

(Level AA 2.1 and 2.2)

Also applies to EN 301 549 Criteria:

  • 9.4.1.3 (Web)
  • 10.4.1.3 (non-web document)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Android: Partially supports

iOS: Partially supports

In most situations, notifications (success, warning or error notifications are presented to the user by assistive technologies).

Exceptions include:

  • Searching inside Transaction History generates asynchronous search results which are not exposed immediately to assistive technologies.
  • Error messages in forms are not exposed immediately to assistive technologies.

In both case, users need to leave the search field and navigate of the result area placed right after in the sequence.

Table 3: Success Criteria, Level AAA

Notes: Not evaluated

EN 301 549 Report

Clause 4: Functional Performance Statements (FPS)

Criteria Conformance Level Remarks and Explanations
4.2.1 Usage without vision

Android: Partially supports

iOS: Partially supports

Most functions of the application are usable without vision.

Exceptions are noted in:

  • WCAG Level A 1.1.1 Non-Text content
  • WCAG Level A 1.3.1 Info and Relationships
  • WCAG Level A 1.3.2 Meaningful sequence
  • WCAG Level A 2.2.1 Timing Adjustable
  • WCAG Level A 2.4.2 Page titled
  • WCAG Level A 2.4.4 Link Purpose (in Context)
  • WCAG Level A 2.4.6 Headings and Labels
  • WCAG Level A 2.5.3 Label in name
  • WCAG Level A 3.1.1 Language of Page
  • WCAG Level AA 3.1.2 Language of Parts
  • WCAG Level A 3.3.2 Labels or Instructions
  • WCAG Level A 4.1.2 Name, Role, Value
  • WCAG Level AA 4.1.3 Status messages
4.2.2 Usage with limited vision

Android: Partially supports

iOS: Partially supports

Most functions of the application are usable with limited vision.

Exceptions are noted in:

  • WCAG Level AA 1.4.3 Contrast (minimum)
  • WCAG Level AA 1.4.12 Text Spacing
  • WCAG Level A 2.2.1 Timing Adjustable
  • WCAG Level AA 2.4.7 Focus Visibility
4.2.3 Usage without perception of color

Android: Supports

iOS: Supports

 All the functions of the application are usable without perception of color.
4.2.4 Usage without hearing.

Android: Supports

iOS: Supports

 The application does not rely on hearing ability to operate any of the contents.
4.2.5 Usage with limited hearing.

Android: Supports

iOS: Supports

 The application does not rely on hearing ability to operate any of the contents.
4.2.6 Usage with no or limited vocal capability.

Android: Supports

iOS: Supports

 The application includes no content that requires vocal ability to operate.
4.2.7 Usage with limited manipulation or strength.

Android: Partially supports

iOS: Partially supports

The application supports standard input modalities so that users with limited motor controls can operate the content.

Exceptions are noted in:

  • WCAG Level AA 1.3.4 Orientation
  • WCAG Level A 2.1.1 Keyboard
  • WCAG Level A 2.2.1 Timing Adjustable
  • WCAG Level A 2.4.3 Focus order
4.2.8 Usage with limited reach

Android: Supports

iOS: Supports

 The application is not a hardware device that requires reachability.
4.2.9 Minimize photosensitive seizure triggers

Android: Supports

iOS: Supports

 The application includes no content that flashes.
4.2.10 Usage with limited cognition, language or learning

Android: Partially supports

iOS: Partially supports

In most cases, the application provides consistent navigation, descriptive headings, and labels, and page and part level language or programmatic language support.

Exceptions are noted in:

  • WCAG Level A 1.1.1 Non-Text content
  • WCAG Level A 2.2.1 Timing Adjustable
  • WCAG Level A 1.3.1 Info and Relationships
  • WCAG Level A 1.3.2 Meaningful sequence
  • WCAG Level A 2.4.2 Page titled
  • WCAG Level A 2.4.4 Link Purpose (in Context)
  • WCAG Level A 2.4.6 Headings and Labels
  • WCAG Level AA 3.1.2 Language of Parts
  • WCAG Level AA 3.3.2 Labels and Instructions
  • WCAG Level A 3.3.3 Error suggestion
4.2.11 Privacy

Android: Supports

iOS: Supports

 The application is compatible with all the privacy options including the use of headphones while using assistive technology.

Clause 5: Generic Requirements

Criteria Conformance Level Remarks and Explanations
5.1 Closed functionality Not Applicable The application includes no closed functionality.
5.2 Activation of accessibility features Not Applicable The application includes no accessibility feature.
5.3 Biometrics

Android: Supports

iOS: Supports

 A user can authenticate with their fingerprint or by entering pre-fillable email and password.
5.4 Preservation of accessibility information during conversion Not Applicable The application includes no conversion feature.
5.5 Operable parts Not Applicable The application includes no actionable part.
5.6 Locking or toggle controls Heading cell – no response required Heading cell – no response required
5.6.1 Tactile or auditory status

Android: Supports

iOS: Supports

 The status of every toggle control can be determined without operating the control.
5.6.2 Visual status

Android: Supports

iOS: Supports

 the status of every toggle control can be visually determined.
5.7 Key repeat Not Applicable The application includes no key repeat function.
5.8 Double-strike key acceptance Not Applicable The application includes no keyboard or keypad.
5.9 Simultaneous user actions Not Applicable The application does not require simultaneous actions.

Clause 6: ICT with Two-Way Voice Communication

Notes: This clause is Not Applicable

Clause 7: ICT with Video Capabilities

Notes: This clause is Not Applicable

Clause 8: Hardware

Notes: This clause is Not Applicable

Clause 9: Web

Notes: See WCAG 2.x section

Clause 10: Non-Web Documents

Notes: This clause applies to PDF documents consultable and downloadable in the Account section.

Criteria Conformance Level Remarks and Explanations
10.0 General (informative) Heading cell – no response required Heading cell – no response required
10.1.1.1 through 
10.4.1.3
See information in WCAG 2.x section

See information in WCAG 2.x section

 
10.5 Caption positioning Not Applicable The application includes no synchronized multimedia content.
10.6 Audio description timing Not Applicable The application includes no synchronized multimedia content.

Clause 11: Software

Criteria Conformance Level Remarks and Explanations
11.0 General (informative) Heading cell – no response required Heading cell – no response required
11.1.1.1 through 
11.4.1.3		 See information in WCAG 2.x section See information in WCAG 2.x section
11.5 Interoperability with assistive technology Heading cell – no response required Heading cell – no response required
11.5.1 Closed functionality Not Applicable The application includes no closed functionality.
11.5.2 Accessibility services Heading cell – no response required Heading cell – no response required
11.5.2.1 Platform accessibility service support for software that provides a user interface Not Applicable The application is not a platform software.
11.5.2.2 Platform accessibility service support for assistive technologies Not Applicable The application is not a platform software.
11.5.2.3 Use of accessibility services See information in 11.5.2.5 through 11.5.2.17 See information in 11.5.2.5 through 11.5.2.17
11.5.2.4 Assistive technology Not Applicable The application is not an assistive technology.
11.5.2.5 Object information

Android: Partially supports

iOS: Partially supports

The application provides information to assistive technologies.

See details and exceptions in:

  • WCAG Level A 1.3.1 Info and Relationships
  • WCAG Level A 2.4.4 Link Purpose (in Context)
  • WCAG Level A 2.4.6 Headings and Labels
  • WCAG Level A 2.5.3 Label in name
  • WCAG Level A 3.3.2 Labels or Instructions
  • WCAG Level A 4.1.2 Name, Role, Value
11.5.2.6 Row, column, and headers Not Applicable The application contains no table.
11.5.2.7 Values Not Applicable The application does not convey information about a range of values.

 

Android: Partially supports

iOS: Partially supports

The application associates form labels and fields.

See details and exceptions in:

  • WCAG Level A 1.3.1 Info and Relationships
  • WCAG Level A 2.5.3 Label in name
  • WCAG Level A 3.3.2 Labels or Instructions
  • WCAG Level A 4.1.2 Name, Role, Value
11.5.2.9 Parent-child relationships

Android: Partially supports

iOS: Partially supports

The application provides hierarchical structure between elements.

See details and exceptions in:

  • WCAG Level A 2.4.4 Link Purpose (in Context)
  • WCAG Level A 2.5.3 Label in name
  • WCAG Level A 4.1.2 Name, Role, Value
11.5.2.10 Text

Android: Partially supports

iOS: Partially supports

 The application contains non-textual information and text elements.

See details and exceptions in:

  • WCAG Level A 1.1.1 Non-Text content
  • WCAG Level A 1.3.1 Info and Relationships
  • WCAG Level A 1.3.2 Meaningful Sequence
11.5.2.11 List of available actions

Android: Partially supports

iOS: Partially supports

The application includes components that have user-operable actions.

See details and exceptions in:

  • WCAG Level A 2.4.4 Link Purpose (in Context)
  • WCAG Level A 2.5.3 Label in name
  • WCAG Level A 4.1.2 Name, Role, Value
11.5.2.12 Execution of available actions

Android: Partially supports

iOS: Partially supports

The application allows the user to execute programmatically determinable actions.

See details and exceptions in:

  • WCAG Level A 1.3.1 Info and Relationships
  • WCAG Level A 2.1.1 Keyboard
  • WCAG Level A 2.4.4 Link Purpose (in Context)
  • WCAG Level AA 2.4.7 Focus Visibility
  • WCAG Level A 2.5.3 Label in name
  • WCAG Level A 4.1.2 Name, Role, Value
11.5.2.13 Tracking of focus and selection attributes

Android: Partially supports

iOS: Partially supports

The application contains elements that can receive focus.

See details and exceptions in:

  • WCAG Level A 1.3.1 Info and Relationships
  • WCAG Level A 2.1.1 Keyboard
  • WCAG Level AA 2.4.7 Focus Visibility
11.5.2.14 Modification of focus and selection attributes

Android: Partially supports

iOS: Partially supports

The application allows changes to the focus and selection state of elements.

See details and exceptions in:

  • WCAG Level A 1.3.1 Info and Relationships
  • WCAG Level A 2.1.1 Keyboard
  • WCAG Level AA 2.4.7 Focus Visibility
11.5.2.15 Change notification

Android: Partially supports

iOS: Partially supports

The application exposes change notifications to assistive technologies.

See details and exceptions in:

  • WCAG Level AA 4.1.3 Status messages
11.5.2.16 Modifications of states and properties

Android: Partially supports

iOS: Partially supports

The application exposes state and property changes to assistive technologies.

See details and exceptions in:

  • WCAG Level A 2.4.4 Link Purpose (in Context)
  • WCAG Level A 2.5.3 Label in name
  • WCAG Level A 4.1.2 Name, Role, Value
11.5.2.17 Modifications of values and text

Android: Partially supports

iOS: Partially supports

The application exposes value and text changes to assistive technologies.

See details and exceptions in:

  • WCAG Level A 1.3.1 Info and Relationships
  • WCAG Level A 2.1.1 Keyboard
  • WCAG Level AA 2.4.7 Focus Visibility
  • WCAG Level A 4.1.2 Name, Role, Value
11.6 Documented accessibility usage Heading cell – no response required Heading cell – no response required
11.6.1 User control of accessibility features Not Applicable The application is not platform software.
11.6.2 No disruption of accessibility features

Android: Partially supports

iOS: Partially supports

The application does not prevent or disrupt any accessibility features or the use of assistive technology.

See details and exceptions in:

  • WCAG Level A 1.3.1 Info and Relationships
  • WCAG Level A 4.1.2 Name, Role, Value
11.7 User preferences

Android: Partially supports

iOS: Partially supports

The application does not interfere with the user preferences.

See details and exceptions in:

  • WCAG Level A 1.3.1 Info and Relationships
  • WCAG Level A 4.1.2 Name, Role, Value
11.8 Authoring tools Not Applicable The application is not an authoring tool.

Clause 12: Documentation and Support Services

Criteria Conformance Level Remarks and Explanations
12.1 Product documentation Heading cell – no response required Heading cell – no response required
12.1.1 Accessibility and compatibility features

Android: Partially supports

iOS: Partially supports

The Account section of the application includes a Help center (FAQ) plus an Accessibility sub-section.

See details and exceptions in:

  • WCAG Level A 1.3.1 Info and Relationships
  • WCAG Level A 4.1.2 Non-Text Content
12.1.2 Accessible documentation See WCAG 2.x section See information in WCAG 2.x section
12.2 Support Services Heading cell – no response required Heading cell – no response required
12.2.2 Information on accessibility and compatibility features

Android: Supports

iOS: Supports

 The Accessibility section includes information about WCAG compliance, with a link to the present report.
12.2.3 Effective communication See WCAG 2.x section See information in WCAG 2.x section
12.2.4 Accessible documentation See WCAG 2.x section See information in WCAG 2.x section

Clause 13: ICT Providing Relay or Emergency Service Access

Notes: This clause is Not Applicable