Accessibility - Helsinki City Pass

What is digital accessibility?

An accessible website is one that allows people with disabilities to access its content and features without difficulty.

An accessible website allows users to, for example:

Navigating with speech synthesis and/or a braille display (especially used by blind and visually impaired people).
Customize the site display according to your needs (enlarge text, change colors, etc.).
Navigate without using the mouse (using only the keyboard, via a touchscreen, voice, or any other suitable device).

To achieve this, the site must comply with the standards in force during its creation and updates.

Declaration of conformity to the RGAA

Helsinki City Pass is committed to making its service portal accessible in accordance with Article 47 of Law No. 2005-102 of February 11, 2005.

This accessibility statement applies to the online service: https://citypass.fi/.

Compliance status

The portal https://citypass.fi/ is partially compliant with the General Accessibility Improvement Framework (RGAA 4.1.2). The non-conformities are listed below.

Test results

The compliance audit carried out by Otipass reveals that 58% of the RGAA criteria are met ^*.

This percentage corresponds to: (out of a total of 36 applicable criteria)

21 criteria met
15 non-compliant criteria
13 inapplicable criteria
57 untested criteria

_{(*) This percentage is provisional. It is calculated based on the automated report which covers 49 out of 106 criteria.}

Criteria

Non-compliance

Criterion 2.1 : Does each manager have a manager title?
Criterion 3.1 : On each web page, information must not be conveyed solely through color. Is this rule respected?
Criterion 3.2 : In each web page, is the contrast between the text color and its background color sufficiently high?
Criterion 3.3 : In each web page, are the colours used in the interface components or graphic elements carrying information sufficiently contrasted?
Criterion 4.13 : Is each temporal and non-temporal media compatible with assistive technologies (except in specific cases)?
Criterion 6.1 : Is each link explicit (except in special cases)?
Criterion 6.2 : In each web page, does each link have a title?
Criterion 7.1 : Is each script, if necessary, compatible with assistive technologies?
Criterion 8.9 : In each web page, tags must not be used solely for presentation purposes. Is this rule respected?
Criterion 9.3 : In each web page, is each list correctly structured?
Criterion 10.6 : In each web page, is each link whose nature is not obvious visible in relation to the surrounding text?
Criterion 11.1 : Does each form field have a label?
Criterion 11.2 : Do labels allow you to know the exact function of the field?
Criterion 11.9 : In each form, is the label of each button relevant (except in special cases)?
Criterion 11.10 : In each form, is input validation used appropriately (except in special cases)?

Not applicable

Criteria for which the content in question is absent from the audited pages (automatic detection axe-core).

Criterion 4.10 : Is each automatically triggered sound controllable by the user?
Criterion 4.11 : Is the consultation of each time-based medium, if necessary, controllable by the keyboard and any pointing device?
Criterion 4.12 : Is the consultation of each non-temporal media controllable by the keyboard and any pointing device?
Criterion 5.8 : Each formatting table must not use elements specific to data tables. Is this rule respected?
Criterion 7.4 : For each script that initiates a context change, is the user notified or does he/she have control over it?
Criterion 8.7 : In each web page, is each language change indicated in the source code (except in special cases)?
Criterion 8.8 : In each web page, is the language code for each language change valid and relevant?
Criterion 10.14 : In each web page, can additional content appearing via CSS styles only be made visible by keyboard and any pointing device?
Criterion 11.11 : In each form, is the input validation accompanied, if necessary, by suggestions to facilitate the correction of input errors?
Criterion 11.13 : Can the purpose of an input field be deduced to facilitate the automatic filling of fields with user data?
Criterion 12.11 : In each web page, are the additional contents appearing on hover, on focus, or on activation of an interface component accessible by keyboard if necessary?
Criterion 13.1 : For each web page, does the user have control over each time limit that modifies the content (except in special cases)?
Criterion 13.8 : In each web page, is each moving or flashing piece of content controllable by the user?

Untested

Criterion 1.3 : For each image containing information that has a text alternative, is that alternative relevant?
Criterion 1.4 : For each image used as a CAPTCHA or as a test image, having a text alternative, does this alternative allow the nature and function of the image to be identified?
Criterion 1.5 : For each image used as a CAPTCHA, is there an alternative access solution to the content or function of the CAPTCHA?
Criterion 1.6 : Does each information-bearing image have, if necessary, a detailed description?
Criterion 1.7 : For each information-bearing image with a detailed description, is that description relevant?
Criterion 1.8 : Every text-containing image that carries information, in the absence of a replacement mechanism, should, if possible, be replaced by styled text. Is this rule respected (except in specific cases)?
Criterion 1.9 : Is each image caption, if necessary, correctly linked to the corresponding image?
Criterion 2.2 : For each manager with a manager title, is that manager title relevant?
Criterion 4.1 : Does each pre-recorded time-based media have, if necessary, a synchronized text transcript or audio description?
Criterion 4.2 : Does each pre-recorded time-based media have, if necessary, a synchronized text transcript?
Criterion 4.3 : Does each pre-recorded time-based media item have a synchronized audio description, if necessary?
Criterion 4.4 : For each pre-recorded time-based media item with a synchronized text transcript or audio description, is the transcript or audio description relevant?
Criterion 4.5 : Does each pre-recorded time-based media have a relevant synchronized text transcript?
Criterion 4.6 : Does each pre-recorded time-based media item have a relevant synchronized audio description?
Criterion 4.9 : For each non-temporal medium that has an alternative, is that alternative relevant?
Criterion 5.1 : Does each complex data table have a summary?
Criterion 5.2 : For each complex data table that has a summary, is the summary relevant?
Criterion 5.3 : For each formatting table, does the linearized content remain understandable?
Criterion 5.5 : If there is a title, is it relevant?
Criterion 7.2 : For each script that has an alternative, is that alternative relevant?
Criterion 7.5 : On each web page, are status messages correctly rendered by assistive technologies?
Criterion 8.1 : Is each web page defined by a document type?
Criterion 8.2 : For each web page, is the generated source code valid according to the specified document type?
Criterion 8.6 : For each web page with a page title, is that title relevant?
Criterion 8.10 : In each web page, are changes in reading direction indicated?
Criterion 9.4 : In each web page, is each quotation correctly indicated?
Criterion 10.1 : In the website, are style sheets used to control the presentation of information?
Criterion 10.2 : In each web page, does the visible content carrying information remain present when stylesheets are disabled?
Criterion 10.3 : In each web page, does the information remain understandable when stylesheets are disabled?
Criterion 10.5 : In each web page, are the CSS declarations for element background and font colors used correctly?
Criterion 10.7 : On each web page, for each element receiving focus, is the focus being visible?
Criterion 10.9 : On each web page, information must not be conveyed solely through shape, size, or position. Is this rule being respected?
Criterion 10.10 : On each web page, information should not be conveyed solely through shape, size, or position. Is this rule implemented appropriately?
Criterion 10.11 : For each web page, can the content be presented without loss of information or functionality and without resorting to vertical scrolling for a window with a height of 256 px, or a horizontal scroll for a window with a width of 320 px (excluding special cases)?
Criterion 10.13 : In each web page, are the additional contents appearing when focus is taken or when hovering over an interface component controllable by the user (except in special cases)?
Criterion 11.3 : In each form, is each label associated with a form field having the same function and repeated several times in the same page or in a set of pages consistent?
Criterion 11.4 : In each form, are each field label and its associated field adjacent (except in special cases)?
Criterion 11.5 : In each form, are fields of the same type grouped together, if necessary?
Criterion 11.6 : In each form, does each grouping of fields of the same type have a legend?
Criterion 11.7 : In each form, is each legend associated with a grouping of fields of the same type relevant?
Criterion 11.8 : In each form, are items of the same type in a choice list grouped in a relevant way?
Criterion 11.12 : For each form that modifies or deletes data, or transmits answers to a test or exam, or whose validation has financial or legal consequences, can the entered data be modified, updated, or retrieved by the user?
Criterion 12.1 : Does each set of pages have at least two different navigation systems (excluding special cases)?
Criterion 12.2 : In each set of pages, are the menu and navigation bars always in the same place (except in special cases)?
Criterion 12.3 : Is the "site map" page relevant?
Criterion 12.4 : In each set of pages, is the "site map" page accessible from the same functionality?
Criterion 12.5 : In each set of pages, is the search engine reachable in the same way?
Criterion 12.10 : In each web page, are keyboard shortcuts using only one key (lowercase or uppercase letter, punctuation, number or symbol) controllable by the user?
Criterion 13.2 : On each web page, a new window must not open automatically without user interaction. Is this rule respected?
Criterion 13.3 : In each web page, does each downloadable office document have, if necessary, an accessible version (except in special cases)?
Criterion 13.4 : For each office document that has an accessible version, does that version offer the same information?
Criterion 13.5 : In each web page, does each piece of cryptic content (ASCII art, emoticon, cryptic syntax) have an alternative?
Criterion 13.6 : In each web page, for each piece of cryptic content (ASCII art, emoticon, cryptic syntax) that has an alternative, is that alternative relevant?
Criterion 13.7 : In each web page, are sudden changes in brightness or flash effects used correctly?
Criterion 13.10 : In each web page, can functionalities usable or available by means of a complex gesture also be available by means of a simple gesture (except in special cases)?
Criterion 13.11 : On each web page, can actions triggered by means of a pointing device on a single point on the screen be cancelled (except in special cases)?
Criterion 13.12 : In each web page, can the functionalities that involve movement of the device or towards the device be satisfied in an alternative way (except in special cases)?

Establishment of this accessibility statement

This statement was made on March 27, 2026.

Technologies used to create the website:

HTML5
CSS3 / SCSS / Bootstrap
JavaScript / jQuery
ARIA
SVG

User agents, assistive technologies, and tools used to verify accessibility

Automated tests

This audit uses the axe-core tool to automatically detect accessibility issues.

Some RGAA criteria require manual verification and are not covered by this automated audit.

Manual tests

Additional testing is required to ensure content is rendered correctly with assistive technologies in accordance with the test environment described in the RGAA 4.1.2 reference database:

Wave (Chrome Plugin)
Lighthouse (Chrome)
Web Developer (Chrome Plugin)
WCAG Contrast checker

Pages of the site that have undergone compliance verification:

Feedback and contact

If you are unable to access content or a service, you can contact the website administrator to be directed to an accessible alternative or to obtain the content in another format.

Legal remedies

This procedure should be used in the following case.

You reported to the digital accessibility officer of Helsinki City Pass an accessibility issue that prevents you from accessing content or one of the services on its portal and you did not receive a satisfactory response.

Write a message to the Defender of Rights: https://formulaire.defenseurdesdroits.fr

Contact the Ombudsman's representative in your region: https://www.defenseurdesdroits.fr/saisir/delegues

Send a letter by mail (free of charge, no stamp required):
Defender of Rights, Free Reply 7112075342, Paris CEDEX 07