Accessibility of HSL's digital services

General

• Video content

  Subtitles and/or audio description are missing from some video content. (WCAG 1.2.1, 1.2.2)

• Visual elements

  There are deficiencies in the text alternatives for visual elements, and they remain hidden from screen reader users. (WCAG 1.1.1)

Home page

• The automatic route search behaves unpredictably from the user’s perspective

  The route search is triggered when the destination field is completed. The browser then moves away from the home page to another page, the Journey Planner. From the user’s perspective, this is unpredictable. (WCAG 3.2.2)

• Focus trap in the search function

  When the search field receives focus on the home page in responsive view, it opens a full-screen dialog. Focus is restricted to this dialog. After it is closed, focus is moved to the start of the page, and moving focus to the search function causes it to open again, making it impossible to move past the search field. (WCAG 3.2.2)

• Opening the time picker

  When the Open picker button is pressed on a mobile device, a dialog opens showing the departure time and arrival time pickers. In the dialog, focus moves directly to the date selection, and the content at the content at the top of the dialog is skipped. Users of assistive technologies may not notice the controls at the top of the dialog. (WCAG 2.4.3)

• Attributes of the favorites button

  There are deficiencies in the implementation of the Open favorites button. (WCAG 4.1.2)

• Button names

  There are deficiencies in button labeling. (WCAG 1.1.1)

Search

• The screen reader does not read the selected search suggestion

  When text is entered in the search field in the top bar, search results are shown below the field. However, the screen reader does not read the selected item. Depending on the screen reader, it either reads the content of the search field for every option or reads nothing at all. (WCAG 4.1.2)

Disruptions and service changes

• States of toggle buttons

  Disruption alerts can be filtered using toggle buttons. However, in the initial state, they work the opposite of normal: all buttons are selected, and when one button is pressed, the states of the other buttons change, but not the state of the button that was pressed. The state of unselected buttons is not announced. Only selected buttons are identified as selected. (WCAG 4.1.2)

• Announcing the results of the search and filtering functions

  Disruption alerts can be searched and filtered using several options. When selections are made, the list of alerts updates accordingly. While this change is easy to see visually, it is not communicated to users of assistive technologies. (WCAG 4.1.3)

Feedback

• Leaving a combo box

  When the selection list is open, it is not possible to leave the combo box with a single press of the Tab key. The combo box is a single focusable element. When leaving the list opened with the Tab key, the selected list item should be set as the value of the combo box. At present, the value is cleared. (WCAG 2.4.3)

• Selecting the suggested value

  The combo box does not correctly set the selected value to match the item already displayed in the field (WCAG 3.3.1, 4.1.2)

   

City bikes – general observations

• The <title> elements of pages are too general, which means that the page content cannot always be inferred from the title. (WCAG 2.4.2)
• The drop-down menus do not work fully with keyboard use because they use customized components. (WCAG 1.3.1, 4.1.2)
• The third-party feedback tool used on the site does not comply with the standards. (WCAG 1.3.1, 1.4.5, 1.4.10, 4.1.2)
• Some input fields in the service use solutions that are problematic from an accessibility point of view. (WCAG 1.3.1)
• The link texts in the service are not always sufficiently precise, making it difficult to determine with certainty where the link leads. (WCAG 2.4.4)
• There are some deficiencies in screen reader focus and reading order. (WCAG 1.3.2, 2.4.3)
• On certain pages, the heading structure is unnecessarily complex, which causes problems when using a screen reader. (WCAG 1.3.1, 2.4.6)
• The structure of the travel history may not be conveyed correctly to a screen reader. (WCAG 1.1.1 ja 1.3.2)
• Some code ID values are named in a way that does not comply with the standard, which may cause problems when using assistive technologies. ( (WCAG 4.1.1)

City bikes – purchasing

• Keyboard use and the VoiceOver screen reader on iOS do not always function logically in parts of the purchase flow. (WCAG 2.1.1, 2.1.2, 3.2.1)
• Not all error messages are accessible. (WCAG 3.3.1, 3.3.3)
• Example content in input fields does not meet the contrast requirements. (WCAG 1.4.3, 2.4.7)
• The step path in the purchase flow does not work appropriately with all assistive technologies (WCAG 1.1.1, 1.3.1)
• Information about the selected product is not conveyed appropriately by all assistive technologies. (WCAG 1.1.1, 1.3.1)
• Some screen readers behave illogically in certain content areas of the service. (WCAG 1.3.1, 4.1.3)
• The structure of the payment elements causes problems for screen reader use. (WCAG 1.1.1, 1.3.1)
• The heading of the radio buttons used to select the number of bikes does not work with all screen readers. (WCAG 1.3.1, 4.1.2)
• There are minor deficiencies in the translations of the payment elements. (WCAG 3.1.1)
• The labels for the payment elements in Vantaa are ambiguous. (WCAG 3.2.4, 3.3.2)
• There are deficiencies in the headings within the purchase flow, so the page content cannot always be inferred directly from the headings. (WCAG 1.3.1, 3.2.2)
• Some labels in the Helsinki–Espoo system are not appropriate. (WCAG 2.5.3)
• Acceptance of the terms of use has not been implemented logically for all screen reader devices. (WCAG 1.3.1, 2.4.6, 4.1.2)
• The contact information review lacks a programmatic structure, so screen readers do not distinguish headings from body text. (WCAG 1.3.1)
• The text alternatives for buttons are not always logical. (WCAG 4.1.2)

City bikes – fault reports

• Submitting a fault report using only a keyboard is difficult because of inconsistencies in focus behavior. (WCAG 2.1.1)
• Some input fields do not work logically in the mobile version. (WCAG 1.4.13, 2.1.2, 2.4.3, 3.2.1, 3.2.2, 4.1.2)
• Returning to previous stages in the fault report form is unclear for all user groups, but especially for screen reader users. (WCAG 1.1.1, 1.3.1, 4.1.2)
• Submitting a fault report and making selections is particularly difficult for screen reader users. (WCAG 1.3.1, 2.4.3, 3.2.2, 4.1.1)
• Some error messages are incomplete. (WCAG 1.4.1, 3.3.1, 3.3.3)
• Not all visually visible headings have been marked up programmatically. (WCAG 1.3.1)
• Example content in input fields does not meet the contrast requirements. (WCAG 1.4.3)

iPhone application

General

• The application does not adapt to device orientation. This can be enabled in the settings, but it is not enabled by default. (WCAG 1.3.4)
• Some of the content does not respond to system-level text resizing features, for example, in news, disruption alerts, the accessibility statement, terms of use and the bottom navigation bar. (WCAG 1.4.4)
• When using the app in Finnish or Swedish, the component type and state are announced in English in some components. (WCAG 4.1.2)

Tickets

• The keyboard focus indicator is not clearly perceivable in blue action buttons. (WCAG 2.4.7)
• When the expandable section in the ticket view is opened, focus is moved to the expand button after a short delay. (WCAG 2.4.3, 1.3.2)

Journey Planner

• When filtering by mode of transport, transport mode icons have duplicate text alternatives. (WCAG 1.1.1)
• When opening the detailed view of a route, the action buttons are not accessible via keyboard. They can only receive focus after the view has been scrolled. (WCAG 2.1.1)
• The real-time location of vehicles along the route is not available to screen reader users. (WCAG 1.3.1)

Android application

General

• View headings have not been programmatically marked as headings in all views. (WCAG 1.3.1)
• The back button in individual news items cannot be used with the keyboard on Android devices. (WCAG 2.1.1) 
• The application does not adapt to device orientation. This can be enabled in the settings, but it is not enabled by default. (WCAG 1.3.4)
• Some views cannot be closed using the keyboard, as the close buttons are not accessible via keyboard. (WCAG 2.1.1)
• Many text input fields cannot be used with the keyboard, as they cannot receive focus. (WCAG 2.1.1)

Tickets

• The validity period of the ticket cannot be selected using the keyboard. (WCAG 2.1.1)
• When the additional information window for the ticket validity area is opened, focus can be moved to content behind the window. When the window is closed, focus is not returned to the button that opened it.(WCAG 2.4.3)

Journey Planner

• The real-time location of vehicles along the route is not available to screen reader users. (WCAG 1.3.1)
• In the Journey Planner, the map can be resized by pinching, but this cannot be done using the keyboard. (WCAG 2.1.1)