Accessibility requirements belong in initial product planning alongside functional needs and regional constraints. They shape design from the start and help people use a product effectively, efficiently, and with satisfaction. section 1.2
Requirements can address both legal obligations and ways people perceive content:
- Account for applicable standards and laws, which vary with where users live and the technologies being offered. section 1.3.3
- Specify needs such as sufficient contrast, not relying on color alone, and making images, audio, and video accessible. section 3.0
Appointment booking
When gathering requirements for a public healthcare appointment-booking system, include accessibility from the outset rather than treating it as a later fix. section 1.2
Figure 1.1 Accessibility affects nearly every aspect of software development, from planning and design to post-launch content management and support. Everyone has a responsibility to ensure users can actually access content and functionality.
Accessibility affects planning, design, development, and post-launch support—not just implementation. section 1.2
