Re: Comment on WCAG-EM, W3C Working Draft 30 January 2014

Apologies for my hasty striking of the send button.  Here is the full
response:

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 in reaching this goal. A sensible
sampling strategy can and should use representative samples of those
document features which contribute to the page. Multiple instances of UI
components that are shared across pages do not need to be tested multiple
times and should be ignored or avoided during the test effort as their
inclusion will not add any new data but will add needless effort.


On Thu, Jan 30, 2014 at 11:08 AM, Karl Groves <karlgroves@gmail.com> wrote:

> 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
>



-- 
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