If not being needed is the best part of web accessibility, then what might be the worst part?
Without a doubt, for me, it's being the last person in the room to sign off before shipping.
I hate finding out a feature is "done" the same week it ships. That's when designs are signed off, the code is merged and the tickets are all closed. Obviously, somewhere in that process, nobody thought to loop me in and accessibility was not included in this definition of done.
So now I'm not doing accessibility any more and instead running around doing damage control as best I can.
Reworking features is hard. Having to tell people they have to go back and do that is absolutely brutal. At this point, the best we can do is patch things up. And half the time the patch is a compromise because the right answer would mean pulling the whole thing apart.
The worst part is knowing it didn't have to be this way. I don't mind the work at all. But I'd like to avoid it.
So tag me in at the start. I promise I'm easier to work with when I'm not already behind.