UX inspection question

[Michael S Elledge]

Rich, everyone--

Can we handle this with properly structured JavaScript? So that it 
degrades gracefully according to the browser being used? I'm sure it's 
not universally the case, but the JAWS and Window-Eyes users we've 
talked to often upgrade their AT application when they upgrade their 
computer, in other words, all at once. So they'll have a JAWS/IE 
configuration that is compatible at a certain point in time. Rather than 
adding a new browser, for example, to an existing setup.

Mike

Richard Schwerdtfeger wrote:
>
> Michael,
>
> The point I am trying to make is that if you go back to some old level 
> of JAWS the rest of your UI will not be compatible with JAWS. This is 
> a big can of worms.
>
> That said, I do not believe we have addressed backward compatability 
> with either the browser or the assistive technologies targeted. We 
> started to discuss that I believe last week wrt. browser support.
>
> One suggestion is that we do both or make it configurable. We can 
> store landmarks in the document and turn on/off skip links and have 
> them link to the regions with the landmark roles.
>
> Thoughts?
>
> Rich
>
>
> Rich Schwerdtfeger
> Distinguished Engineer, SWG Accessibility Architect/Strategist
> Chair, IBM Accessibility Architecture Review Board
> blog: http://www.ibm.com/developerworks/blogs/page/schwer
> Inactive hide details for Michael S Elledge <elledge at msu.edu>Michael S 
> Elledge <elledge at msu.edu>
>
>
>                         *Michael S Elledge <elledge at msu.edu>*
>
>                         06/01/2007 08:31 AM
>
> 	
>
> To
> 	
> Richard Schwerdtfeger/Austin/IBM at IBMUS
>
> cc
> 	
> Colin Clark <colin.clark at utoronto.ca>, Daphne Ogle 
> <daphne at media.berkeley.edu>, Herb Wideman <herb at yorku.ca>
>
> Subject
> 	
> Re: UX inspection question
>
> 	
>
>
> Hi Rich--
>
> We also have to be mindful of screen reader users who have older
> browsers and earlier versions of JAWS. My point is not to hinder our
> ability to take advantage of Web 2.0 advances but to ensure that Fluid
> remains accessible to those who are not on the cutting edge of
> technology and techniques.
>
> Has the question of backward compatibility been satisfactorily answered?
> What I'm really looking for is evidence that this won't be a
> problem--I'm all for making navigation easier for persons using adaptive
> technology.  But we have to be aware that adaptability is a two-way 
> street.
>
> Mike
>
> Richard Schwerdtfeger wrote:
> >
> > Michael,
> >
> > The role landmarks are now actual an XHTML 1.X module and reside in
> > the xhthml 1.X namespace. They are included in the ARIA specification
> > along with the role attribute. So, you will be able to say
> > role="navigation" in your markup using the HTML techniques outlined in
> > the ARIA roadmap.
> >
> > Firefox 3 will provide support for ARIA. Without ARIA you won't have
> > Web 2.0 accessibility. Since the plan is to target Web 2.0
> > applications this is the direction we need to take. So, we are going
> > to be limited to ARIA supportin browsers as it is. Microsoft is
> > participating in the ARIA effort. I believe they are waiting for a
> > last call draft before diving head long into the ARIA implementation.
> >
> > The goal of this project is Web 2.0 applications and pushing the
> > envelope on usability. We are going to have to deal with this industry
> > transition. IMHO skip to content links mixes content and presentation
> > to achieve a goal which should be better specified in the markup. You
> > also have to put them in your tab sequence which is also a usability
> > problem. You would not put links in your GUI application to jump
> > between frames. You would rather assign a key mapping to do the job.
> > Hopefully this image illusrates the point. We, the browser, or the AT
> > could assign a key mapping to cycle through the target region/landmark
> > types.
> >
> >
> >
> >
> >
> > Rich Schwerdtfeger
> > Distinguished Engineer, SWG Accessibility Architect/Strategist
> > Chair, IBM Accessibility Architecture Review Board
> > blog: http://www.ibm.com/developerworks/blogs/page/schwer
> > Inactive hide details for Michael S Elledge <elledge at msu.edu>Michael S
> > Elledge <elledge at msu.edu>
> >
> >
> >                         *Michael S Elledge <elledge at msu.edu>*
> >
> >                         05/31/2007 04:41 PM
> >
> >
> >
> > To
> >
> > Herb Wideman <herb at yorku.ca>
> >
> > cc
> >
> > Daphne Ogle <daphne at media.berkeley.edu>, Colin Clark
> > <colin.clark at utoronto.ca>, Richard Schwerdtfeger/Austin/IBM at IBMUS
> >
> > Subject
> >
> > Re: UX inspection question
> >
> >
> >
> >
> > Hi Herb--
> >
> > This is a very good question.
> >
> > I'm not sure how we'll deal with these. I don't think checkers have been
> > revised to address XHTML2, although I may be wrong, and I'm not familiar
> > enough with them (yet) to know their proper application.
> >
> > Also, I wonder how soon browsers will be able to handle roles, and
> > if/when older browsers will ignore them so that their use won't cause
> > problems. I would hate to lose functionality (i.e., skip to content
> > links) in the near term for the sake of long-term benefits--unless the
> > long-term is truly right around the corner. Internet Explorer is still
> > far and away the most common browser used by screen reader users and
> > usually lags Firefox in adopting and/or applying new specifications
> > correctly.
> >
> > Rich, Colin, please feel free to chime in here.
> >
> > Mike
> >
> > Herb Wideman wrote:
> > > Hi Daphne and Mike,
> > >
> > > I did not mention it at the meeting but some of the additions Rich
> > > added to the Wiki inspection page:
> > >
> > >     * XHTML navigation landmarks from XHTML2
> > >      
> > 
> http://www.w3.org/TR/2006/WD-xhtml-role-20061113/#s_role_module_attributes^
> > >       (don't use skip to main content) as these roles are much more
> > >       comprehensive
> > >     * Consider a navigation section on each page (role="navigation")
> > >     * Correctly tag headings
> > >     * Make sure all navigation landmarks have a title including
> > >       customer ARIA regions
> > >     * Correctly tag table headers
> > >     * mark tables which should not behave has tables as presentational
> > >       (role=:"wairole:presentation")
> > >     * Correctly tag table headers
> > >
> > >
> > > ...etc - if checking these are to be part of the inspections I hope we
> > > will be able to do this with the automated tools as we just don't have
> > > the HTML/CSS expertise to do this manually...although possibly our
> > > computer services participant will, I haven't met him yet.
> > >
> > > Mike has posted the tool demo links so I will give them a spin on a
> > > few Moodle pages to see what they produce.
> > > Herb
> > >
> > /(See attached file: elledge.vcf)/
> >
> /(See attached file: elledge.vcf)/
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: elledge.vcf
Type: text/x-vcard
Size: 136 bytes
Desc: not available
Url : http://fluidproject.org/pipermail/fluid-talk/attachments/20070601/0116a6bd/attachment.vcf