Sometimes we're in such a hurry to get things done, we don't pause to ask the right questions.
- How do I add ARIA labels?
- How do I add the right role to this
div? - How do I add
alttext to this image? - How do I make this keyboard-accessible?
Don't start with the how. The how follows logically. The how has, a lot of the times, a technical answer.
Instead, start with the what.
- What is the purpose of web accessibility?
- What are the principles of the WCAG?
- What types of users am I neglecting?
After you answer that, continue with the why.
- Why is it important to make my product accessible?
- Why does the WCAG matter?
- Why is it important to understand the diverse needs of users with disabilities?
Understand the "why" behind accessibility. This will motivate the "how" of implementing it. With the "what" and the "why," you'll have the necessary context and motivation to properly implement the "how." The "how" is important, but you need a deeper understanding of accessibility goals and best practices to answer it.
Don't start with the how, when you're missing the what and the why.