- From: Karl Groves <karlgroves@gmail.com>
- Date: Thu, 30 Jan 2014 11:08:59 -0500
- To: public-wai-evaltf@w3.org
- Message-ID: <CABScKPCV8dtbbBS_a9DypTaKbCYSozyz2hD2SjBE9PO8u6rMjQ@mail.gmail.com>
WCAG-EM contains the statement, "Methodology Requirement 4.a: Check that each full page (web page and web page state) in the selected sample satisfies each of the WCAG 2.0 Success Criteria of the target conformance level." This statement and supporting material make it appear as though an *entire* web page must be tested in its entirety in order to satisfy the requirements. This ignores the fact that websites composed of a series of static pages is the exception, rather than the rule. The vast majority of websites these days are presented through the use of some server-side means to generate the final interface - from basic SSI to template systems, to complex web applications being generated from content management systems and everything in between. In some cases the server-side generation merely wraps content in a global wrapper while in others the server-side code merges data and markup as part of a template. This methodology seems to ignore that fact and may mislead the reader into believing that the final rendered web page(s) must be tested in their entirety. This risks requiring the tester to perform needless duplicate work. While the goal is and should remain a full page that is accessible, the testing of the entire page is unnecessary -- Karl Groves www.karlgroves.com @karlgroves http://www.linkedin.com/in/karlgroves Phone: +1 410.541.6829 www.botsmasher.com www.a11ybuzz.com www.mothereffingtoolconfuser.com Day One Wordpress Theme: https://bitbucket.org/karlgroves/day-one-theme
Received on Thursday, 30 January 2014 16:40:47 UTC