Product teams are usually made up people with two different mindsets.
On the one hand, you have people who are set on avoiding problems.
These are typically those who approach web accessibility like a potential minefield. They see accessibility as a series of potential legal and ethical pitfalls they need to avoid.
They are hyper-focused on what could go wrong. They'll meticulously review the WCAG, run extensive screen reader tests and create checklists to make sure no one overlooks an accessibility requirement. Their approach is defensive. They want to prevent any potential barriers that might exclude people with disabilities.
On the other hand, you have people who want to solve problems.
These are the innovation-driven team members who see web accessibility as an exciting challenge. They're not just avoiding issues. They're actively excited about creating inclusive experiences that work for everyone.
For them, accessibility isn't a compliance checkbox. They get energized by finding creative solutions that make the product experience better for everyone. They'll prototype new interaction models, develop adaptive interfaces and look for ways technology can bridge the gaps.
It's fine. Both are needed and I've yet to see a team where only one mindset is present.
Problems only arise when you don't know who you're talking to.
It's one thing to ask "What if a user can't use a mouse?" to a person who wants to avoid the problem and another to ask "How might we design this so it's not just keyboard-accessible, but actually delightful for everyone?" to someone who wants to solve the problem.