Guess who starved their Apple Watch to death during a workout today? That’s right kids, me! So I had to charge it in order to get my last couple of stands and my last two workouts in in order to achieve my 600 points for my Apple Watch competitions. I had most of it knocked out by 10 o’clock this morning though. I will probably do the same thing again tomorrow.
If you’re waiting to add accessibility to your projects until your clients ask and pay for it, please rethink your strategy. Accessibility is not a feature. It is not a nice to have. It’s harder to do when you bolt it on after the fact instead of building it in at the start, and the only thing you’re doing with this approach is creating more work for yourself, more hardship for your clients, and a shitty experience for people with disabilities. Please do not do this. Add as much aas you can by stealth if you have to. If your client asks you for some functionality, build the accessibility in without their permission if necessary. If the eclient balks at accessibility, (this does happen), walk away. I’m telling you to do that because I’ve done it myself. I promise you that if they’re balking at accessibility there’s a pretty safe bet they’ll balk at other best practices too, and then blame you when things go south because best practice corners were cut.