Login

Accessibility statement

Aimo Sweden AB strives to make our digital services accessible in accordance with the Act on Accessibility to Digital Public Services (2018:1937) and the European Accessibility Act (EU Directive 2019/882).

This statement concerns Aimo App, a React Native mobile app,  version 1.28.1, published on July 2025.  
 

This mobile application is run by Aimo. We want as many people as possible to be able to use it, and this document describes how Aimo App complies with the accessibility regulations, any known accessibility issues, and how you can report problems so that we can fix them. 

 

How accessible is the Aimo mobile application?

We are aware that some parts of our mobile application are not fully accessible. See the section on non-accessible content below for more information. 

 

What can you do if you cannot use parts of this mobile application?

If you need content from this mobile application that is not accessible for you, but is not within the scope of the accessibility regulations as described below, please contact us:     

   E-mail: digitalaprodukter@aimopark.se

   Phone: 0771-96 90 00

We try to respond within a reasonable time, normally within 10 working days.


Report accessibility issues 

We appreciate your feedback on our accessibility. We’re always looking to improve the accessibility of this mobile application. If you notice any issues that are not described in this statement, or if you believe we are not complying with legal requirements, please let us know so we can address them.

   Contact us via: digitalaprodukter@aimopark.se

 

Enforcement procedure

The Swedish Digital Governance Agency (DIGG) is responsible for enforcing the web accessibility regulations. If you are not satisfied with how we handle your comments, you can contact DIGG:

  Website: https://www.digg.se

  E-mail: tillganglighet@digg.se  

  Phone: 0771-11 44 00 

 

You can also submit a complaint to Digg if you think that our assessment of what constitutes a disproportionate burden should be reviewed, if you think that our accessibility statement is inadequate, or it you think that your request for excluded content in an accessible format has not been handled correctly.

 

Technical information about Aimo mobile application’s accessibility

We have conducted an internal review using WCAG 2.1 level AA as a reference. Our assessment is that this mobile application is partially compliant with the Swedish accessibility regulations, due to the non-compliances listed below.

Non-accessible content 

The content described below is, in one way or another, not fully accessible. 

Non-compliance with the accessibility regulations 

Bottom sheet behavior when VoiceOver is enabled (iOS) 
When using screen reader (VoiceOver) on iOS, the position of the bottom sheet cannot be adjusted using swipe gestures. 
This is due to a limitation in a third-party component we use: 

This issue impacts dynamic interaction and navigation for screen reader users in certain components. 


How we tested this mobile application

We have performed a self-assessment (internal testing) of Aimo App. 

The last assessment was made on June 24, 2025. 

The accessibility testing included manual testing using screen readers, automated testing, and third-party tools. Our testing process is summarized below: 

 

Manual Screen Reader Testing 

Android – TalkBack 

TalkBack is Android’s built-in screen reader that provides spoken feedback. It was used to evaluate navigation, focus order, and interaction across key workflows. 

Test scope and steps included: 

  • Spoken feedback: Verified that each element was announced clearly and accurately. 
  • Notification announcements: Checked if dynamic alerts (e.g., ANPR notifications) are read aloud. 
  • Navigation methods: 
    • Swipe Navigation: Swiped right/left to move linearly through elements. 
    • Explore by touch: Dragged finger across the screen to detect content. 
  • Test Cases: 
    • Parking flow 
    • Bottom sheet interactions 
    • Profile and settings screens 
  • Focus check: Ensured all interactive elements are reachable and logically ordered. 
  • Video recordings: Captured representative test sessions for documentation and training. 



iOS – VoiceOver 

VoiceOver was used to assess accessibility behavior on iOS, ensuring full screen reader compatibility. 

Test scope and steps included: 

  • Enabling VoiceOver: Activated via Settings, Siri, and Accessibility Shortcut. 
  • VoiceOver gestures used: 
    • Swipe right/left – Navigate between elements 
    • Double-tap – Activate focused element 
    • Three-finger swipe – Scroll 
    • Two-finger swipe down – Read from top 
  • Accessibility focus order: Verified logical and expected element order. The order is followed by the DOM order. 
  • Labels & traits: Ensured all elements had descriptive labels and correct accessibility roles (e.g., buttons, headers). 
  • Common checks: 
    • No duplicate reads (e.g., nested Views and Text) 
    • Custom controls (e.g., sliders, bottom sheets) announced correctly 
    • Dynamic updates (e.g., parking alerts, errors) are read out 
  • Test Cases: 
    • Parking flow 
    • Bottom sheet gesture restrictions (known issue) 
    • ANPR and user profile flows 

 

Tool-Based Testing 

We used a mix of automated tools and platforms for broader coverage: 

  • Playwright: Automated end-to-end tests including accessibility assertions and color contrast using axe-core. 
  • axe DevTools (Paid tool): Used in web views or React Native debug sessions to flag common WCAG violations. 
  • BrowserStack (Paid tool): Device cloud testing on various Android/iOS versions to confirm consistent accessibility support. 
  • Lighthouse: Used to run accessibility audits on embedded webviews and React Native debug sessions (via Chrome DevTools). 


Date of the accessibility statement 
This statement was last updated on: 1st July 2025