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 made the app text as easy as possible to understand.

Our commitment to mobile accessibility

Our digital accessibility journey started with a focus on website accessibility and continues with an approach that considers mobile apps. Digital accessibility means developing interfaces and features that are easy for everyone to use, no matter what their abilities – visual, hearing, motor or cognitive.

Website accessibility statement

This means we:

  • work to make sure our app is in line with the Web Content Accessibility Guidelines (WCAG) v2.1 level AA (where they apply to mobile devices) and other international standards such as EN 301 549 (as updated from time to time)
  • use guidance from the World Wide Web Consortium (W3C) to inform our standards
  • respond positively when customers let us know something isn’t accessible and work to fix it.

Web Content Accessibility Guidelines (WCAG) 2.1(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)

Known issues

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

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

Known feature limitations

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

  • Keyboard and Voice Access cannot trigger Terms or Privacy checkboxes, instead the links are activated.
  • Keyboard focus is difficult to see. Focus styling is determined by the system user interface.
  • There is no visible keyboard focus for the Licence sheet expand/collapse control, although it is focusable and can be used.
  • Vehicle alert details with no interactive action are being announced as ‘disabled’ elements.
  • 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.
  • Unable to reorder vehicles using keyboard or Voice Access. Can use TalkBack actions.

Accessibility requirements still to be assessed

  • Switch control/access

What we’re doing to improve accessibility

Making our app accessible is an ongoing project. We continue to dedicate ourselves to doing what we can to make our information accessible to all, so that everyone can benefit from our services.

Improving accessibility over time

We consider accessibility for new features, as well as fixing existing access barriers as we find them. We’re developing mobile accessibility standards based on the current features of the app.

Our initial approach has been to make sure accessibility options configured in device settings are supported. User feedback will help us understand if accessibility options configured in our app are also required.

What we’ve already done

While assessing the app we found things to work on and made improvements:

  • Content supports text resizing and display zoom combinations. Content should still be able to be read, scrolled and used at different sizes
  • Content can be accessed and understood with VoiceOver or TalkBack screen reading
  • Meaningful images have accessible names
  • Words, icons and buttons are visible against their backgrounds
  • Error messages and help text make it easier for people filling in forms
  • Critical status messages are persistent pop-ups. Non-critical feedback disappears automatically.  

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: 12 September 2024