Thread Subject: Re: Some comments ontheSpreadsheet (excel/html)
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: David Poehlman
Date: Sun, Jan 21 2007 4:25 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: None
- Previous message in thread: Gregg Vanderheiden: "Re: Some comments ontheSpreadsheet (excel/html)"
- Messages sorted by: Author | Thread | Date
Greg, My responses inline and only what I've address is left. Thanks
for the explanations and clarifications.
GV: We did create an audible method for locating buttons on a
screen. But it only worked with a portion of people who were blind
and is not recommended. It doesnât work across people who are
blind, it is unreliable, and it only works on screens with a small
number of items on it. Vibratory would have the same problems. So,
yes, theoretically some could use this but no, you couldnât use this
as a general approach for access to touchscreens by people who are
blind.
dp: how can I find out more about this and more details about the
approach used?
GV: Not sure I understand the question here. The blank on the form
talked about the four situations that you can have. 3 of them yield
accessibility. Your Mac example is one of the ones that is in an
accessible category. Actually it is sort of in all three of the
categories.
dp: I missunderstood the intent of the categorization and you've
cleared it up. Thanks!
GV: Sure â we could say âwithout vision, without hearing, etc.â
that doesnât say the user doesn't have vision it just says the
product should be operable without vision. This approach too has
problems when you play it out but it is easier for developers. We
should definitely explore both.
Note that these aren't solutions. They are functional requirements.
Solutions would be what you would use to meet the functional
requirements, and yes â solutions may address all or part of many
different technical and functional requirements. I'm going to take
your suggestion to the General Group since they are supposed to be
looking at the functional criteria.
dp: thhanks, I look forward to the discussion.
- Next message in Thread: None
- Previous message in Thread: Gregg Vanderheiden: "Re: Some comments ontheSpreadsheet (excel/html)"
WebAIM is an initiative of:
