UAAG2 Action: to turn security paragraph in overview into a proposed note for the programmatic access GL

http://www.w3.org/2013/07/11-ua-minutes.html#action04

PROPOSAL: Put the following text under GL 4.1. Perhaps in the summary (if we keep summaries):
http://www.w3.org/WAI/UA/2013/ED-UAAG20-20130628/#gl-AT-access

Note: Some approaches to implementing success criteria in this guideline, and elsewhere in UAAG 2.0, may have security implications. It is the responsibility of UAAG 2.0 implementers to ensure that user agent security is not compromised.

---

CURRENT text is here: http://www.w3.org/WAI/UA/2013/ED-UAAG20-20130628/#conceptual_overview
"Some UAAG 2.0 requirements may have security implications, such as communicating through Application Program Interfaces (API), or allowing programmatic read and write access to content and user interface control. UAAG 2.0 assumes that features required by UAAG 2.0 will be built on top of an underlying security architecture."


(MR) JAN RICHARDS
PROJECT MANAGER
INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)
OCAD UNIVERSITY

T 416 977 6000 x3957
F 416 977 9844
E jrichards@ocadu.ca

Received on Thursday, 11 July 2013 19:26:06 UTC