There is work going at the W3C to make it easier for
developers to make AJAx applications more accessible to people
with disabilities.

More information at:
http://www.w3.org/WAI/PF/roadmap/

Jon


---- Original message ----
>Date: Mon, 12 Jun 2006 22:36:02 -0400
>From: "Michael Yeaney" <[EMAIL PROTECTED]>  
>Subject: RE: [WSG] Screenreaders and AJAX and bears...oh my...  
>To: <[email protected]>
>
>Exactly....I was not suggesting that we should ignore all
aspects - I was
>merely questioning why it seems that we (web developers) are
responsible (or
>so it seems) for the specifics (for example, why should we
worry about
>_exactly_ what colors we choose - I can only hope that a
capable program can
>offer some version of color mapping to alleviate such
problems per a users
>preferences).  Don't get me wrong - this stuff is _very_
important, and I
>think we all understand that.
>
>I agree totally with James - I am stumped that the screen
readers of the day
>need "hand fed" exact information in order to convey a reasonable
>experience.  The translation of screen material into its'
speech counterpart
>(IMO) should not be dealt with by web developers on a
microscopic level.  If
>I need to do that, than I had better be employed by Freedom
Scientific.....
>:-)
>
>Thanks again,
>Mike Yeaney
>
>________________________________
>
>From: [email protected]
[mailto:[EMAIL PROTECTED]
>On Behalf Of James Laugesen
>Sent: Monday, June 12, 2006 9:44 PM
>To: [email protected]
>Subject: Re: [WSG] Screenreaders and AJAX and bears...oh my...
>
>
>Hi Steve, sorry I better confirm what I said "IMO even
considering colour
>blindness is counter-productive, colour correction should be
a feature of an
>'acccessability-friendly' browser.".
>
>If a website is accessable via a screen reader, then it
_must_ be possible
>to display the site in more appropriate colours & contrasts
per users needs.
>So I just think it's counter-productive that a web developer
(not designer)
>considers specific disabilities. A developer should be
focused on exposing
>information in a way that can be interperted by anyone or
anything (isn't
>that why we're all here? standards...). Let a more
specialised group solve
>the specific accessability issues. 
>
>I'm stumped at the ajax/screen reader problem. It's
interesting. I'd love to
>hear from a "screen reader expert" if there is one here?
>Are vision impaired people able to have/develop a kind of
peripheral
>hearing? We can only focus our eyes on one thing but remain
constantly aware
>of the surroundings, obviously hearing is same, but I wonder
if equivalent
>level of accurancey can be acheived with complex information
like spoken
>words. 
>I know performers and presenters can become skilled at
performing some
>actions, speaking, and hearing input from producers,
directors, etc...
>interesting problem.
>
>J
>
>
>On 13/06/06, Steve Green <[EMAIL PROTECTED]> wrote: 
>
>       Having just returned from a user-testing session with
someone who
>has severe colour perception impairment (caused by retinitis
pigmentosa) I
>am appalled by this "it's not the designer's problem"
attitude. This person
>uses the ZoomText magnifier, which has a wide range of colour
substitution
>features but on the site we were testing some of the colour
combinations
>were unreadable regardless of which filter was used. It is
essential that
>sites have sufficient colour and brightness contrast to begin
with.
>        
>       The difficulty with AJAX and screen readers is how to notify the
>user when the content has changed, how to tell them which
content is now
>different and how it is different. This is not covered by any
standards so
>it is no surprise that different screen readers behave
differently as shown
>by a couple of recent research articles. I do not believe
that this is
>something the screen reader vendors can resolve by
themselves, and it will
>require input from all sides of the industry to define the
required
>behaviour.
>        
>       However, it is not simply a technical problem because any
successful
>solution will be dependent on the user creating a mental
model of the page,
>modifying it each time the page is updated and keeping track
of successive
>updates. This is no mean feat given that even static websites
can be
>difficult to visualise, and I have no confidence that there
will ever be a
>viable solution that involves asynchronous or 'push'
technologies.
>        
>       Steve Green
>       Director
>       Test Partners Ltd / First Accessibility
>       www.testpartners.co.uk
>       www.accessibility.co.uk
>
>________________________________
>
>       From: [email protected]
>[mailto:[EMAIL PROTECTED] On Behalf Of James
Laugesen
>       Sent: 12 June 2006 23:57
>       To: [email protected]
>       Subject: Re: [WSG] Screenreaders and AJAX and bears...oh my...
>       
>       
>               I think the only burden placed on developers is to ensure
>their site can be realisticly processed by a computer.
>       When I consider "accessability", I consider it reffering to
>accessability by computers... I know that's not how the term
is usually
>used, but that's just how I think about it. Because, in most
cases some
>computer system is acting as an interface between the
site/software and the
>disabled user. 
>       The 'old' tables and slicing method left the html virtually
useless;
>the browsers had no idea what they're processing, they can
only render it
>and hope the human viewing the screen can understand it.
>       XHTML is essentially about acheiving that... semantics... and
>ultimately accessability. 
>       I think that's a reasonable responsibility to place on all
>developers (not just web).
>       However I do think it's unreasonableto expect WEB developers to
>implement generic solutions to accessability problems, ie,
why implement
>your own screen reader? Or provide facility to change font
size? IMO even
>considering colour blindness is counter-productive, colour
correction should
>be a feature of an 'acccessability-friendly' browser. 
>       
>       I'm not much up-to-speed with screen readers; anyone care to
educate
>us? What's hot, what's not, etc?
>       Any WSG members use screen readers? (due to dissability I
mean, not
>just for testing).
>       
>       J
>       
>       
>       On 13/06/06, Gene Falck <[EMAIL PROTECTED]> wrote: 
>
>               Hi Mike,
>               
>               You wrote:
>               
>               >However, what I've noticed that you do not see are articles
>pushing
>               >the screen reader manufacturers to make more capable and
>intellegent
>               >readers for the browsers.....they seem to be able to do
>this for 
>               >desktop applications (at least to a reasonable level).  It
>seems that
>               >many of the efforts we are making (as well as the WSG) to
>enable
>               >accessibility are in fact disabling (and in many cases
>abandoning) the 
>               >rich features on the net - this goes back to the whole
>"magazine
>               >article" site versus the "application" site - two different
>purposes,
>               >two different needs - both based on the same underlying
>technologies, 
>               >and both need to be accessible.
>               
>               IMO this is because physical access rules came after there
>were
>               wheelchairs that had, in turn, been developed long after
>most of
>               the physical structures we take for granted were
>standardized. 
>               
>               In spite of that timeline, there were some things that had
>to be
>               changed such as the provision of ramps.
>               
>               In web development, we are, then, figuratively, trying to
>build
>               doorways and invent the wheelchair at much the same time.
>Not 
>               only is there a major emphasis on web sites doing a lot of
>the
>               work on this but also our efforts may be obsolete as soon as
>the
>               next generation of assisting software is introduced.
>               
>               That may be a discouraging prospect, but I think we still
>have 
>               to keep up as best as we can.
>               
>               --
>               
>               Regards,
>               
>               Gene Falck
>               [EMAIL PROTECTED]
>               
>               
>               
>               
>               ****************************************************** 
>               The discussion list for   http://webstandardsgroup.org/
>               
>               See http://webstandardsgroup.org/mail/guidelines.cfm
>               for some hints on posting to the list & getting help 
>               ******************************************************
>               
>               
>
>
>
>       ******************************************************
>       The discussion list for http://webstandardsgroup.org/
>       
>       See http://webstandardsgroup.org/mail/guidelines.cfm
>       for some hints on posting to the list & getting help
>       ******************************************************
>       
>       ******************************************************
>       The discussion list for http://webstandardsgroup.org/
><http://webstandardsgroup.org/> 
>       
>       See http://webstandardsgroup.org/mail/guidelines.cfm
>       for some hints on posting to the list & getting help 
>       ****************************************************** 
>
>
>
>******************************************************
>The discussion list for http://webstandardsgroup.org/
>
>See http://webstandardsgroup.org/mail/guidelines.cfm
>for some hints on posting to the list & getting help
>******************************************************
>
>
>
>******************************************************
>The discussion list for  http://webstandardsgroup.org/
>
> See http://webstandardsgroup.org/mail/guidelines.cfm
> for some hints on posting to the list & getting help
>******************************************************
>


Jon Gunderson, Ph.D.
Director of IT Accessibility Services
Campus Information Technologies and Educational Services (CITES)
and 
Coordinator of Assistive Communication and Information Technology
Disability Resources and Education Services (DRES)

Voice: (217) 244-5870
Fax: (217) 333-0248
Cell: (217) 714-6313

E-mail: [EMAIL PROTECTED]

WWW: http://cita.rehab.uiuc.edu/
WWW: https://netfiles.uiuc.edu/jongund/www/




******************************************************
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list & getting help
******************************************************

Reply via email to