Whether
you use
Fangs or a
real
screen
reader it
is
difficult
for a
developer
or tester
to know if
a website
is really
accessible
unless
they have
an
understanding
of how
screen
reader
users
visualise
a website
and
interact
with it.

There is a
huge
difference
between
being able
to hear
the
content
and being
able to
understand
it. Whilst
it is
possible
to make
some
generalities
(as we do
in our
demonstrations)
every user
testing
project
reveals
difficulties
we would
not have
forseen.

It is far
too big a
topic to
discuss at
length
here, but
problems
include
having too
much
content on
a page,
use of
visual
metaphors,
and the
meaning of
the
content
being
conveyed
by the
spatial
relationship
between
two or
more
pieces of
content.
In each
case all
the
content
can be
heard but
it may not
be
understood.

Complex
tables and
nested
lists may
be
unintelligible
despite
being
marked up
perfectly
in terms
of
semantics
and
standards
compliance.
And
dynamic
content
(e.g.
DHTML and
AJAX) is a
world of
pain.

Steve
Green
Director
Test
Partners
Ltd /
First
Accessibility
www.testpartners.co.uk
www.accessibility.co.uk


Rahul
Gonsalves
<[EMAIL PROTECTED]>
wrote:

 Barney
Carroll
wrote:
 > Only I
can never
know if I
have
achieved
it,
because I
can't test
it; 
 > nor can
I find
anybody
else to
test for
me, or
even
pin-point
known 
 >
problems.
 
 Dear
Barney,
 
 For
Firefox,
this seems
like an
interesting
utility. I
haven't
used it 
 yet, but
I think
you might
find it
useful.
 https://addons.mozilla.org/firefox/402/
 
 Regards,
   -
Rahul.
 
 
 *******************************************************************
 List
Guidelines:
http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe:
http://webstandardsgroup.org/join/unsubscribe.cfm
 Help:
[EMAIL PROTECTED]
 *******************************************************************
 
 





*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to