Accessibility Statement
Accessibility of the SFS Store
This accessibility statement explains how the SFS Store online service and reading portal comply with the Act on the Provision of Digital Services, what shortcomings there are in their accessibility, and how you can provide us with feedback on accessibility issues.
These services are provided by SFS Finnish Standards. We want as many users as possible to be able to use our digital services. We take accessibility into account in the development of our digital services.
How accessible are the services?
These services partially meet the accessibility criteria required by law at levels A and AA (WCAG 2.1 and 2.2). There are some accessibility shortcomings that are described in more detail below.
Have you noticed accessibility shortcomings?
We continuously strive to improve the accessibility of the services. If you find issues that are not described on this page, please let us know and we will do our best to correct the shortcomings. We will respond within 14 days.
You can contact us via the feedback form or by email at store@sfs.fi.
Monitoring of Accessibility
The Finnish Transport and Communications Agency (Traficom) monitors the implementation of accessibility requirements. If you are not satisfied with the response you receive, or if you do not receive a response at all within two weeks, you can provide feedback to Traficom. Traficom’s website “Submit a complaint on web accessibility or request clarification” provides detailed information on how to file a complaint and how the matter will be handled.
Finnish Transport and Communications Agency Traficom
Digital Accessibility Supervision Unit
www.webaccessibility.fi
saavutettavuus@traficom.fi
Telephone switchboard: +358 29 534 5000
Detailed Information on Technical Accessibility
The services are not yet fully accessible.
Content or Functions that are Not Yet Accessible
The content listed below is not accessible for the following reasons:
Non-compliance with the Act on the Provision of Digital Services (306/2019)
The shortcomings listed here are intended to be corrected by March 1st, 2026.
Yleiset ongelmat
• Palveluissa on joitakin teksti- ja kuvamuotoisia linkkejä ja painikkeita, joiden näkyvät tai saavutettavat nimet eivät ole riittävän kuvaavia. Ruudunlukija ei aina lue linkin ymmärtämiseksi tarvittavia lisätietoja yhdistettynä linkkiin. Joidenkin toiminnallisten kohteiden ja lomakkeiden saavutettavat nimet ovat englanniksi. (WCAG 2.4.4, 1.1.1, 2.4.6)
• Ruudunlukijat saattavat ääntää tiettyjä sivuja ja sivujen sisältöjä väärän kielen mukaisella ääntämyksellä, koska kielimerkinnät ovat paikoin puutteellisia. (WCAG 3.1.1, 3.1.2)
General issues
• The services contain some links and buttons in text and image format, the visible or accessible names of which are not sufficiently descriptive. The screen reader does not always read the additional information needed to understand the link combined with the link. (WCAG 2.4.4, 1.1.1, 2.4.6)
• Screen readers may pronounce certain pages and page contents with the pronunciation of the wrong language, because the language markings are incomplete in places. (WCAG 3.1.1, 3.1.2)
• Screen readers step through certain links (such as social media links and, in the case of VoiceOver screen reader, other external links) in multiple parts. (WCAG 1.3.1, 2.4.3)
• The service has some checkboxes (e.g. in the user management table) and radio buttons (e.g. in forms) that are not associated with relevant information related to them. This may somewhat slow down using these functionalities with a screen reader. (WCAG 1.3.1)
• There are some functional items in the SFS Store that do not have a clear functional role (e.g. a button) or accessible information about their state (e.g. expanded/collapssed, current). Individual search filters have erroneous collapsed state information, even if they do not open a submenu. In some situations, the state information of functional items (e.g. the menu of search filters) is expressed incorrectly. (WCAG 4.1.2)
• There are individual functional items in the SFS Store that do not have an accessible name (e.g. in the search results and on the card payment page), or the accessible name is misread (e.g. Show/hide password button). (WCAG 4.1.2, 2.4.6)
• In the SFS Store, the screen reader user does not always receive a status message about success, error or search results. In addition, in some situations, communication is incomplete from the user's perspective (for example, "updating..." without notice of when the information has been updated) and sometimes there is extra noise in the status messages that interfere with the use of the service. In some places, the screen reader reads the status messages in the wrong order, i.e. it starts with the end result and then reads a message about loading. With some buttons, the screen reader does not read the changed name of the button in real time. (WCAG 4.1.3)
Perceiving and understanding content
• In the order history table, the column headers overlap when the font is enlarged towards 200 percent. (WCAG 1.4.4)
• In the SFS Store, there are individual views where the content has to be scrolled horizontally on narrower screens, or some of the content written in the text field is left out of the view. (WCAG 1.4.10)
• Understanding the tables using a screen reader can be difficult. In some tables, a screen reader combines data cells with incorrect column headers. Some data pair structures are presented in tabular form, which is not the most ideal representation for them. Some tables also have blank rows and columns. In some places, the screen reader focuses the cells in the same row in one step. (WCAG 1.3.1, 2.4.3)
• The services also include other content, the structure and relationships of which may be difficult to perceive with a screen reader. In the screen reader's document mode, some text content and functionality are not wrapped correctly, and there do not always seem to be spaces between words with the screen reader and braille display. Some individual list structures have also been implemented incorrectly. (WCAG 1.3.1)
Navigating in the services
• The page titles of some pages are not unique or descriptive enough. (WCAG 2.4.2)
• The services have pages that can only be found through one route. (WCAG 2.4.5)
• Focus does not always behave consistently. User management page has modal dialogs that allow the user to tab into the underlying page content. In the standard search and during the purchase process, there are situations where the screen reader focus shifts to an illogical or unexpected location when performing actions on a page or moving from one page to another. (WCAG 2.4.3, 3.2.2)
• In some places, the order in which content and functions are read and focused is illogical. (WCAG 1.3.2, 2.4.3)
• There are some individual scenarios in the SFS Store where there are extra focus stops. The VoiceOver screen reader focuses individual search filters even when the submenu of those filters is visually closed, treating them as unnamed menu items. In addition, the tooltips related to selecting the delivery method cause extra tab stops. (WCAG 2.4.3, 1.3.1)
• There are individual texts in the SFS Store that are marked as headings, even though they are not actually headings. (WCAG 1.3.1)
Forms
• Many text fields do not support autofill. (WCAG 1.3.5)
• Some search fields (e.g. on My products page) do not have a label. (WCAG 3.3.2)
• The user does not always receive sufficient information about the requirements of the forms. For example, the format instructions for payment card fields disappear as the user starts to type. Not all mandatory fields have been correctly marked as mandatory (e.g. the screen reader does not always read this information when navigating with the tab key), and a known correction suggestion has not been offered for all errors. When creating a new password, the password requirements are presented only after the password field and are not associated with the field. (WCAG 3.3.2, 3.3.3, 1.3.1, 1.3.2, 4.1.2)
The standards and other PDF and HTML products that are for sale
• The accessibility requirements do not apply to the standards. The standards are comparable to various documents and updated guidelines rather than to e-books. The nature and content of an e-book are more permanent, while the standards are regularly updated and thus more in tune with the times.
Other issues
• The menu for selecting the number of search results to display per page has an inconsistent visible and programmatic name. This can make it difficult to use the menu with voice control or a screen reader by sight. (WCAG 2.5.3)
How we have tested accessibility
The observations in this accessibility statement are based on a third-party assessment by Avaava Digital Oy of whether the service meets the legal requirements defined in the law.
The service was launched on December 9th, 2025.
This statement was prepared on December 2nd, 2025.
The statement was last updated on December 2nd, 2025.