Many companies just getting started at accessibility focus only on critical bugs and lose momentum and drive to complete fixing the remainder of the bugs. My research testing shows that approach is problematic for two reasons:
One: It is more expensive and time-consuming to go back and reopen code where critical bugs have been fixed. It has to go through full testing and the release process twice
Two: Numerous low and medium priority bugs can drive disabled users away. You must remember that people with disabilities are carrying the lived experience that 96 % of the web doesn’t work for them. If the time it takes for them to go through a workflow is double or triple because there are header or color problems, or issues with poorly drafted error messages, that might drive them away just like a critical error would.
Alt: Black man with sweat dripping down their face with the caption “Don’t sweat the small stuff, ” they said in accessibility, there is no small stuff.