RE: User agent SCs?



> -----Original Message-----
> From: Patrick H. Lauke [mailto:redux@splintered.co.uk]

> Not sure if official of not, but I seem to recall murmurs about the desire to fold
> UAAG requirements into WCAG so that browser devs don't feel they can "get
> away with it" by simply offloading onus on web content authors...

[Jason] Some people (and I think I'm one of them) would prefer WCAG, UAAG and ATAG requirements to be addressed in a single specification. Authoring tools can be implemented as Web applications. Mobile applications can include HTML and JavaScript. The distinctions aren't as sharp today as they once were, thus it can be argued that maintaining separate specifications is no longer appropriate.
>
> It would still be good to see some form of distinction though (so as an author, I
> know what I must do vs what browser devs should be doing)
[Jason] What you need to do depends on what technologies you choose to rely upon. The way in which WCAG has traditionally handled the role of functionality provided by user agents is to specify that a given requirement must be met. If the user agents or assistive technologies address it, then the author need not do so in the content/application; but the content author still has a responsibility for it in cases where the accessibility-supported Web technologies relied upon in writing the content don't address the requirement.
The details of what user agents support change over time and operate below the level of WCAG itself (i.e., at the techniques/implementation guidance level). This is why we have the notion of a set of technologies relied upon to implement WCAG, which must be accessibility-supported, and which change more rapidly than WCAG does.


________________________________

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, 6 July 2016 13:05:05 UTC