Fulfilment of the accessibility requirements is not difficult from a technical point of view. However, a prerequisite for this is the ability to consider the requirements already in the service development phase, and designers and developers must be familiar with the solutions resulting from the requirements.
In the best case, accessibility can be a driver of service development, as it clarifies the features required from web services.
The software developer section is only available in English.
The tools and methods featured in the modules take into account the role and responsibility of the person in taking accessibility into consideration when developing a new service.
- Identifying the key user groups of the service and understanding their needs.
- Responsibilities of the client and the supplier (procurement, implementation, testing).
- Who determines and owns accessibility?
- Practical perspectives on procurement and tendering.
Read more in the ‘Objectives of the service’ module.
- Use cases describe what functions service users need from a service and how these functions are performed in the service.
- Well-created use cases steer user interface design. They help avoid the accumulation of unnecessary functions and contents in the service.
- Use cases are also key in successful accessibility user testing.
Read more in the ‘Use cases’ module.
- The specification phase involves making sure that the visual and technical structures of the service work together in a manner that facilitates effortless production of accessible code.
- Examples of the tools used include so-called wireframe models and interactive user interface prototypes.
- Helsinki Design System (HDS) provides a library component interface that must be taken into account in the specification phase.
Read more in the ‘Software specification’ module.
- This work phase involves implementing (coding) and testing the technical solutions of the service, such as the user interface components and the page structure.
- The specification and use cases are iterated as needed.
- The visual style of the service is created in conjunction with the coding and specification processes, never separately.
- Helsinki Design System (HDS) provides ready-made, reusable library components and implementation instructions for easy accessibility assurance.
Read more in the ‘Implementation and software testing’ module.
- How can the accessibility of a service be assessed and improved through user testing carried out with special users?
- What practical differences and considerations are related to testing carried out with special users?
- Application of City-wide, unified testing practices.
Read more in the ‘Accessibility user testing’ module.
- In the accessibility audit process, the accessibility of the service is assessed as a whole and more broadly than individual components or usage paths.
- The auditing is based on legally prescribed requirements. The tools used include the WCAG (Web Content Accessibility Guidelines) criteria.
- An audit carried out in accordance with the Accessibility Model will produce an up-to-date accessibility statement required by law.
Read more in the ‘Accessibility auditing and creating an accessibility statement’ module.
- Accessibility must also be taken into consideration systematically after publishing when content is produced for the service or the service is developed further.
- Of what kind of use could the testing tools be in monitoring and maintaining the accessibility of the service?
- What must be taken into consideration when deciding to expand, overhaul or otherwise develop the service?
Read more in the ‘Maintenance and post-publication development’ module.
Utilising the help of experts is also recommended. The accessibility service is intended for making sure that digital accessibility is taken into consideration in all service and content production phases from development to publication.