Old people (that have by sheer math of accumulation) a lot of patrimonial tends to be visually more impaired than average. That is the data you need to make a c

Old people (that have by sheer math of accumulation) a lot of patrimonial tends to be visually more impaired than average. That is the data you need to make a correct understatement marketing assessment of the lost ROI. Look at the age of MPs, owners, people with responsibilities. Look at the stats, they tend to be way older than the coders. Just doing «accessible» or at least «high contrast/big lettering/simple UX» websites just highers the probability of getting new «high profile» customers click from your home page to your «purchase» page and transform from suspect to customers... And, chances are persons without disabilities prefers simple ergonomic websites, and that it will cut on your operational expenses (sites that are accessible tends to use fewer CSS and less JS). It will also make you cut on the REST API bullshit crap, because GET/POST on accessible web pages tends to be easier to do than REST/XML.RPC/SOAP. You can also throw another overpromising/underdelivering JS framework and a lot of money at the problem, but I guess it will have less results than firing half of your devs, that if they have to deliver fast and correctly will automatically resort to do Keep It Simple Stupid kind of webpages, that are actually a good recipe for accessibility.