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

Re: [w3c-wai-pf] <none>- eXtensible Accessibility Guidance

From: Lisa Seeman <lisa@ubaccess.com>
Date: Fri, 05 Nov 2004 08:54:21 +0200
To: William Loughborough <love26@gorge.net>, pauls@gorge.net, danbri@w3.org, Libby.Miller@bristol.ac.uk, info@speaktomecatalog.com, me@aaronsw.com, danny666@virgilio.it, zoojuliet@attbi.com, sbpalmer@gmail.com, coordina@sidar.org, joshuaa@microsoft.com, wendy@w3.org, charles@sidar.org, mcmay@w3.org
Cc: w3c-wai-au@w3.org, w3c-wai-pf@w3.org
Message-id: <057101c4c30e$5d6009b0$2b49003e@IBMA4E63BE0B9E>
Charles,

do you have a WIKI to suggest we use

Keep well
L
  ----- Original Message ----- 
  From: William Loughborough 
  To: pauls@gorge.net ; danbri@w3.org ; Libby.Miller@bristol.ac.uk ; info@speaktomecatalog.com ; me@aaronsw.com ; danny666@virgilio.it ; zoojuliet@attbi.com ; sbpalmer@gmail.com ; coordina@sidar.org ; joshuaa@microsoft.com ; wendy@w3.org ; charles@sidar.org ; mcmay@w3.org 
  Cc: w3c-wai-au@w3.org ; w3c-wai-pf@w3.org 
  Sent: Saturday, October 30, 2004 6:29 PM
  Subject: [w3c-wai-pf] <none>


  From the ATAG 2.0 document this quote is sort of like the overarching "declaration of independence" for which we have set out to craft the various guidelines/recommendations and other pronouncements:

  "Everyone should have the ability to create and access Web content."

  To this end I'm highjacking the acronym XAG (nobody's using the original "XML Accessibility Guidelines" anyway!) to mean "eXtensible Accessibility Guidance". 

  If anybody wants to join me, I think the first effort might be to make the software underpinnings that enable Lisa's http://www.webeone.org/ldweb/ site work in an interactive way, in fact in multiple interactive ways.

  To start with, each time something is preached it should be an exemplar of what it says. When the document speaks (as it does) of  "make text expandable", there must be a way to do that right there rather than just preaching it. If it says something about fonts, etc. they should be showable. In short if this document can be used to develop the techniques to be/do what it says, it can serve as the basis for numerous essays into the field of providing access.

  If it be a wiki then we can include allowance of "the ability to create" as well as the ability to "access Web content".

  The tools for doing this are fairly abundant but those of us who don't know how to make text "expand in place" or easily provide illustrations of style changes and such things need help from those for whom these are second nature - or maybe I'm over-simplifying?

  If anyone can do any part of this, even just looking it over and advising or all the way to downloading the current source and modifying any part of it and I'll put it up for others to mess with. 

  If we continue to depend on formal/WAI/process/consensed procedures this will take forever and not be sufficiently involving. So if you know how to fairly readily make it a simple stroke to turn the admonition to use a certain font into a fairly straightforward way to let the reader/would-be-contributor actually see what it is you're talking about, it would be a neat present for an old geezer who needs all the help he can get.

  At the bottom of the referenced page is one of an infinitude of possible examples of the "clear/simple" argument and if that could be made a "transform" (maybe a "de-fogging key"?) so that clicking on dense would overlay/substitute clear?

  Anybody home?

  --
  Love.

  Everyone/everything/everywhere/always connected 



------------------------------------------------------------------------------



  ---
  Outgoing mail is certified Virus Free.
  Checked by AVG anti-virus system (http://www.grisoft.com).
  Version: 6.0.774 / Virus Database: 521 - Release Date: 10/7/2004
Received on Friday, 5 November 2004 08:07:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:39:51 UTC