WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Mobile view different source code order

for

From: Guy Hickling
Date: Sep 7, 2018 6:05PM

Karin, I would flag it as bad for usability and user experience for all
users, rather than an accessibility defect for disabled people only, if
they see one menu order on their desktops then a different order on their
mobiles. That's confusing, and may even cause some to wonder if they are
missing some options on the mobile.

It can also be poor accessibility. Suppose someone with poor eyesight has
their text size set to a larger size in their browsers, a size that's close
to triggering the mobile layout, but not quite there. Then they find
something on your website they can't quite see so they zoom. Now all of a
sudden the menu order has changed! Again confusing. Users are used to menus
being replaced by the hamburger icon at different zooms, but do expect
everything to be more or less the same options inside that. So I think it's
poor accessibility experience for them, but I agree with what Glen has
just said, I can't think of anything in the WCAG that is infringed.

For your second query, "...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 ", if I am understanding you correctly that sounds to me
rather dire. Something I would raise under SC1.3.1, but perhaps you can
give us more detail so we can get a better understanding of that question?
Is it really leaving the menu and tabbing through the entire page before
going back to the menu?

Regards,
Guy Hickling