Re: Best practices for screen readers

Hi Roel,

>> Thanks for your valuable comments, but I'm afraid they were meant for
>> Andy, not for me ;)

Sorry about that, my error.

>> I don't know if this discussion has ever been brought up, but I find
>> this list (email lists in general actually) very cumbersome to use.

It takes a while to get used to using lists but as a medium I find it
worth it - as
it teaches you to gather your thoughts and present them in a cogent fashion.

That in itself is a useful exercise/meditation in these days of instant
"connectedness".

There have been some good points raised in this thread, about the
limitations of current
AT and also flaws in markup itself, that can make for unsuitable
rendering/delivery to the end user.

All the best

Josh






Roel Van Gils wrote:
> 
> Hi Joshue,
> 
> Thanks for your valuable comments, but I'm afraid they were meant for
> Andy, not for me ;)
> 
> I don't know if this discussion has ever been brought up, but I find
> this list (email lists in general actually) very cumbersome to use.
> Especially from an accessibility perspective (markup cannot be used,
> long threads become confusing to read etc.).
> 
> I'm interested in hearing suggestions on how to follow up discussions
> more easily (I'm using Gmail for it now, but I don't really like the
> way Gmail handles threads).
> 
> -- 
> Roel Van Gils
> AnySurfer - Belgisch kwaliteitslabel voor toegankelijke websites
> http://blog.anysurfer.be
> 
> 
> On 10/6/06, Joshue O Connor <joshue.oconnor@ncbi.ie> wrote:
>>
>> Hi Roel,
>>
>> Welcome to the list.
>>
>> > You can mark up a phone number (indeed, a whole address) using semantic
>> > hCard microformat markup:
>> >
>> >         <http://microformats.org/wiki/hcard>
>> >
>> > (Microformats are a way of adding simple markup to human-readable data
>> > items such as events, contact details or locations, on web pages, so
>> that
>> > the information in them can be extracted by software and indexed,
>> searched
>> > for, saved, cross-referenced or combined. More technically, they are
>> items
>> > of semantic markup, using just standard (X)HTML with a set of common
>> > class-names. They are open and available, freely, for anyone to use.)
>>
>> Maybe you can, as you suggest, use these microformats in this way
>> but be careful as that doesn't mean that you should. Many user agents
>> don't even fully
>> support HTML never mind the new kid on the block. I would be concerned
>> that that is
>> just bad advice.
>>
>> Its interesting to me that the advent of these microformats is an
>> indication of future possibilities
>> but I guess that its application, especially relating to disability, is
>> very limited.
>>
>> > Hopefully, in time, the authors of screen readers and similar software
>> > will include recognition of that standard.
>>
>> You may have a very long beard by the time that happens. Mine will be
>> longer.
>>
>> > There is also a style for aural stylesheets, something like
>> "spell-out",
>> > but that's not widely supported.
>>
>> Exactly.
>>
>> Josh
>>
>>
>>
>> Andy Mabbett wrote:
>> > "Roel Van Gils" <roelvangils@gmail.com> wrote on 06/10/2006 16:54:45:
>> >
>> >> Hi Bianca,
>> >
>> >> I'm a newbie on this list myself ;)
>> >
>> > Me too. We should start a club! ;-)
>> >
>> >>> 2. Is there a way to make the screen reader know that a number is a
>> >>> phone number or street address so it reads 2-9-1-6 instead of 2,916?
>> >
>> >> I'm not aware of any reliable way to achieve this without adding extra
>> >> (unsemantic) tags. This will probably work, but it's not so pretty.
>> >
>> > You can mark up a phone number (indeed, a whole address) using semantic
>> > hCard microformat markup:
>> >
>> >         <http://microformats.org/wiki/hcard>
>> >
>> > (Microformats are a way of adding simple markup to human-readable data
>> > items such as events, contact details or locations, on web pages, so
>> that
>> > the information in them can be extracted by software and indexed,
>> searched
>> > for, saved, cross-referenced or combined. More technically, they are
>> items
>> > of semantic markup, using just standard (X)HTML with a set of common
>> > class-names. They are open and available, freely, for anyone to use.)
>> >
>> > Hopefully, in time, the authors of screen readers and similar software
>> > will include recognition of that standard.
>> >
>> > There is also a style for aural stylesheets, something like
>> "spell-out",
>> > but that's not widely supported. I have a reference at home, and
>> will dig
>> > it out for next week.
>> >
>>
>>
>> ********************************************************************
>>
>> NOTICE: The information contained in this email and any attachments
>> is confidential and may be privileged.  If you are not the intended
>> recipient you should not use, disclose, distribute or copy any of
>> the content of it or of any attachment; you are requested to notify
>> the sender immediately of your receipt of the email and then to
>> delete it and any attachments from your system.
>>
>> NCBI endeavours to ensure that emails and any attachments generated
>> by its staff are free from viruses or other contaminants.  However,
>> it cannot accept any responsibility for any such which are
>> transmitted.  We therefore recommend you scan all attachments.
>>
>> Please note that the statements and views expressed in this email
>> and any attachments are those of the author and do not necessarily
>> represent the views of NCBI
>>
>>
>> ********************************************************************
>>
>>
>>
>>
> 
> 
> 


********************************************************************

NOTICE: The information contained in this email and any attachments 
is confidential and may be privileged.  If you are not the intended 
recipient you should not use, disclose, distribute or copy any of 
the content of it or of any attachment; you are requested to notify 
the sender immediately of your receipt of the email and then to 
delete it and any attachments from your system.

NCBI endeavours to ensure that emails and any attachments generated 
by its staff are free from viruses or other contaminants.  However, 
it cannot accept any responsibility for any such which are 
transmitted.  We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email 
and any attachments are those of the author and do not necessarily 
represent the views of NCBI


********************************************************************

Received on Saturday, 7 October 2006 08:37:51 UTC