- From: Dylan Barrell <dylanbarrell@gmail.com>
- Date: Wed, 5 Mar 2014 16:14:34 -0500
- To: public-indie-ui-comments@w3.org
- Message-ID: <CAKiJnYtjUYn2ZG0cD3ncvBp3DS528KR1=KouwreC2juqddsnqQ@mail.gmail.com>
I am in favor of the draft wanting to enable the detection of certain assitisve technology software settings and features, however I think that it does not go as far as it needs to to be of ultimate practical use. 5.4.1 Key: screenreader Some platforms have only one viable screen reader (iOS) whereas others have multiple (Windows). It is therefore not only important that a screen reader is running, ut rather which one is running. Also, whereas some operating system versions are closely synced with the screen reader versions (iOS, OS X), other are totally independent (Windows). Therefore it is also important to know which version of the screen reader is running. This key should therefore wither return an easily parseable string representation of the screen reader and version, or it should return a JSON structure with the appropriate information or undefined if not relevant. This brings me to a second critique: What about Voice Recognition and other Assistive Technology software components? I see support for contrast issues, magnification and subtitling (hearing issues) but I see no support at all for the types of assistive technology used by users with physical disabilities. Dragon is one such piece of software. The existence of this sort of technology should also be exposed. This leads me to think that the key should be changed from screenreader to assistivetechnology (or some such equivalent) in order to be more widely usable and applicable. If the return type is a JSON structure then it could include the type of assistive technology with 'screenreader' being one of the applicable types. Furthermore, I would like the committee to consider whether the actual capabilities of the assistive technology should be detectable, rather than the existence of a particular version of the technology. This would certainly require some careful thought to come up with a useful set of features but some food for thought would be to specify for example which ARIA roles are fully supported by the browser/AT combination, which ARIA version is supported. I am still reading through the entire draft and may have more comments later --Dylan
Received on Monday, 10 March 2014 10:23:43 UTC