reader users won't
hear the title attribute at all but, if they do, all it will contribute
is unnecessary noise.
HTH
Mel
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
sibility:hidden etc.
http://css-discuss.incutio.com/?page=ScreenreaderVisibility
Mel
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
on 23/11/2006 10:54 Barney Carroll said the following:
Steve, do you know what JAWS' attitudes to display:none; and
visibility:hidden; are?
Not Steve but...
http://www.access-matters.com/screen-reader-test-results/
separate
links - which means that it could create probems for some users. I'm not
sure if JAWS 7 can audibly separate the links itself. Certainly, older
screen readers will have problems and, probably, anyone using a bra
essibility, any warnings
from accessibility parsers can be safely ignored.
Mel
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
it's so
over-used) so will not be pre-warned about the new window.
Automated accessibility parser warnings about tab indexes and access
keys can be safely ignored provided you've actually tested the keybaord
navigation of the page yourself and you
sion has been around long enough, or is
implemented widely enough, to indicate how many keyboard navigators
actually use make use of the facility when it's offered. I know I've
never bothered. :-)
Mel
***
Lis
gn contrary to that
expectation, the end result may be disorientations and/or frustration
for this sub-group.
In the past 12 months, I've not come across any newer studies that would
suggest anything has changed.
Hope that helps.
Mel
**
). Using conceptual
icons can help both groups to some extent but there does come a a point
when there is very little a designer can do to alleviate the problems
and it's really down to training, support and experience at the user's end.
Mel
, I just thought it was worth pointing out that those suffering
from severe dyslexia often use screen readers for support.
So it maybe unwise to assume that a screen reader user can't see.
Mel
***
List Guidelines:
arily, in my opinion).
And for what benefit?
Mel
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
on 30/10/2006 14:14 Rob Kirton said the following:
FAO Katie Ledger
I (undoubtedly along with others) found your article "designing a more
accessible web" to be of great interest.
If you're asking for signees to this, please add my na
. Is there some sort of
hangup I don't know about?
OATS is fairly new (launched May 2006) but there does seem to be a
reasonable archive of software already available or under development.
Mel
***
List Guidelines:
the user? My own
research amongst keyboard navigators suggest that very few, if any, will
bother to 'learn' accesskeys associated with a specific site. After all,
would you? If people don't already 'know' the
element - which would suggest that you can't use it to enclose a block
level header element.
Could you not precede the form with a header?
Mel
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubs
15 matches
Mail list logo
