Liddy, Tom,
Where I get confused in this discussion is I understand <auditory> to
mean content including encoded sound that is significant for its purpose
where as Tom's description of <AURAL> is text content that can be
transformed by a synthesiser into speech. These are obviously distinct
and an argument can be put forward that both should exist.
Could some please clear up my confusion if that is what it is or take my
point on board if I am right?
Cheers,
Martyn
-----Original Message-----
From: DCMI Accessibility Community
[mailto:[log in to unmask]] On Behalf Of Tom Worthington
Sent: 07 May 2008 07:16
To: [log in to unmask]
Subject: Re: accessibility term use and vocab
At 09:44 AM 7/05/2008, Liddy Nevile wrote:
>... I suspect I am being very dense here but I cannot see quit how
>these terms would help us. ...
I was suggesting using the words W3C uses, such as "AURAL", rather
than "auditory".
>... something like auditory(ISO/IEC)= AURAL(W3C)= formatted for
>speech synthesisers. Now what if it was a sound file but not so
>formatted? Wouldn't I have to have another word? ...
Yes.
Just for those having difficulty following this, the W3C term "AURAL"
is for a text document which can be turned into synthetic speech,
using some special formatting to make it more intelligible as speech.
It may be important to distinguish this from a digital recording of a
person reading out the text. On the other hand, as long as it ends up
being sound, perhaps it doesn't much matter how the sound is produced.
>BTW - it's wonderful that you teach your students what you teach
>them and wouldn't it be even more wonderful if everyone did this??? ...
Yes. Many Australian Government agencies make reasonable efforts to
produce accessible web sites (I helped train some of the people doing
this). But most commercial organisations make little effort for
accessibility.
>I guess not everyone on this list will know how to get access to
>what you teach your students but I am sure many would be interested
>- can you point them to it please? ...
The latest version of my notes on Website Design for ANU course
"Networked Information Systems" (COMP2410 / COMP6340) are at:
<http://www.tomw.net.au/2008/wd/>.
There is an explanation of this in in "Teaching Web Accessibility at
an Australian University", Web Accessibility Forum 2007, Canberra, 11
April 2007 <http://www.tomw.net.au/technology/it/webteaching.shtml>.
A lot of the accessibility teaching is done in the labs, not the
lectures. The automated accessibility tools are very useful for this,
as students can learn on real problems. This semester their
assignment is to redesign the web page for the 2010 Commonwealth Games.
Also I emphasize flexible design which will work with screens,
talking terminals and mobile phones. Web pages for mobile phones gets
the students a lot more excited than ones for blind people.
Tom Worthington FACS HLM [log in to unmask] Ph: 0419 496150
Director, Tomw Communications Pty Ltd ABN: 17 088 714 309
PO Box 13, Belconnen ACT 2617
http://www.tomw.net.au/
Adjunct Senior Lecturer, ANU
---------------------------------
The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302).
|
