W3C home > Mailing lists > Public > w3c-wai-au@w3.org > October to December 1999

Re: ATAG GL5 Integrate accessibility [Priority]

From: Charles McCathieNevile <charles@w3.org>
Date: Mon, 4 Oct 1999 20:19:30 -0400 (EDT)
To: pjenkins@us.ibm.com
cc: w3c-wai-au@w3.org
Message-ID: <Pine.LNX.4.10.9910042016030.30037-100000@tux.w3.org>
While we who know how to create accessible pages are doing it without
the support of our tools, the rest of the people who are building web pages
do not manage to make them accessible. The alternative to this is to educate
every author as to the requirements of accessible authoring, and a rough idea
of how to get around the tool, before they start using it.

Since that is clearly impractical, I suggest that 5.2 remain at P1 and 5.1
retain the priority 2 that was proposed and accepted by the working group
during the last call period.

Charles McCN

On Mon, 4 Oct 1999 pjenkins@us.ibm.com wrote:

  Comments from tool developers agree that "5.1 Make generation of accessible
  content a natural integrated..." and "5.2 Ensure the highest-priority accessible
  practices are among the most obvious..." are beneficial to achieving
  accessibility.  They agree that without proper integration the result may be
  obvious discontinuity and can affect user acceptance - but, none of the reasons
  documented in the intro paragraph nor in the checkpoints equate to the
  definition of Priority 1: essential to...  The developers agree it is beneficial
  and at best important ...  After all, we're creating accessible pages today
  without integrated tools.   Proposal to lower to priority 3
  Phill Jenkins

--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 Monday, 4 October 1999 20:19:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:28:22 UTC