Luhta.fi – deficiencies listed in the accessibility statement

Email feedback:

• Feedback regarding accessibility issues can be sent to [email protected].

• There are some accessibility deficiencies in the service’s registration form. WCAG 1.3.5 Identify input purpose (AA), WCAG 4.1.2 Name, role, value (AA)

  • Input fields are missing definitions that tell assistive technologies that the field is mandatory or its status has errors. The browser may not necessarily be able to complete the field automatically for the user.

  • The button that shows the password entered in the field has no name.

• In addition, in forms meant for logging in or signing up, it is difficult for the user to detect an error status in the form if they are using the service solely with the information provided by an assistive technology. WCAG 1.3.3 Sensory characteristics (A), WCAG 3.3.1 Error identification (A), WCAG 4.1.3 Status messages (AA)

  • When a form is submitted, a person using assistive technology is not notified of errors on the form.

  • The error messages are in English, regardless of the language of the website.

  • The error message does not explicitly indicate the field to which the error is related.

• The number of products shown on a product list is updated whenever the user changes the filters on the website. However, the updated number is not forwarded to screen readers. WCAG 4.1.3 Status messages (AA)

• The search field in the header shows search results as the user inputs characters into the field. A user of a screen reader does not receive information about available results and may therefore not know how to navigate to them. The search results list can also remain permanently on top of the other content as it cannot be closed with keyboard browsing. In addition, the form is missing a name that is always visible because the so-called placeholder text is replaced with the characters input by the user. WCAG 3.3.2 Labels or instructions, WCAG 4.1.2 Name, role, value

• On the product page, the size selection functions as a combo box (so-called select HTML element). However, the control has not been implemented as a combo box or a drop-down list for assistive technology tools. WCAG 4.1.2 Name, role, value (AA)

• The website has functionalities that are difficult to use with screen readers because they are missing the technical definition needed by the assistive technology. WCAG 4.1.2 Name, role, value (AA)

  • The buttons on the website’s navigation menu do not indicate whether the drop-down list that the button opens is open or closed.

  • The same issue exists in the cart button as it does not indicate whether it is open or closed.

  • The header has a button (e.g. “Finland”) that the user can use to go to the website of a certain country. The button does not indicate that it opens a modal dialog.

  • The website’s main page has content that has been implemented in a tab-like manner. The tabs may have buttons that have not been named or labelled as a button.

  • The website uses so-called accordion buttons that can be used to open or hide content. For example, the frequently asked questions on the product page are accordions. The elements correctly indicate when they are open, but once they are closed, the status is not updated on a screen reader.

  • Similar buttons can be found on the search page where the search filters are inside drop-down menus that can be opened and closed. The buttons do not indicate that they can be opened and closed.

  • On product pages, the colour of the product can be selected with buttons. However, the buttons do not tell the assistive technology which colour is selected, i.e., which button has been pressed.

  • In the size information dialog, it is possible to select whether the sizes are shown in centimetres or inches. The selected unit is not forwarded to screen readers.

• The main site has clickable cards, for example, under “News”. Their reading order is illogical from the point of view of a person using a screen reader: The card includes the link first and the heading second, which means that the heading defines the content of the following card. WCAG 1.3.2 Meaningful sequence (A)

• The website has elements that are missing a name forwarded to assistive technologies, or the name is unsuitable. WCAG 1.1.1 Non-text content (A)

  • The header’s Wishlist link is always in English.

  • Country selection: Certain country names are associated with an additional information icon: “Online shopping available”. This is not forwarded to assistive technology tools.

  • The payment methods listed in the footer are pictures without names.

  • The product page has a so-called carousel element with which the user can browse the available product images. All of the carousel buttons are named after the product, which makes their purpose unclear. The carousel also has English content, “Page X of Y”, which is meant only for screen readers.

  • The carousel’s browser buttons are missing names completely they are always in English (mobile view).

  • In store search, contact information is shown as icons that have not been named for assistive technologies.

  • In the cart, the field that indicates the number of products has no name. Likewise, the buttons that can be used to add or reduce the number of items or to remove a product have no name.

  • The company page has link fields with both a text link as well as a nameless link that covers the entire screen.

• Next to the product listing, there are product types on the basis of which the product listing can be changed. The product types are accordion buttons. However, they also include a link element, so they have two clickable nested objects, which is why assistive technologies may function abnormally with accordions. WCAG 1.3.1 Info and relationships (A)

• The website is missing a structurally marked main content section. If a site has several navigation areas, they have not been named. The breadcrumb trail is also always missing a name. WCAG 1.3.1 Info and relationships (A)

• Not all text meant as headings is marked as a heading technically, and some headings are ranked illogically. WCAG 1.3.1 Info and relationships (A)

• The main site has a tab selection in front of some product carousels that can be used to change the product type on the carousel. However, the selection is not technically implemented as a tab structure. WCAG 1.3.1 Info and relationships, WCAG 4.1.2 Name, role, value

• Keyboard focus does not always move to the correct place on the website even if the action carried out by the user requires it. For example, clicking the Favourites icon link may open the login function, but the user’s focus remains on the link element instead of moving to the login. Similarly, the “Show more” buttons may keep the focus at a random spot on the website. The Back to top link in the footer only scrolls the website visually. WCAG 2.4.3 Focus order (A)

• In product listings, products are shown as clickable cards in which, among other things, the available colours are shown as thumbnails. When you point the photos with a mouse, the card shows which sizes are available in the colour in question. However, the size information is not shown if keyboard focus is used on the photos. A user of a screen reader will also not receive the size information as a photo label. WCAG 1.3.1 Info and relationships (A), WCAG 2.1.1 Keyboard (A)

• The website has text with poor contrast and, therefore, poor resolution. The type of some controls, such as the shape of input fields, and the status of various selectors may have poor resolution due to low contrast. WCAG 1.4.3 Contrast (minimum) (AA), 1.4.11 Non-text contrast (AA)

• Some of the controls and clickable elements do not show keyboard focus at all, or the focus is difficult to discern due to poor contrast. WCAG 2.4.7 Focus visible (AA)

• The store search has an embedded map with accessibility deficiencies, especially from the point of view of a user of assistive technologies. However, corresponding information is also available as text on the website. WCAG 4.1.2 Name, role, value

• Certain texts have been defined with an absolute size as CSS pixels, which is why users may not be able to change the size of the text in browser settings. WCAG 1.4.4 Resize text (AA)