Search posts, tags, users, and pages
Although accessibility is widely accepted and highly important in the design department at my company, we do have issues getting content writers and especially developers interested and accountable in accessibility. I work at a large org. What have you found that works to get other teams invested in accessibility?
Different approaches for different folks.
However, I have noticed most people who seem to not care about #a11y are just indifferent. In their minds, they're choosing between #a11y and something else that's "more important". To make a change here, you need to demonstrate that it's not a zero-sum game. Accessibility and company/team goals aren't mutually exclusive. e.g I once told my PM that it'll take the same time for me to implement a feature accessibly as it would take to implement inaccessibly. Then, I went on to deliver. Gradually, the team accepted accessibility as a product requirement.
As a teammate, the best way to seek buy-in is to show that it can be done at little or no cost.
In my other answer, I shared how to engage folks and make accessibility a team-wide responsibility, so I hope those insights can be helpful here!
Something that has worked for me is to just start talking about accessibility and asking questions that presume accessibility is a core part of our process. It's not a niche discussion, it's the discussion.
Cultivating a culture of accessibility where it becomes habit is critical, where your teammates feel empowered to contribute and to help, rather than under the careful watchdog.
For writers, I've found tapping into their expertise and usually common desire to want things to be clear.
h tags work, could you label your copy doc?For developers, I've found tapping into their desire for consistency and reuse:
I think it can be helpful to point blank ask people: Do you care about making our product accessible to people? Figuring out that baseline first tends to help.