Accessibility statement
Tikkurila.com online service
This accessibility statement applies to the digital service tikkurila.com and was published on 11.12.2025. The description of the service’s accessibility is based on self-assessment and an evaluation conducted by an external expert organization.
Our goal is to provide digital services that are accessible to all users. This accessibility statement outlines the known issues in the accessibility of the service and provides instructions on how to send us feedback or improvement suggestions regarding accessibility.
Accessibility status of the digital service
The service partially complies with the accessibility requirements.
Non-accessible content
The following content and functions do not yet meet the requirements of WCAG 2.1 levels A and AA. We aim to address the key issues by the end of June 2026.
Recurring issues
Header
- The open/closed state of the main menu items is not conveyed to assistive technologies, and menu item labels lack a button role on mobile. (4.1.2)
- The focus order of sub‑menus is incorrect on mobile. (2.4.3)
- Menu headings do not describe their contents sufficiently and are in the wrong language. (2.4.6), (3.1.2)
- The main menu button’s name is not descriptive enough, its open/closed state is not conveyed to assistive technologies, and its aria-controls value is incorrect. (4.1.2)
- The active segment is not indicated programmatically. (1.3.1)
- The skip to content link does not appear when receiving keyboard focus. (2.4.7)
- After closing the search or the "Checklist", focus incorrectly shifts to the main menu button on mobile. (2.4.3)
- The "Checklist" content does not fit on vertically narrow screens without content getting cut off. (1.4.10)
Footer
- The footer’s logo link lacks text equivalent. (1.1.1), (2.4.4)
- Footer headings are not marked programmatically as headings. (1.3.1)
- The chatbot’s visible name is not included in its accessible name. (2.5.3)
Cookies (modals / consent / cookie banners etc.)
- The cookie modal does not automatically receive keyboard or assistive‑technology focus when arriving at the site. (2.4.3)
- Accordion toggle buttons do not receive visible focus, their expanded/collapsed state is not conveyed to assistive technologies, and when expanded, they lack a name. (4.1.2)
- When navigating to subpages from the cookie banner, focus jumps directly to the buttons at the bottom. (2.4.3)
- The "Privacy policy" link has been implemented incorrectly as a button. (4.1.2)
Cards and carousels
- The "Add to checklist" buttons do not receive keyboard focus, nor do they have an accessible name. (2.1.1), (4.1.2)
- The heading levels within cards do not follow a logical structure; and for some cards, links lack a name describing their target. (1.3.1), (2.4.4)
- Carousel buttons receive focus in the wrong place; the focus is not visible; and accessible names are in the wrong language. (2.4.3), (2.4.7), (3.1.2)
Forms
- Checkboxes are not grouped programmatically, and checkbox roles have been incorrectly assigned to other elements. (4.1.2)
- Mandatory fields are marked with an asterisk, but the asterisk lacks an explanation. (3.3.2)
- General user information fields lack appropriate autocomplete attributes. (1.3.5)
Search and filters
- The close button of the search dialog lacks an accessible name; and the "Send" button inside the dialog is unclear regarding its purpose. (4.1.2)
- There is no programmatic feedback when search results are updated or filters are cleared. (1.3.1), (4.1.3)
- Search fields have been implemented inconsistently across different pages. (3.2.4)
- Loading new search results is implemented inconsistently across different pages. (3.2.4)
- Search fields are missing accessible names. (4.1.2)
- Filters do not receive visible focus, and focus moves away from them when selections are changed. (2.4.7), (3.2.2)
Whole service
- Several visible texts, text alternatives, and accessible names are in the wrong language. (3.1.2)
- Some images lack alt attributes, and some decorative images have unnecessary text alternatives. (1.1.1), (2.4.4)
- Some interactive elements do not receive visible focus, or the focus contrast is too weak. (1.4.11), (2.4.7)
- Some texts do not meet minimum contrast requirements. (1.4.3)
- Feedback for adding or removing items from the "Checklist" is not conveyed to assistive technologies. (4.1.3)
- External links are not programmatically marked as external, or the marking is in the wrong language. (2.4.4), (3.1.2)
- Decorative icons are not hidden from assistive technologies. (1.1.1)
- Some pages include invisible links without descriptions. (2.4.4)
Page‑specific issues
Home page
- Several "Read more" links do not uniquely identify their targets. (2.4.4)
- Some headings are not programmatically marked as headings. (1.3.1)
- New products loaded via the "Load more products" button do not receive focus. (2.4.3)
Inspiration articles
- The newsletter banner image contains embedded text; its text alternative is incomplete and in the wrong language. (1.1.1), (1.4.5), (3.1.2)
- The "Used colors" buttons do not have unique names. (2.4.6)
Color pages
- Carousel arrow buttons do not have sufficiently descriptive accessible names. (4.1.2)
- The feedback section’s language attribute is incorrect. (3.1.2)
Color planning
- Form error messages are not conveyed programmatically. (4.1.3)
- Help texts for input fields are not programmatically associated with fields. (4.1.2)
Products for interiors
- The search button lacks an accessible name. (4.1.2)
- Pagination heading is not associated with the list element; the active page is not marked programmatically; and the "…" element has an incorrect role. (4.1.2)
- On mobile view, filters are visually hidden behind the dialog but still receive focus. (1.3.1), (2.4.7)
Product page
- The "Add to checklist" button lacks an accessible name. (4.1.2)
- Additional details of stamps are not accessible with keyboard. (2.1.1)
- The alt text for the humidity and temperature chart is missing measurement units. (1.3.1)
All products for do‑it‑yourself painters
- Checkboxes are not programmatically associated with their labels, and do not receive visible focus. (2.4.7), (4.1.2)
All products
- Buttons for the YouTube player receive focus before video activation; and the visual play button is accessible with keyboard. (2.4.7), (2.1.1)
- Links embedded in text are indicated only by color. (1.4.1)
Find a store
- Store cards have incorrect roles and accessible names; and contain nested interactive elements. (3.1.2), (4.1.2)
Contact
- The embedded form’s iframe title is unclear and in the wrong language. (3.1.2), (4.1.2)
Accessibility statement for the Tikkurila Visualizer service
This accessibility statement applies to the digital service Tikkurila Visualizer and was published on 11.12.2025. The description of the service’s accessibility is based on self-assessment and an evaluation conducted by an external expert organization.
Our goal is to provide digital services that are accessible to all users. This accessibility statement outlines the known issues in the accessibility of the service and provides instructions on how to send us feedback or improvement suggestions regarding accessibility.
Accessibility status of the digital service
The service partially complies with the accessibility requirements.
Non-accessible content
The following content and functions do not yet meet the requirements of WCAG 2.1 levels A and AA. We aim to address the key issues by Q1 2026.
Language selection
- Changing the language does not update the language settings. Language options do not have correct language settings. (3.1.2)
- The language selection menu does not remain readable when text is enlarged to 200%. (1.4.4)
Home View
- The component uses an invalid ARIA attribute, causing items to be announced as buttons even though they cannot receive focus via the Tab key and therefore do not behave like standard buttons. (4.1.2)
Room Views
- Some elements are missing accessible names. (4.1.2)
- The image and color selection elements do not indicate correct tab-like behavior to assistive technologies. (4.1.2), (2.4.3)
- The language and color category menus use invalid ARIA attributes, are not fully reachable or operable with the Tab key, fail to expose key states (such as selection and open/closed status), and on iOS with VoiceOver selecting a color collection closes the view unexpectedly. (4.1.2), (2.4.3)
- The selected surface is not exposed programmatically, the arrow buttons cannot be focused with Tab despite appearing as standard buttons, and color changes provide no programmatic feedback. (4.1.2), (4.1.3)
- The color selection component uses an invalid ARIA attribute, causing items to be announced as buttons even though they cannot be focused with Tab, and does not expose which option is selected. (4.1.2)
- The “Last used” menu cannot be closed with the keyboard, and the closing control lacks a role, name, and state information; additionally, the color options lack descriptive roles. (2.1.1), (4.1.2)
- Color selection view is not usable in landscape orientation. (1.3.4)
- Assistive technology focus does not move into the Start Over dialog when it opens. (2.4.3)
- The open/closed state of search suggestions is not conveyed. (4.1.2)
- Search results do not have appropriate roles. (4.1.2)
- The room image does not have an alt attribute. (1.1.1)
Did you notice an accessibility issue in our digital service?
You can provide us with accessibility feedback via the feedback form. Please describe the issue as clearly as possible.
If you encounter any accessibility issues on the website, we recommend that you first provide feedback to us as the administrators of the service. We will respond within 14 days. If you are not satisfied with the response you receive, or do not receive a response within two weeks, you can escalate the issue to the Traficom.
Contact information for the supervisory authority
Finnish Transport and Communications Agency Traficom
Digital Accessibility Supervision Unit
telephone switchboard 029 534 5000