Techniques, a Note! and preference to pick up next

Hi everyone,

First a Note!:  At https://www.w3.org/WAI/GL/wiki/Wcag21-techniques I see:


*         1.4.10 => 4. CSS, Reflowing simple data tables.(new)

*         1.4.10 => 5. CSS, Fitting data cells within the width of the viewport. (new)

I'm wondering if this is all about changing display of cells and table. If so we should NOT do these ones as there's no proper accessible way to do this.
Using table display: inline, cell display: block and pseudo classes all do only half the job and cause other issues like not being recognised by SR and arrow keys in table mode not logically going to the expected rows/cells.
All so called "accessible tables" out there on the internet are sadly not accessible at all.
I do have a complex idea to do this with re-ordering elements in a very custom way by using lots of ARIA and JavaScript, but this is not a simple example and surely not a CSS approach.
So I suggest these to be removed and not burn our fingers.

Second I can pick up one of the following techniques but wonder if we do have some sort of preference?


*         1.3.4 => 1/2/3

*         1.3.6 => 2/3

*         1.4.10 => 3/6/7

*         1.4.11 => 1/2/3/4

*         1.4.13 => 1/2

*         2.5.5 => 1

Regards,
Jake Abma

Accessibility Lead ING
Product owner at Team A11Y
http://www.a11yportal.com<http://www.a11yportal.com/>

ING Nederland / CIO / Omnichannel / Experience
ACT C.02.406, Bijlmerdreef 24
Postbus 1800, 1000 BV Amsterdam
0031 (0)6 - 25 27 52 46
jake.abma@ing.com


-----------------------------------------------------------------
ATTENTION:
The information in this e-mail is confidential and only meant for the intended recipient. If you are not the intended recipient, don't use or disclose it in any way. Please let the sender know and delete the message immediately.
-----------------------------------------------------------------

Received on Tuesday, 11 September 2018 10:31:39 UTC