Mobile accessibility statement

We are working towards as many people as possible being able to use our mobile application (app). This means you should be able to use your device settings to:

  • change display options like dark mode, bold text, reduce transparency and increase contrast
  • apply the maximum text size and display zoom without content clipping or overlapping
  • use the app features with a keyboard or speech recognition software
  • access the app content and features using a screen reader

We’ve also tried to make the app text easy to understand.

Making our app accessible is an ongoing project. Our first priority is to make sure accessibility options configured in your device settings are supported. User feedback can help us understand if accessibility options configured in our app are also needed.

Our commitment to mobile accessibility

Digital accessibility means developing interfaces and features that are easy for everyone to use, no matter what their abilities - visual, hearing, motor or cognitive.

This means we:

  • use the Web Content Accessibility Guidelines (WCAG) v2.2 level AA and other international standards such as EN 301 549, as they apply to mobile accessibility
  • use guidance from the World Wide Web Consortium (W3C) to inform our standards
  • do our best to make sure that vendors developing or designing for us also comply with accessibility standards and requirements
  • respond positively when customers let us know something isn’t accessible and work to fix it.

Web Content Accessibility Guidelines (WCAG) 2.2 (external link)
W3C’s Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile(external link)
EN 301 549(external link)
Website accessibility statement

Known issues

We test our app to discover where we can improve. We know some parts are not fully accessible. Sometimes the platform (iOS or Android), service or technology we’re using to build the app may also have issues.

Some issues are resolved by using the latest version of iOS or Android. Issues that only happen on older versions of iOS or Android are not listed here.

This is not a full list. It only covers high impact issues or things we cannot fix.

Both platforms (iOS and Android)

  • RealMe login NZ Transport Agency Waka Kotahi logo needs alternative text label.
  • Focus order for screen readers and keyboard only users could be improved.
  • PIN screen provides no way to view the digits already entered.
  • ‘Pull to refresh’ reloading of whole screen data relies on gesture to trigger.

iOS

  • Elements that are not interactive get keyboard focus, so that all scrollable content can be accessed. This means non-interactive elements are also being identified by Voice Control.
  • Screen content native tab controls do not meet contrast requirements.
  • Unable to reorder vehicles using assistive technologies.

Android

  • Voice Access can’t trigger links and checkboxes separately saying on screen text, only using ‘show numbers’. Screen readers can access the links using Actions.
  • Keyboard focus is difficult to see. Focus styling is determined by the system user interface.
  • There is no visible keyboard focus for the Licence screen expand/collapse control, or info button on some Vehicle alerts. Although they are focusable and can be used.
  • When TalkBack reaches the bottom of the Classes tab content, it automatically changes context to select the Endorsements tab, instead of the bottom app navigation.
  • App activity timeout is not refreshed when TalkBack is just reading content.
  • Pull to refresh has no screen reading feedback.
  • Voice Access cannot delete vehicles using numbers, must use grid method instead.

Not yet assessed

  • Switch control/access

How we tested this app

Our app is tested in-house using manual testing methods. We can’t test all devices and operating system combinations, so our focus has been to cover one high-end and one low-end phone for both Apple and Android:

  • iPhone without physical Home button, running latest iOS release.
  • iPhone SE (2020) with physical Home button, running latest iOS 16 version.
  • Other brand phone (Oppo), running latest Android release.
  • Samsung phone, running Android 11.

Assistive technologies used

Both platforms (iOS and Android)

  • Device accessibility settings options
  • Bluetooth keyboard.

iOS

  • VoiceOver screen reader
  • Voice Control.

Android

  • TalkBack screen reader
  • Voice Access.

What to do if you can't access parts of this app

Email us if you have any accessibility feedback for us, need support accessing content, or want to request content in an alternate accessible format.

Email: accessibility@nzta.govt.nz

Contacting us by phone

We recommend a text relay service if you want to call us and are D/deaf, Deafblind, hard of hearing or have a speech impediment.

NZ Relay service(external link)

Last Updated: 27 November 2024