Archive service accessible to everyone
We implemented an accessibility test for Disec's Yksa archive service.
Case accessibility test for Yksa
With Mindhive's accessibility test, we were able to move quicker to the actual development work. The experts at Mindhive helped us understand what we needed to do differently to make our services more accessible. Once the development targets were already mapped out, we no longer had to spend time searching for them, and we could directly engage in productive work within our core expertise.
Kaisa Neuvonen
Account Manager
Disec Oy
Disec offers Yksa archive service, which is a Sähke2-certified archiving system. Yksa is also used by public sector entities, which is why the service is subject to legally defined accessibility requirements. At Disec's request, we conducted an accessibility test on the Yksa archive service, enabling their development team to more effectively implement the necessary changes.
Learn more
Disec.fi
Where did we start
Need
When updating the Yksa archive service, the client needed to ensure equal treatment of all user groups by meeting the accessibility requirements set at the A and AA levels of the WCAG 2.1 guidelines.
Solution
We conducted an accessibility test on the website, which helped the client to identify areas where accessibility could be improved.
Need
When updating the Yksa archive service, the client needed to ensure equal treatment of all user groups by meeting the accessibility requirements set at the A and AA levels of the WCAG 2.1 guidelines.
Solution
We conducted an accessibility test on the website, which helped the client to identify areas where accessibility could be improved.
Goals
Testing
Report
Review
How did we do it
Automation testing delves into the code
In automation testing, we went through each view of the service with the help of an accessibility tool. Using the accessibility tool, we listed observations on factors affecting accessibility, such as font sizes and text contrast. The tool also helped us investigate the structure of the site, meaning the code. By examining the structure, we determined how screen readers and other assistive technologies interpret the page.
Human touch with manual testing
There are many aspects in accessibility, and not all of them can be tested mechanically. To ensure accessibility, we also manually reviewed various parts of the service. We tested the service on different devices, such as phones and computers. We also examined how user-friendly the service is for those who navigate using only a keyboard or only a mouse. Finally, we assessed how the service met the accessibility criteria of the A and AA levels of the WCAG 2.1 guidelines used as the basis for testing, and how compliance with these criteria could be ensured.
What did our customer get
Accessibility test report
In the report, we outlined the four principles of the WCAG guidelines: perceivability, operability, understandability, and robustness. We described to the client the A and AA level criteria included in these principles, along with success criteria, use case examples, and considerations.
To support the written report, we created a visual summary of the website's accessibility observations. The client received images of each tested view, which made it easy to understand the location of programming-related observations and development tasks within the service.
Clear steps towards development work
We reviewed the results of the testing together with the client. After the review the client's development team was able to make the necessary changes to the Yksa archive service. Based on the accessibility testing, the client could ensure a smooth user experience for an increasingly wider target group with the Yksa archive service.
Accessibility test report
In the report, we outlined the four principles of the WCAG guidelines: perceivability, operability, understandability, and robustness. We described to the client the A and AA level criteria included in these principles, along with success criteria, use case examples, and considerations.
To support the written report, we created a visual summary of the website's accessibility observations. The client received images of each tested view, which made it easy to understand the location of programming-related observations and development tasks within the service.
Clear steps towards development work
We reviewed the results of the testing together with the client. After the review the client's development team was able to make the necessary changes to the Yksa archive service. Based on the accessibility testing, the client could ensure a smooth user experience for an increasingly wider target group with the Yksa archive service.
Do you need help with accessibility testing?
Contact us and let's see how we can help your business.
Case accessibility test for Yksa
With Mindhive's accessibility test, we were able to move quicker to the actual development work. The experts at Mindhive helped us understand what we needed to do differently to make our services more accessible. Once the development targets were already mapped out, we no longer had to spend time searching for them, and we could directly engage in productive work within our core expertise.
Kaisa Neuvonen
Account Manager
Disec Oy
Disec offers Yksa archive service, which is a Sähke2-certified archiving system. Yksa is also used by public sector entities, which is why the service is subject to legally defined accessibility requirements. At Disec's request, we conducted an accessibility test on the Yksa archive service, enabling their development team to more effectively implement the necessary changes.
Learn more
Disec.fi
Where did we start
Need
When updating the Yksa archive service, the client needed to ensure equal treatment of all user groups by meeting the accessibility requirements set at the A and AA levels of the WCAG 2.1 guidelines.
Solution
We conducted an accessibility test on the website, which helped the client to identify areas where accessibility could be improved.
Goals
Testing
Report
Review
How did we do it
Automation testing delves into the code
In automation testing, we went through each view of the service with the help of an accessibility tool. Using the accessibility tool, we listed observations on factors affecting accessibility, such as font sizes and text contrast. The tool also helped us investigate the structure of the site, meaning the code. By examining the structure, we determined how screen readers and other assistive technologies interpret the page.
Human touch with manual testing
There are many aspects in accessibility, and not all of them can be tested mechanically. To ensure accessibility, we also manually reviewed various parts of the service. We tested the service on different devices, such as phones and computers. We also examined how user-friendly the service is for those who navigate using only a keyboard or only a mouse. Finally, we assessed how the service met the accessibility criteria of the A and AA levels of the WCAG 2.1 guidelines used as the basis for testing, and how compliance with these criteria could be ensured.
What did our customer get
Accessibility test report
In the report, we outlined the four principles of the WCAG guidelines: perceivability, operability, understandability, and robustness. We described to the client the A and AA level criteria included in these principles, along with success criteria, use case examples, and considerations.
To support the written report, we created a visual summary of the website's accessibility observations. The client received images of each tested view, which made it easy to understand the location of programming-related observations and development tasks within the service.
Clear steps towards development work
We reviewed the results of the testing together with the client. After the review the client's development team was able to make the necessary changes to the Yksa archive service. Based on the accessibility testing, the client could ensure a smooth user experience for an increasingly wider target group with the Yksa archive service.