While helping create the Cloud Computing Code of Practice alongside the New Zealand Computer Society, I was approached by Kevin Prince who is the Manager of Innovation and Development working within the Access, Innovation & Enterprise unit of the Royal New Zealand Foundation of the Blind. The RNZFB, as the name implies, is an organization that advocate for the rights of the visually impaired, and as would be expected, technology falls into its area of concern.
Prince wanted to give me some insight into a submission he’d made to the Code of Practice. Now I have to admit that when talking around the areas of concern for the CoP, not much (if any) thought was given to the issues that impaired people face when using cloud. In fact the decision was made during the consultation process that universal design and accessibility issues should in fact be outside the scope of the document. That was a necessary, if unfortunate decision as the drive was to come up with a readily consumable document that vendors could relatively easily comply with.
That said, Prince is justified in his assertion that accessibility is in fact an issue that falls under compliance rather than design. I met with Prince who ran through the issues that visually impaired users had with technology in general, and cloud solutions in particular. He pointed out that there is no technical reason for modern products to fail in universal design and asserted that exclusion from the code would give the issue the appearance of a ‘nice to have’ rather than an integral part of professional software engineering.
Prince shared with me the RNZFB submission to the code and I’ve copied excerpts of it below. I’d be interested to hear other people’s thoughts around accessibility issues specifically related to cloud solutions.
…the main area of concern will be the clients of SaaS although it should be borne in mind that blind and partially sighted IT Professionals work on backroom functions so PAAS and IAAS providers should not ignore accessibility.
While scripting can address some issues after the fact it is not ideal in that the user of the software is not in control of the upgrade path and what works today could be useless tomorrow by something as simple as a change of graphic or the order of objects on a page. This is not the case with non-cloud software as the owner can test and then schedule upgrades to address the issue.
It is perhaps easiest to demonstrate that accessibility has relevance beyond design by looking at some recent case studies. These will be found in the appendix below.
Appendix 1- Case Studies.
1. Inconsistent user interface.
Office 365 seemingly offers a seamless environment for the sharing of documentation across devices and organisations, however, a key principle of user interface design is consistency. See below the effect on a keyboard user of stepping between client and cloud versions of Word. In the graphics we show the effect of choosing <Alt F> to select the ‘save as’ dialogue.
On pressing ALT + F the file menu opens and I can use first letter navigation to find save. This will save a local html copy of the page.
On pressing ALT + F the file menu opens and I can use first letter navigation to find save. This will save a local word copy of the document.
Blind users rely on consistent navigation to carry out tasks efficiently. They do not see the visual clues that would be obvious to an IT professional here. The same applies to non-technical users – the confusion caused by having two inconsistent ways to access the same task should not be underestimated – discussion of one being on the cloud and ‘in a browser’ is not generally understood.