WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Screen reader question


From: Joshue O Connor
Date: Dec 13, 2007 3:40AM

Jared Smith wrote:
> You usually should not attempt fixing the MANY reading issues that
> screen readers have. Luckily, screen reader users are typically aware
> of these and use various methods (such as reading character by
> character or identifying punctuation) to make sense of information
> that doesn't seem to be read correctly. Trying to hack them to work
> the way we think they should is usually a bad idea and may result in
> issues in other screen readers.

Jared is right and its an important point. If some element of a page (a
table etc) has been marked up correctly then the screen reader user can
tap into features already existing in their AT to interrogate the
element. For example there are commands like "Speak all" or the ability
to read content character by character that are often used when there is
confusing or ambiguity in the content, and many screen reader users will
do this. Most are used to AT output being "slightly off". Relying on
this kind of functionality is not even really only for power users and
is fairly common among more basic level users of screen readers.

If XStandard are putting in some kind of "see what your content will be
like to a screen reader user" feature and this will be useful, don't
worry *too* much about trying to simulate perfect output as it's not
perfect for the existing AT :-)




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