Re: [Access-activists] Next Set of Tasks for GAI

[Janina Sajka]

One key strategy is to make accessible authoring tools available that
are capable of producing accessible web content. We need to be able to
point to tools that people can use effectively. For too long accessible
web content has required too much by-and tweaking and expert knowledge.

Guidelines, v. 2.0, for this are about to go to last call in the W3C's
Web 
Accessibility Initiative. We should provide comments, and I'll take on
the obligation to let us all know when this last call is published. It
is imminent, though. We're talking days--perhaps a couple weeks.

>From that we need to follow up with building in the recommended support
to some of our F/OSS authoring environments. I would include Open
Office. Last time I looked, its 'Save As' html was still generating
problematic html. If memory serves, I saw things like hard-coded fonts,
bolds, etc. These should be CSS, of course.

In parallel, we should follow up with CMS systems. Their default
teplates should be accessibility friendly. I believe Druple is the only
project to form an actual accessibility team for this. Chris, Gregory is
connected to that.


There have been other efforts in CMS, notably a GPL'd product produced
by a suburban DC development house for the Clinton White House called
EZRO.

Janina


Christian Hofstader writes:
> What then can we do to pressure web developers into making their
> sites accessible? Do we take the lawsuit approah like NFB or educate
> the proprietors and just sit  back and wait for change?
> 
> cdh: If Macy's didn't allow black people in it would be a national
> outcry; if Amazon doesn't let blinks in we are supposed to be happy
> as a clam while we watch them ignore us?
> 
> cdh: Sometimes, one has to throw a brick.
> 
> cdh: We will offer them test results from running testing tools on
> their sites, we will afford them the opportunity of having our
> volunteers work with them to remidiate their site, we will give them
> n months to come into compliance, we'll start a petition to
> hopefully add a little pressure, we can put them onto our wall of
> shame but celebrate corrections when they happen and, our last order
> of biz, we will work with the disability law center in Boston to
> threaten and then take legal action.
> 
> Peter is correct, though, web accessibility is probably not an issue
> for FSF to campaign so all of this may be mute.
> 
> Ideas?
> 
> cdh
> 
> 
> On 07/01/2010 11:46 AM, T.V. Raman wrote:
> >Also, shaming has the effect of the person being shamed becoming
> >first defensive, and next just doing the bare minimum to pass a
> >checkbox test --- the user usually gets forgotten in the melee
> 
> -- 
> Happy Hacking,
> cdh
> 
> Christian Hofstader
> Director of Access Technology
> FSF/Project GNU
> http://www.gnu.org, http://www.fsf.org
> GNU's Not Unix!

-- 

Janina Sajka,   Phone:  +1.443.300.2200
                sip:address@hidden

Chair, Open Accessibility       address@hidden  
Linux Foundation                http://a11y.org

Chair, Protocols & Formats
Web Accessibility Initiative    http://www.w3.org/wai/pf
World Wide Web Consortium (W3C)