On September 23, the web accessibility directive comes into force. This means that authorities and other actors within digital public services must publish an accessibility statement on their websites. The report must describe how to meet the accessibility requirements i WCAG 2.1 AA. With the report, there must be a way for users to point out obstacles DIG (the authority for digital administration), which follows up on the directive.

Reviewed together with Funka

Nordic Medtest is responsible for testing parent company Inera's services. Together with a consultant from Work Jonathan Petrone, tester at Nordic Medtest, has reviewed the accessibility of some of Inera's services, using the web accessibility directive as a starting point.

- We have reviewed the services and developed proposed solutions to the problems we found as well as developed documentation so that the services can write a good accessibility report about their service, says Jonathan.

- In the report, known deficiencies in accessibility and how it is planned to remedy these must be communicated to users. There must also be contact information available for comments directed at the service, with further reference to DIGG, if the user is not satisfied. The idea is that the report should be easy to understand and not contain advanced technical language or code examples, says Jonathan.

Testing user experiences in UX frameworks

Jonathan Petrone has worked with UX (User Experience) in an internal project at Inside. The UX framework is intended as a gathering place for work with user experience within Inera, where you can get information on how to work with UX. There is a component library that can be used as a reference when building and updating your service. Jonathan has tested the accessibility of the components and written recommendations regarding accessibility aspects, on various subpages in the framework.