W3C home > Mailing lists > Public > public-wai-evaltf@w3.org > August 2012

Fwd: Re: comments on WCAG Methodology

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Mon, 27 Aug 2012 20:38:23 +0200
Message-ID: <503BBE9F.3040106@w3.org>
To: Eval TF <public-wai-evaltf@w3.org>
CC: Eric Velleman <E.Velleman@bartimeus.nl>, Jeanne Spellman <jeanne@w3.org>, Bruce Bailey <Bailey@Access-Board.gov>
Dear Eval TF,

Please see message below in response to WCAG WG comment #13:
  - <http://www.w3.org/WAI/ER/conformance/comments-20120730-WCAG#c13>

Regards,
   Shadi

-------- Original Message --------
Subject: Re: comments on WCAG Methodology
Date: Mon, 27 Aug 2012 09:29:15 -0400
From: Jeanne Spellman <jeanne@w3.org>
To: Shadi Abou-Zahra <shadi@w3.org>

[...]

I looked at the ATAG definitions, which aren't particularly helpful,
because they are serving a different purpose.  But in case they are
useful, here they are:

templates
     Content patterns that are filled in by authors or the authoring
tool to produce content for end users (e.g., document templates, content 
management templates, presentation themes). Often templates will 
pre-specify at least some authoring decisions.

         accessible templates (WCAG): Templates that can be filled in to
create web content that meets the WCAG 2.0 success criteria (Level A, AA 
or AAA), when both of the following are true:
             The author correctly follows any instructions provided
(e.g., correctly responding to prompts, correctly replacing highlighted
placeholders); and
             No further authoring occurs
         Note: Under these conditions, some templates will result in
completely empty documents, which are considered accessible by default.

template selection mechanism
     A function beyond standard file selection that allows authors to
select templates to use as the basis for new content or to apply to
existing content.
Received on Monday, 27 August 2012 18:38:47 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:52:14 GMT