WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Interaction with tab panels

for

From: _mallory
Date: Aug 9, 2016 5:28AM

I'm confused, why is an anchor with a role of "button" better than
a button? I vaguely recall something about working cross-browser...
is there a browser who won't work with real buttons?

_mallory

On Fri, Aug 05, 2016 at 05:15:13PM +0000, Bryan Garaventa wrote:
> I'm glad that helped, we are currently discussing these differences so they can be added to the APG 1.1 document for Accordion, reference
> https://lists.w3.org/Archives/Public/public-aria/2016Jul/0172.html
>
> Going forward, the most accessible implementation recommended for a basic Accordion is the design pattern demonstrated at
> http://whatsock.com/test/w3c/ARIA%20Accordions/demo.htm
>
> Which can be easily implemented using the demo code at
> http://whatsock.com/test/w3c/ARIA%20Accordions.zip
>
> Kind regards,
> Bryan
>
>
> Bryan Garaventa
> Accessibility Fellow
> SSB BART Group, Inc.
> <EMAIL REMOVED>
> 415.624.2709 (o)
> www.SSBBartGroup.com
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Vemaarapu Venkatesh
> Sent: Thursday, August 04, 2016 10:21 PM
> To: <EMAIL REMOVED>
> Subject: Re: [WebAIM] Interaction with tab panels
>
> Bryan,
>
> After a bit of work around that, I seriously got the conclusion that it is not tab panel but accordians. Here what made my life harder was aria-tab roles are used while designing these accordians. This makes user to live in fool's world as no differentiation is provided even though they are two different custom widgets. I always tried to interact with the panel keeping tablist in view but never bothered to consider that as accordians. Actually I came across this type of scenario for the first time and really confused with the reading order.
> Thank you Bryan for your precise explanation of these widgets.
>
> As experts discussed here, mode of interaction is differs with the same widget in different cases provided with different apps. Really it will be very difficult to teach someone if they arrives to us with these change of behaviors. I think keeping different projections and resolutions in view there should be some legal standards regarding these interaction modes like WCAG 2.0, I mean to say there should be only one way of interaction if we consider any component.
> I don't think so WCAG 2.0 will talk about modes of interaction with the different elements. Please let me know if any such standards exists as I am not aware of it. Can I consider APG as such standards and can I raise any violations pointing towards APG. Also correct me if WCAG 2.0 talks about modes of interaction.
>
> Regards,
> venkatesh
>
> On Thu, Aug 4, 2016 at 8:49 AM, Vemaarapu Venkatesh < <EMAIL REMOVED> > wrote:
>
> > Bryan, I found interaction is perfect with tab panel in the mentioned
> > pages by you. In the first page, tab items are selected with the focus
> > and in the second page first tab item is expanded as soon as receiving
> > the focus. In two pages, interaction is possible only with arrow keys
> > inside tab panel and tab key wont take us to next tab item.
> > But in my case tab items are in collapsed state even after taking the
> > focus to the tab panel and my main concern is "navigation is moving to
> > other tab items in the list when we hit tab key when all items are
> > collapsed". Is it fine like that.
> > Please referhttps://support.skype.com/en/faq/fa109/i-ve-
> > forgotten-my-username-or-password
> > I am using NVDA+Firefox. Hope I am clear.
> > Regards,
> > venkatesh
> >
> >
> > On Wed, Aug 3, 2016 at 8:12 PM, Vemaarapu Venkatesh <
> > <EMAIL REMOVED> > wrote:
> >
> >> Hello all, Greetings
> >>
> >> If we consider tab panel, we should use arrow keys to interact with
> >> tabs inside the widget if I am not wrong.
> >>
> >> https://support.skype.com/en/faq/fa109/i-ve-forgotten-my-
> >> username-or-password
> >>
> >> When I interacted with the tab panel present in the above link, I
> >> observed 1. When all tabs are in collapsed state, I hit tab to enter
> >> into tab panel. Then I thought that focus moves out of tab panel to
> >> "Yes" button if I hit tab key once again. But navigation continues in
> >> tab panel i.e the other two tab items are in tab order. This behavior
> >> is not seen when any one of tab items is expanded.
> >> I feel that interaction inside the tab panel should be only with
> >> arrow keys but not with tab key anytime.
> >> 2. If I am expanding any tab item, the already selected tab item is
> >> not getting collapsed automatically. User has to collapse and expand manually.
> >>
> >> Whether these two behaviors are recommendable when I am interacting
> >> with tab panel widget.
> >>
> >> Hope you will correct me if I am going wrong with my perception.
> >>
> >> Regards,
> >> venkatesh
> >>
> >
> >
> > > > > > >