WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Mobile view different source code order

for

From: glen walker
Date: Sep 6, 2018 8:10AM

1. For 3.2.3, it just says to be consistent "within a set of web pages", so
you don't have to compare your desktop layout to your mobile layout.

2. That depends if you are using ARIA to make it a real menu by using
role="menu" and role="menuitem". If so, then the arrow keys must be used
to navigate the menu. If your "menu" is just a list of links, then tabbing
through the links is correct. Most people implement navigation menus as
lists of links so the arrow keys are not used. If you had a list of
actions, that's typically implemented as a real menu with role="menu" (or
menubar).

Whether you have headings and sections in your menu is tough to comment on
without further info. It's usually sufficient to have lists and sublists.

Glen


On Wed, Sep 5, 2018 at 11:15 PM Karin Carlson < <EMAIL REMOVED> >
wrote:

> Hi everyone. I'm giving the developers of a small app feedback on the
> app's accessibility. One of the main screens has links in groupings to
> navigate to subpages. They are arranged on the page in a sort of
> three-column format with text above every three or four links. They made
> each group of associated links into sections with ARIA labels.
> When the browser window is narrow enough that the app goes into Mobile
> mode, there is a new button that is labeled "menu" that is first in the tab
> order that opens all of the navigation sections in a sort of side menu. All
> of the options available on the main page are available in the side menu,
> but they are in a different order then the options on the main page.
> My questions1-- When deciding if a website or application has consistent
> navigation between pages, are you comparing only all of the mobile versions
> with other mobile versions, or do things have to match between mobile and
> regular?
> 2-In the mobile mode, when the navigation elements are functioning as a
> menu, you can't arrow key down into the choices immediately, but have to
> tab through the entire contents of the page and then it jumps to the second
> item in the menu. The sections also still exist in the menu, which I think
> is not the way a menu should be built. Is there ever a time to use headings
> and sections and buttons inside of a menu?
> Thanks,
> Karin Sent from my Samsung Galaxy smartphone.
> > > > >