W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > June 2007

Requirement for \'7.) Full Pages\' may be too narrow

From: WCAG 2.0 Comment Form <nobody@w3.org>
Date: Fri, 29 Jun 2007 22:16:59 +0000 (GMT)
To: public-comments-wcag20@w3.org
Message-Id: <20070629221659.7746F3320A@kearny.w3.org>


Name: Peter Wallack
Email: peter.wallack@oracle.com
Affiliation: Oracle
Document: W2
Item Number: Conformance Requirements
Part of Item: 
Comment Type: technical
Summary of Issue: Requirement for \'7.) Full Pages\' may be too narrow
Comment (Including rationale for any proposed change):
With the move to Web 2.0, it is possible that a \'single\' web page is re-used to render vastly different content, which previously might have been presented as individual pages. In an extreme case, one can imagine an entire application suite rendering in a single \'web page\', such that a browser \'Back\' takes them completely out of the application. In such a case, if a single piece of content were not accessible, as currently worded the entire application would not be able to claim conformance.

Proposed Change:
We suggest that the wording be broadened so that exceptions within a \'page\', when using such dynamic content, can be specifically listed.  Or alternatively, the definition of \'web page\' be broadened to account for dynamic content on the screen.
Received on Friday, 29 June 2007 22:17:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:08 UTC