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

Alastair, the following is not clear yet:

> 6. Using flexible text input form control (new)

I think this was recognising that inputs can be an issue, as 320px is not huge for a text-box, so something that shows it can be limited to 100% wide, with a label that moves above it at smaller sizes.

=> Can be an issue (which issue exact?) as 320px is not huge for a text-box (where does the 320 in this case comes from?) so something that shows it can be limited to 100% wide(width: 100% in CSS… depending on parent container?) with a label that moves above it at smaller sizes (like here in my portal: https://a11yportal.com/good-bad/request.html ??? Still in draft by the way)

Cheers!

From: Alastair Campbell [mailto:acampbell@nomensa.com]
Sent: maandag 17 september 2018 18:37
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,

> Just went through the techniques as proposed but the exact wish for the suggested ones and the conditions are not always clear enough.

The titles were sourced from the Understanding docs and may well need adjustment.


> As an example take the first on my list below: “Using CSS to set the orientation to allow both landscape and portrait.”
…
> Also how do you “Set the orientation”, it’s the way you hold your device isn’t it, not set by CSS.

Given where that SC ended up, it might be better translated to a failure technique.

I guess there is the possibility of having an interface that provides the option to set (i.e. lock) the orientation if the user wants to do that, but the failure technique seems like a more obvious starting point.


> 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?)

I think they would be good questions for the Mobile TF, I can guess what they were intended to be, but they were the source.


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

We have ARIA instances of landmark techniques, we can link to those for now. (Alastair writes down  an understanding doc update.)


> 3. Marking up icons (Assigned to TBC )

Unless we can get one of the examples used for accessibility support testing, I’d leave this one for now. It would take a fair bit of work & writeup.


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

This one is basically using something like img {max-width: 100%;} to ensure images don’t cause scrolling.

If something like a map is picked (where a tiny version may be difficult to understand), a best practice could be to include a link to the full size version, where the user can then zoom & scroll.


> 6. Using flexible text input form control (new)

I think this was recognising that inputs can be an issue, as 320px is not huge for a text-box, so something that shows it can be limited to 100% wide, with a label that moves above it at smaller sizes.

> 7. Mechanism to allow mobile view at any time (new)

Where the site is not responsive, but allows you to pick the ‘mobile’ view, essentially a link to the m.example.com version. Probably just a description rather than example.

-Alastair

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