E-mail List Archives
Thread: Re: can screen reader user please test expanding content?
Number of posts in this thread: 3 (In chronological order)
From: Greg Gamble
Date: Wed, Apr 06 2011 9:30AM
Subject: Re: can screen reader user please test expanding content?
No previous message | Next message →
Hello All,
I'm the one who asked Angela to send a request for the Screen reads help ( no account at the time )
I have a couple of questions, sorry if they've been answered before ...
So when a person using a screen reader encounters an accordion type of control, where the content is hidden from a sited user but is still visible in the source, they cannot see inside of them or know when they are opening? Reading up on support for ARIA lead me to the following ...
I found this on handling some of the issues that have been brought up:
http://test.cita.illinois.edu/aria/tabpanel/tabpanel1.php
http://test.cita.illinois.edu/aria/tabpanel/tabpanel2.php
... do these examples work better than the original example, as far as letting a screen reader user know what is happening?
http://www.sohtanaka.com/web-design/examples/toggle/bad.htm
Greg Gamble
SBCTC - Olympia | Information Services
p - 360-704-4376
think before printing
-----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Jeevan Reddy
Sent: Tuesday, April 05, 2011 1:10 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] can screenreader user please test expanding content?
Hi Angela,
The Markup is fine, still the symantics of this Jquery/CSS expanding content is not conveyed to AT.
I've tested with NVDA V2011.1 on Firefox 3.6 and Windows 7.
it's working well with keyboard, but the screen Reader user has no idea what was happened when he/she clicked on it, i.e wether it is expanded or closed.
using well heading markup will help once the Screen Reader user used the content couple of times. so i suggest you to convey the user the state of hte widget. one way of doing it is ARIA. ofcourse older browser browsers doesn't support ARIA still atleast some users can receive well accessible information.
On Sat, Apr 2, 2011 at 2:25 AM, Angela French < = EMAIL ADDRESS REMOVED = > wrote:
>
> Hello,
> I am hoping that a screen reader user on this list would be willing to
> test the accessibility of this jQuery/CSS expanding content implementation.
>
> http://www.sohtanaka.com/web-design/examples/toggle/bad.htm
>
> Thank you very much,
>
>
> Angela French
> Internet Specialist
> State Board for Community and Technical Colleges
> 360-704-4316
> = EMAIL ADDRESS REMOVED =
> http://www.checkoutacollege.com<;http://www.checkoutacollege.com/>;
>
>
From: Patrick Burke
Date: Thu, Apr 07 2011 2:39PM
Subject: Re: can screen reader user please test expanding content?
← Previous message | Next message →
Hi Greg,
I'm another screen reader user, somewhat late to
this party ... (Jaws 12, Firefox 4.)
The biggest difference on the two U of Illinois
pages is that the ARIA markup lets the screen
reading software know that these are not normal
links (see Birkir's original comments). The first
page identifies Crust, Veggies etc. as "tabs".
The second example includes a message such as
"Delivery Tab, expanded Delivery", announcing the
state of each tab. (Although at first "collapsed
crust" sounds like a baking mishap, not a markup status message...)
The keyboard commands described on the example
pages work to allow extra maneuvering within the tab sets.
Hope that's useful,
Patrick
At 08:23 AM 4/6/2011, Greg Gamble wrote:
>Hello All,
>
>I'm the one who asked Angela to send a request
>for the Screen reads help ( no account at the time )
>
>I have a couple of questions, sorry if they've been answered before ...
>
>So when a person using a screen reader
>encounters an accordion type of control, where
>the content is hidden from a sited user but is
>still visible in the source, they cannot see
>inside of them or know when they are opening?
>Reading up on support for ARIA lead me to the following ...
>
>I found this on handling some of the issues that have been brought up:
>http://test.cita.illinois.edu/aria/tabpanel/tabpanel1.php
>
>http://test.cita.illinois.edu/aria/tabpanel/tabpanel2.php
>
> ... do these examples work better than the
> original example, as far as letting a screen
> reader user know what is happening?
>
>http://www.sohtanaka.com/web-design/examples/toggle/bad.htm
>
>Greg Gamble
>SBCTC - Olympia | Information Services
>p - 360-704-4376
>ï think before printing
>
>
>-----Original Message-----
>From: = EMAIL ADDRESS REMOVED =
>[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Jeevan Reddy
>Sent: Tuesday, April 05, 2011 1:10 AM
>To: WebAIM Discussion List
>Subject: Re: [WebAIM] can screenreader user please test expanding content?
>
>Hi Angela,
> The Markup is fine, still the symantics
> of this Jquery/CSS expanding content is not conveyed to AT.
>I've tested with NVDA V2011.1 on Firefox 3.6 and Windows 7.
>it's working well with keyboard, but the screen
>Reader user has no idea what was happened when
>he/she clicked on it, i.e wether it is expanded or closed.
>
>using well heading markup will help once the
>Screen Reader user used the content couple of
>times. so i suggest you to convey the user the
>state of hte widget. one way of doing it is
>ARIA. ofcourse older browser browsers doesn't
>support ARIA still atleast some users can receive well accessible information.
>
>On Sat, Apr 2, 2011 at 2:25 AM, Angela French < = EMAIL ADDRESS REMOVED = > wrote:
>
> >
> > Hello,
> > I am hoping that a screen reader user on this list would be willing to
> > test the accessibility of this jQuery/CSS
> expanding content implementation.
> >
> > http://www.sohtanaka.com/web-design/examples/toggle/bad.htm
> >
> > Thank you very much,
> >
> >
> > Angela French
> > Internet Specialist
> > State Board for Community and Technical Colleges
> > 360-704-4316
> > = EMAIL ADDRESS REMOVED =
> > http://www.checkoutacollege.com<;http://www.checkoutacollege.com/>;
> >
> >
From: Birkir R. Gunnarsson
Date: Thu, Apr 07 2011 3:45PM
Subject: Re: can screen reader user please test expanding content?
← Previous message | No next message
Hi Angela
I have to dig up the Display:None answer some time, not 100% sure what
you are asking for there.
The biggest drawback, as previously noted, is that I cannot see that
these links are anything special and I can easily see a user hittig
nter on them, no new page opens, and then user decides the links do
not do anything.
May be the link text can say (hit enter to expand), or you could use
ARIA to make the content descriptions better.
I concurr with Patrick on the ARIA sample. Use of ARIA is not too
widespread yet, I have a feeling it is certainly not fully and
consistently implemented in many browsers or screen readers, but we
have to start somewhere.
Thank you
-Birkir
On 4/7/11, Patrick Burke < = EMAIL ADDRESS REMOVED = > wrote:
> Hi Greg,
>
> I'm another screen reader user, somewhat late to
> this party ... (Jaws 12, Firefox 4.)
>
> The biggest difference on the two U of Illinois
> pages is that the ARIA markup lets the screen
> reading software know that these are not normal
> links (see Birkir's original comments). The first
> page identifies Crust, Veggies etc. as "tabs".
> The second example includes a message such as
> "Delivery Tab, expanded Delivery", announcing the
> state of each tab. (Although at first "collapsed
> crust" sounds like a baking mishap, not a markup status message...)
>
> The keyboard commands described on the example
> pages work to allow extra maneuvering within the tab sets.
>
> Hope that's useful,
>
> Patrick
>
> At 08:23 AM 4/6/2011, Greg Gamble wrote:
>>Hello All,
>>
>>I'm the one who asked Angela to send a request
>>for the Screen reads help ( no account at the time )
>>
>>I have a couple of questions, sorry if they've been answered before ...
>>
>>So when a person using a screen reader
>>encounters an accordion type of control, where
>>the content is hidden from a sited user but is
>>still visible in the source, they cannot see
>>inside of them or know when they are opening?
>>Reading up on support for ARIA lead me to the following ...
>>
>>I found this on handling some of the issues that have been brought up:
>>http://test.cita.illinois.edu/aria/tabpanel/tabpanel1.php
>>
>>http://test.cita.illinois.edu/aria/tabpanel/tabpanel2.php
>>
>> ... do these examples work better than the
>> original example, as far as letting a screen
>> reader user know what is happening?
>>
>>http://www.sohtanaka.com/web-design/examples/toggle/bad.htm
>>
>>Greg Gamble
>>SBCTC - Olympia | Information Services
>>p - 360-704-4376
>>ï think before printing
>>
>>
>>-----Original Message-----
>>From: = EMAIL ADDRESS REMOVED =
>>[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Jeevan Reddy
>>Sent: Tuesday, April 05, 2011 1:10 AM
>>To: WebAIM Discussion List
>>Subject: Re: [WebAIM] can screenreader user please test expanding content?
>>
>>Hi Angela,
>> The Markup is fine, still the symantics
>> of this Jquery/CSS expanding content is not conveyed to AT.
>>I've tested with NVDA V2011.1 on Firefox 3.6 and Windows 7.
>>it's working well with keyboard, but the screen
>>Reader user has no idea what was happened when
>>he/she clicked on it, i.e wether it is expanded or closed.
>>
>>using well heading markup will help once the
>>Screen Reader user used the content couple of
>>times. so i suggest you to convey the user the
>>state of hte widget. one way of doing it is
>>ARIA. ofcourse older browser browsers doesn't
>>support ARIA still atleast some users can receive well accessible
>> information.
>>
>>On Sat, Apr 2, 2011 at 2:25 AM, Angela French < = EMAIL ADDRESS REMOVED = > wrote:
>>
>> >
>> > Hello,
>> > I am hoping that a screen reader user on this list would be willing to
>> > test the accessibility of this jQuery/CSS
>> expanding content implementation.
>> >
>> > http://www.sohtanaka.com/web-design/examples/toggle/bad.htm
>> >
>> > Thank you very much,
>> >
>> >
>> > Angela French
>> > Internet Specialist
>> > State Board for Community and Technical Colleges
>> > 360-704-4316
>> > = EMAIL ADDRESS REMOVED =
>> > http://www.checkoutacollege.com<;http://www.checkoutacollege.com/>;
>> >
>> >