v2.x - a step backwards in accessibility
Posted: Thu Nov 12, 2015 5:01 am
Hi all,
Adoption of CMSMS for us, was in large part driven by the promise that the team was working on accessibility. But now that I had my first look at v2.x, I wonder if anyone in the core team read the WCAG prior to building/OK-ing features?
For example: some inputs are drag & drop. Please sit down, disconnect your mouse, and tell me how to use this? Come on folks, this is like the most basic of basics here... This affects people with motor issues, the non-sighted ...
Please note that our core business is building websites that pass inspection. Please note that with the UN treaty in place most western countries have committed to accessible government services and this includes back-office.
We regularly hear about people losing their jobs because due to disability they cannot use the software/CMS anymore.
Get it right, please...
Adoption of CMSMS for us, was in large part driven by the promise that the team was working on accessibility. But now that I had my first look at v2.x, I wonder if anyone in the core team read the WCAG prior to building/OK-ing features?
For example: some inputs are drag & drop. Please sit down, disconnect your mouse, and tell me how to use this? Come on folks, this is like the most basic of basics here... This affects people with motor issues, the non-sighted ...
Please note that our core business is building websites that pass inspection. Please note that with the UN treaty in place most western countries have committed to accessible government services and this includes back-office.
We regularly hear about people losing their jobs because due to disability they cannot use the software/CMS anymore.
Get it right, please...