Re: Author incentives for accessibility

> Accessibility applies to all of us.

amen, brother!  accessibility cannot be seperated from usability, 
as one cannot use an object or tool if one cannot access it, nor 
can one access an object or tool if there is no indication that 
the object or tool even exists...

as sander eloquently expressed the situation, the solution lies 
in the authoring tools, especially when perceptual black holes 
are created by use of uni-modal (read: visually-oriented) authoring 
tools and concepts...  (which is why i, personally, still hand code)

as with the user agent issues, i would refer the list to the 
Authoring Tool Accessibility Guidelines, whose purview is not 
only ensuring that the output of an authoring tool is accessible,
but that the tool itself is accessible:

ATAG 1.0:
ATAG 2.0 Working Draft:
Authoring Tool Accessibility Working Group:

there is also an Evaluation and Repair activity within WAI, headquartered 

the ER WG currently has 1 document in Last Call:

Evaluation & Repair Schema 1.0:

and is moving in that direction with another:

HTTP Vocabulary in RDF:

there is also important work being done on roles and states in the 
Protocols & Formats group, under the rubric ARIA: Accessible Rich 
Interface Applications -- consult:

Roadmap for Accessible Rich Interface Applications (ARIA Roadmap):

Roles for Accessible Rich Interface Applications (ARIA Roles)

States and Properties Module for Accessible Rich Interface Applications 
(ARIA States & Properties):

how does the ARIA work fit in with HTML?  consult the following:

Embedding Accessibility Role and State Metadata in HTML Documents:

all of which should -- nay, must -- inform our work on HTML5,

LANGUAGE, n.  The music with which we charm the serpents guarding 
another's treasure.     -- Ambrose Bierce, The Devil's Dictionary
            Gregory J. Rosmaita,
     Camera Obscura:
UBATS: United Blind Advocates for Talking Signs:

Received on Friday, 18 May 2007 19:28:36 UTC