You're at odds with the UX/UI team on web app accessibility. How do you find common ground?

Simply put: 1. Accessible Design Principles: Advocate for accessibility as a core design principle, not an afterthought. 2. User Research: Leverage real user feedback to demonstrate the impact of accessibility on diverse users. 3. Educate & Collaborate: Offer workshops or resources to bridge knowledge gaps and foster collaboration. 4. Prototype & Test: Create accessible prototypes and test with users to showcase practical benefits. 5. Compromise Solutions: Find middle ground with design tweaks that enhance accessibility without compromising aesthetics.

As a person who takes care of accessibility changes on a daily basis for our product I can totally understand. Firstly, I will appreciate the stunning UI that team has developed and how they have made sure that it is user friendly and easily understandable. But since our user base is not just common people but also people with disability so I would just ask them a doubt on how a visually impaired person can experience the same understandability just like any normal one, how would they interact with limited to no vision. I would make sure that they could get what my intention behind those questions are and help them to start thinking on a more broder perspective which in turn helps the bussiness as well.

Accessibility and User experience go hand in hand, even an accessible website will be looked down upon if it is not visually appealing. You must acknowledge that their design goals are extremely important and promote the App's image.

Finding common ground with the UX/UI team on web app accessibility starts with empathy. Understand their perspective and the challenges they face in balancing design aesthetics with accessibility requirements. By putting yourself in their shoes, you can better appreciate their concerns about maintaining visual appeal while ensuring accessibility. For example, they might worry that adding screen reader support could clutter the design. Acknowledging these concerns fosters a more respectful dialogue, laying the foundation for a collaborative approach to resolving differences.

Where possible, try to have testers with specific accessibility requirements give feedback from time to time. However, no matter who gives the feedback, it is a learning experience rather than an indication that you are doing something wrong and be open to discussion. For those giving feedback, also try to give positive feedback. It is easy to focus on what needs improvement rather than what to keep, so certain useful features can sometimes be lost. I've also seen people get demotivated when they only receive negative feedback because they don't realise just how much they have done right.

Educate together by sharing knowledge about accessibility and its impact on users. Organize joint learning sessions where both teams explore the importance of accessibility, from legal obligations to the ethical imperative of inclusivity. For instance, reviewing case studies of users who benefit from accessible design can bridge the knowledge gap and create a mutual understanding. When both teams have a shared knowledge base, it's easier to align on the necessity of incorporating accessibility without compromising on design quality.

I'd organise informal (in the pub), collaborative learning sessions where we explore accessibility together. We could focus on users with disabilities to share their experiences, making the topic more relatable. I'd demonstrate how accessibility features often improve usability for everyone, not just those with disabilities. For example, we could explore how clear, high-contrast designs benefit users in bright sunlight or how keyboard navigation helps power users. By learning together, we'd build a shared understanding and appreciation for accessible design.

We can have information and we can also have knowledge. While there is no single individual that knows every single detail a distillation and cross sharing of knowledge will help us fill the gaps we might all have. We all get to have different perspectives and experiences one may never have. This is why education can be a two way street given our collective knowledge.

Collaborate creatively by involving the UX/UI team in brainstorming sessions to find innovative solutions that satisfy both design and accessibility needs. Encourage thinking outside the box to integrate accessibility features seamlessly into the design. For example, rather than removing visual elements, work together to ensure that color contrasts meet accessibility standards without sacrificing aesthetics. This collaborative approach not only fosters creativity but also helps both teams feel invested in the final product.

To align design and accessibility, focus on improving user experience and achieving business goals by adopting WCAG standards and tracking success with clear metrics. Collaborate on inclusive design principles, set a joint timeline with defined roles, communicate regularly, celebrate successes, and remain adaptable to evolving needs and feedback.

Setting shared goals is crucial in finding common ground. Define clear, mutual objectives that prioritize both user experience and accessibility. For example, agree that the web app should be fully navigable by keyboard for users with mobility impairments, while also maintaining a visually engaging interface. When both teams are aligned on these goals, it reduces friction and ensures that everyone is working toward the same end result, making it easier to resolve disputes and keep the project on track.

If I were at odds with the UX/UI team about web app accessibility, I would focus on finding common ground by setting shared goals. I’d start by organizing a meeting to discuss the importance of accessibility and how it aligns with our team's objectives. I would emphasize how accessible design can improve user experience and broaden our audience, showing how it benefits everyone involved. Then, I’d work with the team to define clear goals and outcomes for the project, ensuring that everyone is on the same page about the accessibility standards we want to achieve. By fostering an environment of open communication and encouraging regular feedback, I would aim to keep the team aligned and committed to creating a more inclusive web app.

Compromise wisely by finding solutions that balance design preferences with accessibility needs without significantly compromising either. For example, if the UX/UI team is concerned about the impact of large text on visual design, suggest adjustable font sizes that allow users to control their experience. This kind of compromise respects the design vision while still adhering to accessibility standards, ensuring that the final product meets the needs of all users.

Reflect and adjust by regularly reviewing the implemented solutions and gathering feedback from users, especially those with accessibility needs. For example, after launch, collect user data to see if the accessibility features are being used effectively or if they need tweaking. This ongoing reflection allows both teams to learn from the process and make necessary adjustments, ensuring that future projects benefit from the lessons learned and that the web app continues to serve all users effectively.