Raising mobile accessibility from 38 to 90 on Screwfix France

Screwfix France scored 38 for mobile accessibility. We took it to around 90, working inside the client’s own release cycle so the fixes stopped being undone.

Diagram: accessibility fixes removed by parallel releases, then re-sequenced so fixes are applied at pre-UAT

The work

Screwfix, part of Kingfisher plc, asked us to review and improve accessibility on the mobile version of screwfix.fr. We worked directly with their team in the UK.

The site scored 38 for accessibility in Google PageSpeed Insights when we started. It finished at around 90.

What made it difficult

Screwfix had their own development team releasing updates to the same site while we were implementing ours.

At some point we found that changes we had already implemented were no longer there. They were being removed as the other team’s releases went out.

What we did about it

We proposed a change to the development flow rather than a technical workaround.

We asked to be included in the project’s own update cycle. The Screwfix team’s changes would land first, and we would implement ours on top of theirs at the pre-UAT stage, so what went into user acceptance testing already contained both.

That change mattered more than any individual fix did.

One qualification

A PageSpeed accessibility score is generated by automated testing and does not certify that a site is accessible. It covers a defined subset of issues. What a move from 38 to 90 tells you is that the structural failures were found and closed.

We hold our own site to the same standard. unomage.com scores 100 for accessibility in the same tool, and anyone is welcome to run the check.

Have a similar challenge?

[email protected]