Re: [w3c-wai-pf] <none>

Split thread out of W3C member-private space.

Hi Bill,

Actually, I am still waiting for the PF group to recharter, at which point
I intend to continue the work on XAG, if the working group charters to do
it.

Otherwise, this makes sense. One of the things I think is important is
that Wikis require people learning a new collection of syntax - which
varies between wikis.

HTML is a realtively simple set of structures, and there are a handful of
editors that are capable of generating it in ways that can at the very
least be made compatible with accessibility. Given the failure of many
servers to accept things like HTTP PUT, or allow anything but the most
simplistic levels of authorisation, we are in an unfortunate situation
where it is still not easy for ordinary people to pick up straightforward
tools that do a reasonable job.

That far, I am following you... so where do we go? Presumably writing
actual techniques for ATAG is a helpful thing to do - showing in some
reasonable detail what you are achieving, how to do it with actual tools
available to people, and how to implement it in other tools...

whaddaya reckon?

cheers

Chaals

-- 
Charles McCathieNevile           charles@sidar.org
                 http://www.sidar.org

<quote who="William Loughborough">
>  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.

> 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 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.

Received on Sunday, 31 October 2004 12:46:03 UTC