Mike Thomas
Product Design Lead
London

A11y

Designing an approach to get to AA accessibility

6 min read

What

Over a 6 month period, I worked both individually, and as part of a small cross-functional team to audit and improve Piclo's flagship SaaS app, Piclo Flex, with the goal being to achieve 'AA' accessibility standards across the whole app, aligned to WCAG 2.1 accessibility guidelines.

Why

At Piclo, we hadn't yet formalised our approach to designing accessible digital services, and we didn't know how well we were doing (or not doing) across our ecosystem of customer touchpoints.

In addition, Piclo's SaaS product and business services were being procured by a UK public sector organisation. A key requirement of this process asked that we commit to ensuring our web app adhered to accessibility standards, which we did.

This hard requirement acted as a catalyst to our desire to find out, see where we were falling short, and make improvements.

Role

My contributions

Asking questions and identifying work themes

When considering this work initially, the team hadn't yet been fully formed, and so I chose to start by noting all of the questions I had.

Sticky notes on a Miro board grouped into four clusters: Defining scope, Measuring, Thinking strategically, and Organising. Each is surrounded by questions such as 'What are the WCAG 2.1 guidelines?' and 'How will we prioritise what to do first?'
Initial brain-dump of questions.

This proved valuable, as it helped to lay some ground-work ahead of others joining the project by providing loose structure.

From the above, I was able to work with incoming colleagues to arrive at the following rough project structure.

We'd spend a short period (not to scale below) figuring some things out based on our initial questions, then we'd move into a phase where we'd be both auditing and delivering solutions in parallel.

Timeline split into Discovery and Delivery tracks. Discovery: 1, build initial knowledge and expertise; 2, evaluate tools and testing methods; 3, audit the application and gather evidence. Delivery overlaps the audit: 4, prioritising, sequencing and executing the work.
Thinking in dual tracks helped us move faster.

Defining some strategic principles

Alongside the above, I spent some time discussing the potential impact of the project with colleagues from across other Product teams to sound out any concerns and see who had some experience already.

From those conversations, as well as taking inspiration from several webinars and other sources of information, I wrote out some draft principles that would help guide our thinking.

Principle Description
Everyone is responsible We didn't want to fall into the trap of making accessibility the problem of one specific team, we wanted the whole business to be pulling in the right direction.
Embedded Accessibility isn't just something to test for at the end of the process before shipping, it should be embedded end to end in how we design solutions for users.
Continuous Accessibility isn't something we stop thinking about when some target is met. Good standards, once achieved, need to be maintained and carried forward as our software and services evolve.
Non-disruptive Achieving and maintaining standards will require extra effort, but we aim to minimise the impact on other teams who are focussed on other problems.
Imperative Contractual obligations aside, poor accessibility standards are, in our case, bad for users, bad for business, and bad for the planet.

Organising the work

I made the choice early in the project to create a simple way to keep track of everything we were doing. I chose to use Google Sheets for this work, and my goal was to promote visibility of progress, transparency of process and provide links to any production tickets or other relevant materials.

This also proved to be a great resource to help onboard colleagues who joined the team, whether they were engineers or product managers.

The following details some things I included to help us stay organised.

Google Sheet audit checklist listing each page URL with columns for customer type and pass or fail results from Lighthouse, Axe, WAVE, keyboard and screen reader tests. Annotations highlight 'Who is affected?' and 'Link to scoped tickets'.
Keeping track of what we've tested, how, and cross-referencing with related issues.

This resource evolved over time as our process improved and we added more tooling and built our own knowledge.

Google Sheet issue log listing each accessibility issue by view, with columns for nature of issue, scope and detection method. Annotations highlight 'Succinct issue description', 'Scope/impact of the issue' and 'Do we need more discovery?'
Triaging issues for every digital touchpoint (with a unique URL) and deciding what to do next.

I also included a transcription of important WCAG 2.1 guidelines that were relevant to us, so colleagues could remain within the sheet when referencing things if needed.

Google Sheet tab transcribing WCAG 2.1 AA success criteria, starting with 1.1.1 Non-text Content, next to an empty column annotated 'Space to write up how we intend to test'.
This also allowed us to document how we intended to test for each section.

As you can see from the empty cell highlighted above, this last sheet wasn't entirely successful, as we documented our testing methodology elsewhere in the end.

Standardising ideation for efficiency

We used Miro as a place to gather visual evidence accumulated during our audit. I chose to create repeatable ideation canvases we could 'fill in the blanks' on to smoothly move through each issue consistently.

Miro audit canvas with four areas: screenshots of a login journey on phone, tablet and desktop; an audit space holding Lighthouse, Axe and WAVE reports; sticky notes of issues discovered; and a prioritisation matrix.
Auditing journeys, identifying issues and prioritising.

I created two types of canvas. One for looking across journeys in a more visual way, where we could log issues and attach our own notes and commentary as needed.

Secondly, I created a lower-level version that helped us focus on individual issues and ideate on solutions.

My aim was to make it as easy as possible for the team to fly through the work as smoothly as possible, with a good baseline of thought and time being afforded to each issue discovered.

Miro canvas for a single issue, 'No page regions are defined', with sections for evidence from WAVE and Axe, a proposed solution annotated on a login screen wireframe, open questions, and a link to the relevant WCAG criterion.
Drilling down into specific issues.

Codifying what good looks like

Towards the end of the project, we had built high confidence in our domain knowledge and working practices. Referring back to several of the principles highlighted earlier, I wanted to use part of our remaining time to decentralise that knowledge and onboard other teams.

To aid this process, I created a series of slides that walked teams through everything we had learned.

Slides from an A11y Guide deck for Piclo, with the 'What is accessibility / a11y?' slide circled. It explains that accessibility means making services usable by the widest possible audience, and that accessibility is broader than disability.
Assuming no prior knowledge, getting everyone aligned from the outset.
Slides titled 'Standards we are aiming for' and 'When to think about a11y'. The second maps accessibility questions onto each stage of the Double Diamond: Discover, Define, Develop and Deliver.
Discussing standards and highlighting where and how we might think about accessibility.
Slide titled 'Holistic AC for a new View' listing accessibility acceptance criteria, including a Lighthouse accessibility score of 100, zero WAVE and Axe errors, full keyboard access, logical tab order, landmark regions and visible focus states.
Setting a clear standard with acceptance criteria for product teams to use when working on new features.

Lastly, I needed to write up an accessibility statement. I conducted a short analysis of what other businesses were doing in this space to identify good practice and align with our own business needs. The latest version of this can be seen live here.

Zoomed-out Miro board comparing accessibility statements from several other organisations side by side, with annotated sticky notes and a summary column of takeaways.
One size fits one. Identifying good practice for writing an accessibility statement.

Wrap-up

What worked

Questions for the future

Reflections

Notes for hiring managers

Thank you 🙏

Please note that all product screenshots and images of Figma, Miro, or other cloud-based work spaces are © Open Utility Ltd.