RE: ACTION-2053: Draft-y language for Accessibility Considerations sections



> -----Original Message-----
> From: LĂ©onie Watson [mailto:tink@tink.uk]

> We should keep in mind that the interface that uses these APIs may not be well
> covered by WCAG (at least at present). Definitely a good idea to point people to
> WCAG, but I'd hesitate to say that accessibility requirements are defined by
> them.
[Jason] If it's implemented at the user agent level then software user interface guidelines would be more relevant (and perhaps a combination of WCAG + WCAG2ICT and UAAG). I wouldn't wish to be prescriptive here, and, admittedly, I haven't looked at UAAG 2.0 (currently a Working Group Note) in any detail.


________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________

Received on Wednesday, 10 August 2016 23:25:50 UTC