top of page
Solirius Reply - LOGO RGB.png

Insights

7 lessons on integrating accessibility feedback into the design process

Aaron Grey
3 days ago
6 min read

Accessibility specialists are often brought into delivery phases when working code is ready to test. Ongoing testing and assurance are essential, but decisions about content, interactions and user journeys can be harder and more costly to change once implemented.


Shifting accessibility input upstream gives delivery teams more opportunities to address accessibility risks while designs are malleable. Moving from reactive audits towards active collaboration with user-centred design (UCD) teams builds stronger foundations early. 


Collaboration is not always built into a team's routine ways of working. These seven lessons share practical ways to integrate specialist feedback into early design stages. 



1. Distinguish accessibility risk from confirmed WCAG failures


A wireframe, a coded prototype and a live service offer different levels of evidence. Accessibility feedback is most useful when it clearly explains what can be assessed at each stage.


Some concerns can be assessed before development begins. For example, if a wireframe specifies text and background colours, teams can measure whether that combination meets the required colour contrast ratio.

 

However, a dense layout that has not been explored at smaller screen sizes may suggest a potential barrier. It is a risk for people who magnify content, rather than a confirmed failure against the Web Content Accessibility Guidelines (WCAG).


Accessibility audits test code against defined conformance requirements and report binary pass or fail findings. Early designs, however, are more exploratory: a static wireframe or coded prototype may capture a snapshot of work that is still evolving, rather than a settled design direction. 


Describing a potential barrier as a risk to explore gives teams an opportunity to investigate and iterate early. Where a WCAG failure can be confirmed from a static design alone, this should still be clearly communicated and supported by evidence.


Useful feedback surfaces risks early and separates what can be verified from what needs further testing in production code. It highlights who may be affected by a design direction and what the team should explore next. 



2. Explore suggested solutions collaboratively


Early accessibility reviews can identify potential barriers without necessarily identifying the best way to resolve them.


Designers and user researchers bring valuable context from previous research, service constraints and decisions made across the wider user journey. Recommending a single fix before discussing this context can overlook important evidence or rule out alternative accessible approaches. 


When accessibility specialists, designers and developers explore a barrier together, they can: 

  • agree on the practical impact of the issue

  • consider different solutions

  • decide how to test them


Accessibility advice becomes part of a shared design direction rather than an external change request raised late in delivery. If a solution requires further work, teams can make space for it during sprint planning.



3. Target the origin of an accessibility barrier


Accessibility is a shared team responsibility, but this can sometimes leave ownership of individual issues unclear.


Reviewing designs together makes it easier to identify where a barrier originates and agree on who should lead its resolution. Different barriers might require different skill sets:

  • unclear instructions need input from a content designer

  • confusing interactions require further design exploration

  • inaccessible document journeys will require changes across the wider service

  • keyboard focus issues require a developer to investigate code behaviour


Responsibilities can overlap in practice, particularly with accessible names and labels, error messages and dynamic interactions. For example, where a GDS Check your answers pattern contains several links labelled ‘Change’:

  • a content designer might clarify and annotate the wording required for the hidden text 

  • an interaction designer could review how the repeated links relate to the surrounding visual content

  • a developer could then ensure each link has the agreed hidden text in place in code


Rather than agreeing only on a code fix, teams can ask, ‘Where does this barrier originate, and whose expertise on the team do we need to resolve it?’ This brings the right people into the discussion and reduces the risk of a later workaround that addresses only the symptom of a larger problem.



4. Always investigate beyond published design system guidance


Public sector design systems offer reusable components, patterns and guidance that help teams avoid solving common accessibility problems from scratch.


However, using a design system component does not guarantee accessibility in every context. For example, a table might follow the established GOV.UK Design System pattern. If a team adds too many columns or actions, it can become difficult to navigate at higher zoom levels. In this case, the issue is how the component is used in practice. 


Published design system guidance continues to evolve as new accessibility concerns emerge. The GOV.UK Design System's Details component, for example, includes a section on research highlighting potential difficulties for people using voice control software. It also links to GitHub discussions where teams can share findings and raise concerns with design system maintainers.

Published documentation is a starting point rather than the final word. Teams can:

  • follow discussions across government community channels

  • share findings directly with design system maintainers

  • test patterns in the context of their own service


Research findings, implementation issues and accessibility testing results can all strengthen this shared community knowledge base. Sharing what a team learns beyond its own project can help improve established patterns for the whole public sector design community.



5. Experience accessibility barriers in action


A design review or audit report may accurately describe an assistive technology barrier. However, words alone rarely convey the actual friction someone experiences when using the service.  


Rather than only describing an issue, experience it in action:

  • observe what happens when keyboard focus is lost

  • listen to what a confusing screen reader announcement sounds like

  • explore how a straightforward wireframe becomes difficult to navigate once built in code


Invite colleagues unfamiliar with accessibility tools to try assistive technology with guidance from a specialist. This builds empathy and provides a shared experience to discuss when the impact of a barrier is difficult to communicate.

 

Specialist demonstrations should not replace research with people who use assistive technology in everyday life. Teams should work with user researchers and participants with lived experience to understand the complete user journey. 



6. Keep accessibility conversations ongoing throughout delivery


Feedback should not begin and end with a single review or audit. Designs evolve and new constraints emerge during development. Ongoing conversations help teams act on advice while decisions are still flexible.


This can be as simple as discussing an interaction, joining a design critique, commenting directly on a design file or clarifying an accessibility requirement before development. These smaller activities should complement rather than replace formal reviews.


Earlier input also gives teams more options. A concern raised in a design critique might be resolved quickly by trying another interaction pattern. The same change could be harder to accommodate once the interface has been signed off, built, and integrated into a live service. 


Accessibility specialist time and access is often limited, so teams should agree which decisions and milestones would benefit most from early input. A few targeted discussions can be much more useful than waiting for one late-stage audit.



7. Build confidence, not dependency


Close collaboration should strengthen the whole team. It should not turn an accessibility specialist into a sign-off gate for every design decision.


Accessibility should form part of every designer's practice, but we should not expect every designer to have the same depth of knowledge as an accessibility specialist.


Sharing examples, demonstrating assistive technology and explaining the reasoning behind recommendations can help design teams recognise common risks themselves. They can then make more informed decisions and know when to seek specialist advice or additional testing.



Why earlier collaboration matters

Accessibility audits and ongoing testing of live services remain essential. However, a service can meet technical requirements and still be difficult to use. Meeting WCAG success criteria alone does not guarantee that everyone can understand a journey or complete a task.


Regular conversations between specialists and design teams connect formal assurance with earlier design decisions. Discussing risks, exploring solutions together, and sharing knowledge openly makes accessibility an ongoing consideration across all delivery phases.


This approach will not prevent every issue from reaching a final code audit. It does, however, give teams more opportunities to address barriers while designs can still change, creating inclusive digital services that work better for everyone.



About the author

This article was written by Aaron Grey, Accessibility & UX Consultant at Solirius Reply.



Contact information

Want to bring accessibility expertise earlier into your design lifecycle, or need help reviewing your digital services? Get in touch.

 
 
 

Comments


bottom of page