Unless you have a legal requirement to provide accessibility, I encourage everyone to ignore this advice. It is basically letting perfect be the enemy of good. Especially if your project is opensource. Someone that cares, which may even be you at a later date when other things on the to-do list are done, can submit patches to address accessibility later.
Brace yourself: the "European accessibility act" will soon make accessibility a legal requirement to the private sector, including computers, operating systems, smartphones, and e-commerce.
Have your popcorn ready to watch how this will freak out plenty of big corporations, rushing to fix their products, services, and websites from their accessibility "short-sightedness" of times past.
Depending on circumstances, failing to comply may cause heavy fines and having the product removed from market.
I just read it and the requirement for computers applies to hardware and operating systems. Ecommerce sites are covered but website and mobile app requirements beyond that apply to communication, transportation and public sector systems. The vast majority of private sector systems will still not have a legal accessibility requirement.
> ... can submit patches to address accessibility later.
I'm not experienced with accessibility, but I pay attention to it whenever I can to increase my own awareness. A very common feedback when it fails (e.g. in software, online conferences, ...) is: "Accessibility must be part of the plan from early on. Trying to add it afterwards basically always fails."
