Re: Template for Methods

Another issue I would like to raise is the following: (and it seems to
apply, probably lots of times!)

IF the text of Methods for different techniques is 90% or even more (95%?)
the same, and the only difference will be the technical example of
implementation, will we end up with lots of duplicates / duplicate pages?

So when reading the Methods in WCAG 3 for a specific functional outcome
there are (example) 7 Methods with 7 times the same text (only to be
discovered when reading them.
That might be frustrating and bloating the document (a Heading Method for
HTML, PDF, iOS, XR, Android, Technology x, Technology y etc) while every
time the text is 90 / 95% the same.


Different groups writing different interpretations for the same solution
and we end up with (example) 7 different texts for fixing Headings and the
reason why while only the implementation should be the difference.

Think we need to solve this also ASAP


Op di 18 aug. 2020 om 01:39 schreef Jeanne Spellman <>:

> Rachael, Francis and I worked on this new template for writing Methods
> today.  I'd like to discuss it tomorrow if we have time.
> It is a template and an example using the template.  The example uses a
> WCAG2 Technique, because it was fast.  There is also an Appendix section
> that you can ignore.  It's interesting to  try to do Methods based on
> Functional Outcomes instead of guidelines.  We had to work out a lot of
> little details of what goes where.
> For any content subgroup that has not written any Methods yet, please try
> it out.  If you have written Methods, you can try to to move your content
> to this new template, or you can send me what you have and I will fill out
> as much of the Method template as I can, and then go back to you with
> questions.
> Method Template and Example
> <>

Received on Tuesday, 25 August 2020 11:46:54 UTC