Accessibility statement

Version 2 · In force from 2026-11-16

This is a translation. If the translation differs from the Dutch text, the Dutch text prevails.

GoSwift wants to be usable for everyone, including people with a disability. For the website, the web version and the apps we aim for the European standard for digital accessibility: WCAG 2.1 level AA.

1. Current status

1.1 Website, checked on 11 November 2026. This is what we did:

  • An automatic check with axe-core 4.11.0 (the rules of WCAG 2.0, 2.1 and 2.2 level A and AA and the best-practice rules) on every page in Dutch and English, at a screen width of 1280, 640, 375 and 320 pixels. Result: no violation found. A few elements the tool could not judge by itself (text in the illustration, table cells out of view, the message field); for those we rely on the website's own colour-contrast tests.
  • Zoom and text spacing: at 200 % zoom (640 pixels wide) and 400 % zoom (320 pixels wide) every page fits without sideways scrolling, except the tables, which scroll on their own and can be reached with the keyboard. With the text spacing of WCAG 1.4.12 (line height 1.5, letter spacing 0.12 em, word spacing 0.16 em) no text is cut off anywhere.
  • The keyboard, by hand: the link to skip to the content, the order of the tab key, the visible focus outline (at least 3 to 1 contrast with the background, also on the green areas), the menu on a narrow screen, the frequently asked questions, the language switch and the contact form.
  • Every time the website changes, automatic tests run on, among other things, colour contrast (at least 4.5 to 1 for text), the size of buttons and fields (at least 48 pixels), the heading structure, the language attribute, the labels of form fields and the alternative text of images.

1.2 What we have not done: the website has not been tested with a screen reader (such as NVDA, VoiceOver or TalkBack) or on a range of real devices, and there has been no independent audit.

1.3 Staff environment (the management screen at /beheer), checked on 11 November 2026. Our staff use this screen; it falls under the same standard. This is what we did and improved:

  • Colour: all text colour pairs reach at least 4.5 to 1 and the borders of input fields and switches at least 3 to 1. The red button for irreversible actions and the main button under the mouse pointer were too weak and have been changed.
  • Keyboard: the focus outline stays visible in input fields, the menu on a narrow screen cannot be reached with the tab key while it is closed, tables that scroll sideways and the map can be operated with the keyboard (arrow keys), and tabs work with the arrow keys.
  • Pages: when the page changes, the tab title follows the page heading and the new page is announced, every page has one main heading, and an error or warning message no longer disappears by itself.
  • Automatic tests run on every change: axe-core 4.11.0 on every page and the colour contrast of all colour pairs.
  • What we have not done yet: a check with axe-core in a real browser on the pages after signing in at 1280, 640, 375 and 320 pixels, and a test with a screen reader.

1.4 Web version and apps: we build them to the same rules and test them with a keyboard and a screen reader. This is a self-assessment. No independent audit has been done yet; once there is one, we will state the result here.

1.5 So we have not been fully assessed yet. What we know can still be better is listed below.

2. What can still be better

  • The map in the web version and the apps is visual. You can always type an address and choose from a list without using the map.
  • Voice messages in the ride chat have no text captions yet.
  • PDF attachments such as a transport receipt have not all been checked for accessibility yet.
  • The error message of the contact form comes from your browser (in your browser's language); we have not tested it with assistive software.
  • On the website itself we know of no open findings from the check above, but an automatic check does not find everything. If you notice something, please tell us.

3. Wheelchairs and other needs for the ride

3.1 You request a vehicle for a wheelchair through Support (+32 499 07 03 32), day and night; read spacious and wheelchair taxi. An assistance dog is always welcome and a driver may never refuse a ride because of a disability.

4. Reporting a problem

4.1 Did you run into an accessibility problem, or do you need another format (for example a text in large print)? Report it through the contact form, by e-mail at [email protected] or by phone at +32 499 07 03 32. We reply within 14 days and look for a solution.

4.2 If you are not satisfied with our answer, you can report this to the contact point of the Federal Public Service Economy (meldpunt.belgie.be).

5. About this statement

5.1 This statement was drawn up by GoSwift. It is reviewed at every important change and at least once a year.