WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Tab controls and WCAG 1.4.10 Reflow

for

From: Niranjan Vala
Date: Mar 31, 2022 1:36AM

I also think that horizontal tabs should be made responsive for all screen
sizes so it meets with the Reflow WCAG success criterion. For smaller
screen sizes, it should be vertically stacked and for bigger screens, It
can be aligned horizontally. In fact that is what I have seen on many
popular websites that uses tabs. There could be another approach in which
tabs with only icons with proper hidden but accessible labels can be used
so they can be aligned horizontally even on smaller screen sizes.

On Thu, 31 Mar 2022 at 11:31, Steve Green < <EMAIL REMOVED> >
wrote:

> This exact issue came up last week in an IAAP discussion, and our team
> discussed it internally for more than an hour. It seems simple at first,
> but it raises the question of what "scrolling" means, among other things.
> The WCAG authors must have assumed it's obvious, because they do not
> provide a definition.
>
> Opinion was split, both in IAAP and in our team. My view is that a Tab
> component does not require two-dimensional layout, and that the tabs can
> perfectly well wrap onto two or more lines. Indeed, I failed one of our
> clients' sites on this exact issue.
>
> Steve Green
> Managing Director
> Test Partners Ltd
>
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> Laurence Lewis
> Sent: 31 March 2022 06:53
> To: <EMAIL REMOVED>
> Subject: [WebAIM] Tab controls and WCAG 1.4.10 Reflow
>
> Hello
>
> I have a situation where a Tab component design had multiple tabs
> horizontally. If the screen is resized, or zoomed, some of the tabs are
> hidden from view in the sized container div. In some cases the tab name can
> be truncated with half the tab in view.
>
> The tabs can be scrolled in the container which opens other problems,
> however for WCAG 2.2 I think this will be a Visible Controls fail. but, is
> this a Reflow fail? I believe it may be because a Tab component does nor
> require a two-dimensional layout to be meaningful and thus the Tabs can be
> stacked in view.
>
> I would like to hear the opinion of other A11y people on potential
> accessibility issues.
>
>
> All the best
> Laurence
> Digital Accessibility Senior Specialist Telstra
> > > at http://webaim.org/discussion/archives
> > > > > >


--
Cheers,

Niranjan G Vala