Last year, we decided to redevelop Rider Spoke from scratch (the first version was made before smartphones existed). This also gave us a chance to improve accessibility for our audiences – which was challenging with a software-led project for cyclists who ride alone, often at night, on public roads.
We’ve now published a new resource using the Rider Spoke accessibility testing process as a case study. In the document, we explain how we approach software testing; what additional tests we carried out for accessibility; what went well; and what we learnt. If you’re working in a similar area, we hope you’ll find it useful.
In our experience accessibility requires time, resources and significant thought. We’ve found that there are always limits to what we can offer to those with access needs. But the work we have done is richly rewarding and we have seen immediate improvements in removing barriers to participation.
If you create software projects, artworks or services and want to reduce barriers for people with restricted mobility, hearing or vision, this resource is for you. We hope it will help you move more quickly and get more done – and we’d love to hear what you think.
Download the resource here (PDF).
Download a large print version here (Word).