In many western countries it is a legal requirement to have an accessible site. Not just public ones either - internal-only sites still need to be accessible i

In many western countries it is a legal requirement to have an accessible site. Not just public ones either - internal-only sites still need to be accessible in many countries since internal users need to do their jobs too. Have your customers "asked" for the code to not be awful, or for there not to be security issues, or for it to be performant and so on? They're all kinda "implicit" non-functional requirements in my mind. We make the code non-shit and performant just as part of our job without anyone asking, and a11y is probably something we should do by default too. It is very easy to make some absolute show-stopping errors with accessibility if you are not developing with it in mind, but luckily there is a lot of good free tooling that will catch 80-90% of the issues. The Chrome Dev tools, OS-built-in screen readers, aXe for automated testing, and some very basic knowledge will get you a lot of the way (e.g. chrome dev tools accessibility tree view is awesome), but there will be some bits that require hands-on knowledge and engineering to implement/test/fix - e.g. making a table keyboard accessible is "trivial" from a technical perspective, but it might still be an awful experience for the users if you don't give it some care and thought (e.g. do you need to make every cell navigable via keyboard, or can you just do perhaps each row...? It really depends on your use case and that is where it gets harder of course!) I'd recommend trying to use a screen reader from time to time. If you are used to seeing a page then it is a total culture-shock and feels totally impossible . However persevere and try to put your self I to the mindset of listening to a podcast/radio show or simply reading a fiction book etc and you'll slowly get the hang of it. Start slow and don't expect to be as fast as you are used to being when visually reading/scanning a page. Some.of the fundamentals and errors I see so so so frequently: - make sure the DOM is in a logical order (i.e. elements nested correctly and in a logical order - don't use CSS or JavaScript to move things around visually ... Elements should follow each other in the DOM logically) - use HTML semantics properly - use <button> not <div class=button>, use <a> not <div onclick=navigate(foo)>, use <h1> not <div class=heading> etc etc etc. This is so common. - use sensible labels - check color contrast is sensible. Just those few things will take you a long way to at least making your page comprehensible for assistive technology users, even if there are a few other rough edges elsewhere Good luck.