W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2003

More references on XML/XHTML and accessibility

From: Tim Roberts <tim@wiseguysonly.com>
Date: Fri, 27 Jun 2003 08:36:51 +0200
Message-ID: <3EFBE603.1000402@wiseguysonly.com>
To: w3c-wai-ig@w3.org, Kynn Bartlett <kynn@idyllmtn.com>, tina@greytower.net

This stuff is at last accessibility related again.

Kynn Bartlett also wrote:

http://www.csun.edu/cod/conf/2003/proceedings/76.htm

While *XML languages generally provide the greatest accessibility*, 
there has been major progress in the development of document formats 
which had previously provided a barrier to access for many people with 
disabilities.

HTML -- Extensible HyperText Markup Language -- is the reformulation of 
HTML according to the rules of XML. XHTML is a clean, structured version 
of HTML that allows for greater separation of content and presentation, 
and compatibility with XML tools. Information stored in XML can be 
easily converted to XHTML for display in Web browsers, and that XHTML 
may be tailored to the needs of specific users.

Rather than being afraid of future advances and their potential to shut 
out audiences with special needs, we should embrace the concepts of the 
21st Century Web, employing them to their fullest to ensure 
accessibility for everyone. While HTML continues to serve as the most 
common language of the Web, accessibility for the new millennium is not 
merely about checking your alt text.


Kynn Bartlett also wrote (about using XHTML, XML and XSLT):

http://www.csun.edu/cod/conf/2002/proceedings/218.htm

The *accessibility benefit* of this approach, which is a single source, 
multiple interface model (rather than the traditional single source, 
single interface model of earlier web design) is that it allows for each 
user to receive an optimal user interface -- one which is not merely 
"accessible" but also "usable." Rather than the screenreader version 
being a derivate of the graphical user's design, the screenreader user 
receives her own interface to the same content, made to work with her 
needs and preferences. Conflicts between accomodations necessary 
different disability types can be mitigated with such an approach, since 
different transformations can be used for different users.

Tim writes:

These are great resources (I am being serious). They assure me that I am 
making the right choice in using XHTML as my base for accessible 
development.
Its good to have these kind of resources to affirm the way I feel.

Many thanks Kynn.

Tim








Kynn Bartlett wrote:

>
> On Thursday, June 26, 2003, at 03:56 PM, Tim Roberts wrote:
>
>> My only crime here is trying to defend standards.
>
>
> *snicker*
>
> I'm dropping this conversation:  I've made my points effectively,
> and everything more I'd say would just be repeating myself.
>
> --Kynn
>
> -- 
> Kynn Bartlett <kynn@idyllmtn.com>                     http://kynn.com
> Chief Technologist, Idyll Mountain                http://idyllmtn.com
> Author, CSS in 24 Hours                       http://cssin24hours.com
> Inland Anti-Empire Blog                      http://blog.kynn.com/iae
> Shock & Awe Blog                           http://blog.kynn.com/shock
>
>
Received on Friday, 27 June 2003 02:34:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:10 GMT