RE: Techniques, a Note! and preference to pick up next

Alastair / all,

Just went through the techniques as proposed but the exact wish for the suggested ones and the conditions are not always clear enough. It would be great to provide a small description, and if needed some conditions to get started.

As an example take the first on my list below: “Using CSS to set the orientation to allow both landscape and portrait.”
Is that a technique? Blocking on orientation is, but just using CSS is by default fine for landscape/portrait… ?! What is the idea here? Also how do you “Set the orientation”, it’s the way you hold your device isn’t it, not set by CSS.

So I would like to take on a couple of techniques but would appreciate it if they are a bit more explained by the ones who suggested them:

1.3.4

1. Using CSS to set the orientation to allow both landscape and portrait. (Assigned to TBC )

2. Use of show/hide controls to allow access to content in different orientations. (Assigned to TBC )

3. Use of the flexible box model to change the meaningful sequence order of content to match the visual order in different orientations. (Assigned to ) (Shouldn't this be a failure? Example?)

1.3.6

2. Use of landmarks (Assigned to TBC )Status: New (do we have one already?) => My Examples?

3. Marking up icons (Assigned to TBC )

1.4.10

3. CSS, Fitting images to the viewport; (new) (Assigned to Jake Abma )
Status: New

6. Using flexible text input form control (new)
Status New

7. Mechanism to allow mobile view at any time (new)
Status: New

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



From: Alastair Campbell [mailto:acampbell@nomensa.com]
Sent: dinsdag 11 september 2018 13:24
To: Abma, J.D. (Jake) <Jake.Abma@ing.com>
Cc: WCAG <w3c-wai-gl@w3.org>
Subject: Re: Techniques, a Note! and preference to pick up next

Hi Jake,

If there isn’t a known & useful technique for reflowing tables I’m happy to leave that for now, there’s an exception for tablular data.

For the fitting to viewport, have you found issues with applying max-width: 100% or 100vw to a cell?

It is advisory rather than sufficient, so it’s probably best to focus on a sufficient techniques anyway.

In terms of prioritisation, I’d look at which you are happy to tackle, then prioritise by: Level A sufficient, Level A failure, Level AA sufficient, Level AA failure etc.

I think you’d find these relatively easy to get done:

-          1.3.4: Failure: Locking the orientation.
-          1.4.10: CSS, Fitting images to the viewport (3)

And I’m sure there are more!

Thanks,

-Alastair


From: "Abma, J.D. (Jake)" <Jake.Abma@ing.com<mailto:Jake.Abma@ing.com>>
Date: Tuesday, 11 September 2018 at 11:31
To: Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>>, Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>, WCAG list <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: 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<mailto: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.

-----------------------------------------------------------------

-----------------------------------------------------------------
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.
-----------------------------------------------------------------