- From: Charles McCathieNevile <charles@w3.org>
- Date: Wed, 31 Mar 1999 16:22:47 -0500 (EST)
- To: Jutta Treviranus <jutta.treviranus@utoronto.ca>
- cc: William Loughborough <love26@gorge.net>, "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
I don't think merging the two would confuse the reader. I think that if done right it would strengthen the message that accessibility of the tool and accessibility of the output are parts of making a tool accessible, and that both things are necessary. The overlap is primarily in the sections identified by Jutta - 2.6 and 2.7, but it seems to me a clear overlap rather than a dubious one. Charles On Wed, 31 Mar 1999, Jutta Treviranus wrote: At 3:48 PM -0500 3/31/99, Charles McCathieNevile wrote: >I also think that this is one of the areas where the distinction between >section 2 and section 3 is meaningless. I therefore think Ian's proposal >to merge the two sections has merit, and should be revisited. > I feel the two sections should not be merged. They address two very distinct principles: 2. generate accessible content and 2. have an accessible user interface. Even in the sections where there might be a dubious overlap such as 'integrate help files' and 'allow user configuration', there are still clear distinctions and merging them would only muddy the waters and confuse the reader. Integrate help files and allow user configuration are general software accessibility principles that we will probably only cover by reference in section 3, so the overlap is a mute point. 3 does not fit into 2 in any other way. Trying to make 2 more general to accomodate the principles in 3 would weaken the message. Jutta --Charles McCathieNevile mailto:charles@w3.org phone: +1 617 258 0992 http://www.w3.org/People/Charles W3C Web Accessibility Initiative http://www.w3.org/WAI MIT/LCS - 545 Technology sq., Cambridge MA, 02139, USA
Received on Wednesday, 31 March 1999 16:22:56 UTC