Accessibility statement

 

Services2cities strives to make its digital applications as accessible as possible. We do this in accordance with the European directive and the Flemish administrative decree.

 

Everyone must be able to use and view the information on www.velo-antwerpen.be easily, including visually impaired, blind, hearing impaired, deaf people and people with a different disability. This accessibility statement indicates the extent to which this website meets the proposed guidelines.

 

The guidelines that are followed are the Web Content Accessibility Guidelines version 2.1 or simply WCAG 2.1. EThere are three levels of accessibility: from low to high A, AA and AAA. This application complies with the guidelines up to and including level AA, apart from the following work points.

 

Open work points

The content below is not accessible due to a disproportionate burden. For this we rely temporarily on article 5 of the European directive 2016/2102. We are committed to resolving the outstanding issues within a reasonable time.

 

1.3.1 Info and Relationships (Level A)

  • Work point

    Some lists do not contain only <li> elements and script supporting elements (<script> and <template>).

  • Effect for the user

    Screen readers and other assistive technologies cannot inform the listener that they are listening to items within the list.

  • Plan of action

    Ensure all ordered and unordered lists (defined by <ul> or <ol> elements) contain only <li> content elements.

  • Schedule

    Pending to be scheduled according to effort estimation.

 

1.3.1 Info and Relationships (Level A)

  • Work point

    List items (<li>) are not contained within <ul> or <ol> parent elements.

  • Effect for the user

    Screen readers and other assistive technologies require list items <li> to be contained within parent <ul> or <ol> to be announced properly.

  • Plan of action

    Ensures <li> elements are used semantically.

  • Schedule

    Pending to be scheduled according to effort estimation.

 

2.1.2 No Keyboard Trap (Level A)

  • Work point

    All the interactive controls of the page are not reachable. This point must be solved in order to provide a smooth keyboard navigation experience.

  • Effect for the user

    Users cannot rely on the keyboard to navigate the whole website, nor using keyboard shortcuts to be more efficient and productive.

  • Plan of action

    Replace custom controls with native HTML alternatives.

    Use tabindex attribute to ensure interactive controls are keyboard accesible.

  • Schedule

    Pending to be scheduled according to effort estimation.

 

2.4.4 Link Purpose (In Context) (Level A)

  • Work point

    Some links do not have a discernible name. This must be solved in order to improve the navigation experience for screen reader users.

  • Effect for the user

    Users who rely exclusively on a keyboard (and no mouse) to navigate a webpage can only click on links that can receive programmatic focus. A link that cannot receive programmatic focus is inaccessible to these users.

  • Plan of action

    Zorg ervoor dat alle koppelingstekst zichtbaar is en programmatische focus kan ontvangen.

  • Schedule

    Pending to be scheduled according to effort estimation.

 

3.3.2 Labels or instructions (Level A)

  • Work point

    Form elements do not have associated labels.

  • Effect for the user

    Navigating through frames and inline frames can quickly become difficult and confusing for assistive technology users if the frames are not marked with a title attribute.

  • Plan of action

    Add the corresponding label on the following elements, when missing:

    • Text entry fields.

    • Radio buttons.

    • Checkboxes.

    • Select menus.

  • Schedule

    Pending to be scheduled according to effort estimation.

 

4.1.2 Name, Role, Value (Level A)

  • Work point

    Some <frame> or <iframe> elements do not have a title.

  • Effect for the user

    Navigating through frames and inline frames can quickly become difficult and confusing for assistive technology users if the frames are not marked with a title attribute.

  • Plan of action

    Replace placeholder titles such as "untitled frame" with a more appropriate phrase.

  • Schedule

    Pending to be scheduled according to effort estimation.

 

Accessibility PDF documents

All PDF files from the website are accessible.

 

Preparation of this accessibility statement

This accessibility statement was drawn up on 20/01/2020.

The accessibility of this website was checked via a manual inspection and the tool Lighthouse Chrome plugin.

The accessibility statement was last revised on 20/01/2020.

 

Compatibility with browsers and supporting technologies

This website is made to be compatible with most common accessibility technologies. We also use compatibility with the most current browsers.

 

Technical specifications

The accessibility of a website depends on the following technologies and can be guaranteed by supporting it on your device:

HTML5, CSS3 and JavaScript.

 

Feedback and contact details

o you have any comments or do you experience accessibility problems that have not yet been addressed and are not listed as working points? Let us know.

end an email to info@velo-antwerpen.be

We strive to provide you with an answer within 7 working days.