- From: White, Jason J <jjwhite@ets.org>
- Date: Fri, 12 Aug 2016 13:09:56 +0000
- To: Jonathan Avila <jon.avila@ssbbartgroup.com>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
- Message-ID: <BY2PR0701MB1990F79AA060D8091E223C7CAB1F0@BY2PR0701MB1990.namprd07.prod.outlook.>
From: Jonathan Avila [mailto:jon.avila@ssbbartgroup.com] Sent: Thursday, August 11, 2016 8:47 PM To: w3c-wai-gl@w3.org The challenge we have is that a viewport within a single page may need a different title than another viewport within the same page. For example, some pages use snap to scrolling where different whole screens are loaded when you scroll but it’s all the same document. In mobile apps we have screens and not pages – right now with WCAG to non-web ICT only the app needs a title and there is no requirement for screen titles for each screen of a native mobile app. [Jason] Furthermore, WCAG2ICT is non-normative, and any normative integration of non-Web ICT would be outside the scope of WCAG 2.1, but within the scope of whatever major revision follows it. I think the issue you raise here affects the conformance scheme quite fundamentally, since it seems to demand a unit of conformance other than a “Web page” as currently defined. Similarly, the concerns I expressed yesterday may turn out to require revision of conformance-related concepts (unless they’re addressed already somewhere). ________________________________ 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 Friday, 12 August 2016 13:10:28 UTC