Re: [HTML-AAM] effect of CSS display and tabindex on <span>

Steve, out of curiosity do you have any data about dispaly:table usage?


On Wed, May 13, 2015 at 4:48 AM, _mallory <stommepoes@stommepoes.nl> wrote:

> It should be noted however that many, maybe most developers who are
> using (for example) display: table are not trying to convey table
> semantics at all, but merely want even automatic spacing and
> vertical alignment and maybe also collapsed borders.
>
> When I use this trick for a navigation menu, I want users to know
> it's the menu I HTML'd in there.
>
> Or does anyone have numbers showing that, at least for display:
> table, that in fact there are a majority making actual tables
> from divs and then styling them as tables with display: table?
>
> One use case I can think of for that might be backwards-done
> "responsive tables" where it's not a table (for mobile/small screens)
> and gets styled as a table when screens have the room to show them.
> But I did not think this was a majority use, in fact I haven't
> seen it anywhere (yet).
>
> Display: none and visibility: hidden seem to be a different area,
> maybe because they've been passed on by browsers since almost
> forever and everyone seems to know it now.
>
> _mallory
>
> On Tue, May 12, 2015 at 02:57:10PM -0400, Alexander Surkov wrote:
> > In Firefox we rely much on layout. If something was rendered as a table
> > then it's exposed as table on accessibility layer too. There are strong
> > voices that CSS display shouldn't affect on content semantics because the
> > author has ARIA for that, and I find this argument reasonable. On the
> other
> > hand this approach may harm web apps that don't use much ARIA and relies
> on
> > the browser to get some a11y for free. I would love to have consistency
> > here, I'm not sure though how it can be achieved.
> > Thanks.
> > Alexander.
>