The best products are designed for everyone, and consider how all users will interact with the product. Many products and digital services are designed without thinking about accessibility. Adding accessibility to a product or service after launch is far more expensive than including it from the start.
I came across this article discussing how to include accessibility in designs to ensure developers and testers know how a product is intended to function. Embedding this into your design processes will improve the quality of the product for all users and reduce costs in the long run.
Apple products are a fine example of designing for everyone. Regardless of the product, there are accessibility options to help make the product accessible - from a screen reader through to switches that allow users with limited mobility to navigate the device. I have written more about this in my Accessibility as Standard article
As we build back ever better, we need to include accessibility in everything we do.
Accessibility is unfortunately still an afterthought on many projects. User interaction and accessibility requirements are poorly documented, at best. Or forgotten, when handing over designs to developer teams. And fixing it later costs a LOT more than building it right to begin with. Great documentation helps teams implement accessibility requirements the right way. I will tell you why, what and how designers can document different aspects of accessibility and user interactions requirements, to build better more inclusive products.