Re: Some thinking around the orientation discussion

I agree... it is a good point in a responsive world where sections get
dropped off ... do you have some proposed language?

 I'm wondering what type of mechanism we might propose to notify a user of
what is gone from a page and how to get it back...

The Cognitive team have looked at simplifying interfaces dropping off
content that is not central to the point of the page, that might be
pertinent to this success criteria

They proposed an attribute "@aria-importance": {"high"}
This might be an area we would want to stay in close contact with them
about...

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*
Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Thu, May 5, 2016 at 7:42 PM, Patrick H. Lauke <redux@splintered.co.uk>
wrote:

> On 05/05/2016 17:50, David MacDonald wrote:
>
>> Added to WIKI
>>
>> https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_revision_of_3.4.1
>>
>
> I was going to comment on the line about "Changes in orientation must be
> programmatically exposed", but I see that in the latest edit on the wiki
> that has been removed. Just to say I approve of this, partially because
> it's usually the domain of the OS/AT to announce an orientation change.
>
> I *can* see that in certain situations it would be useful to announce to
> the user if something changed in the current page/view as a result of an
> orientation change (e.g. a completely different layout is introduced with
> more/less navigation options, functionalities, etc), but this is probably
> something that falls under the need to have a more generic "if parts of the
> page change, this change should be announced to the user" SC (which, at
> least for interface components, is probably covered by 4.1.2, but not for
> non-user-interface cases.
>
> For this latter part, is it worth proposing/thinking about another SC
> (which is, once again, not really "mobile" specific)?
>
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>
>