Re: New possible SC: All functionality available in portrait / landscape, OR not?

The Force Orientation simply disables the detection of orientation. This
feature is designed to keep content from changing randomly, NOT to force
content to be in a particular orientation state.

On Thu, May 2, 2019 at 9:26 AM Michael Gower <michael.gower@ca.ibm.com>
wrote:

> David, obviously there's not a lot of info here, but it just looks to me
> like the OS ignoring any sensor information in regard to rotation. This
> lock already exists in iOS and I think you're confusing this OS feature
> with an author-controlled forced orientation. This would be ineffective at
> resolving display where the author only designed the opposite orientation.
>
> > if your app has any customized rotation behavior or uses any unusual
> screen orientation settings, you might run into issues that would have gone
> unnoticed before, when user rotation preference was always set to portrait
>
>
> Michael Gower
> Senior Consultant in Accessibility
> IBM Design
>
>
> 1803 Douglas Street, Victoria, BC  V8T 5C3
> gowerm@ca.ibm.com
> cellular: (250) 661-0098 *  fax: (250) 220-8034
>
>
>
> From:        David MacDonald <david100@sympatico.ca>
> To:        Chris McMeeking <chris.mcmeeking@deque.com>
> Cc:        Jonathan Avila <jon.avila@levelaccess.com>, "Patrick H. Lauke"
> <redux@splintered.co.uk>, Michael Gower <michael.gower@ca.ibm.com>,
> Detlev Fischer <detlev.fischer@testkreis.de>, "Abma, J.D. (Jake)" <
> Jake.Abma@ing.com>, "public-mobile-a11y-tf@w3.org" <
> public-mobile-a11y-tf@w3.org>
> Date:        2019-05-02 06:19 AM
> Subject:        Re: New possible SC: All functionality available in
> portrait / landscape, OR not?
> ------------------------------
>
>
>
> Interesting new feature in Android.
>
> "To eliminate unintentional rotations, we've added a mode that pins the
> current orientation even if the device position changes. Users can trigger
> rotation manually when needed by pressing a button in the system bar."
>
> I find this interesting because it allows users to override the forced
> orientation. So if the DEV locks orientation this way, it would allow the
> default mode to persist, and most users without disabilities would simply
> turn the device back to portrait, while someone on a wheelchair mounted
> system, could activate the button to change the orientation and it would be
> in the "ugly but functional horizontal view". I could see selling this to
> some corporate customers whereas no locking at all might be a non starter.
> *https://developer.android.com/about/versions/pie/android-9.0#rotation*
> <https://developer.android.com/about/versions/pie/android-9.0#rotation>
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
>
> Tel:  613-806-9005
>
> *LinkedIn * <http://www.linkedin.com/in/davidmacdonald100>
>
> *twitter.com/davidmacd* <http://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 Wed, May 1, 2019 at 1:58 PM Chris McMeeking <
> *chris.mcmeeking@deque.com* <chris.mcmeeking@deque.com>> wrote:
> Here's a diagram to help.
>
>
> On Wed, May 1, 2019 at 1:46 PM Chris McMeeking <
> *chris.mcmeeking@deque.com* <chris.mcmeeking@deque.com>> wrote:
> > clients will simply not want an "ugly but functional" experience
>
> Then this Success Criteria is no different from other Success Criteria
> that involve design changes and companies should consider Accessibility
> Early on in their development cycles.
>
> > Chris does this provide gutter space on the right if a portrait app was
> turned to Landscape, or does everything reorient including spacing to fill
> out the entire width. How easy is it to just keep the portrait view and
> throw in the correct black gutter space across dozens of form factors?
>
> This is not reality. If left alone, what you're going to get is the
> content rendering completely across this screen, with simply more scrolling
> necessary.
>
> The "Design Difficulties" come into play when you have content that you
> want rendered to the user without scrolling. There is significant research
> that shows that users are X% (all stats are made up) more likely to engage
> with things already on screen, and that they won't scroll.
>
> Well coded content, and I'm not gonna lie, I couldn't give a rats patoot
> about developers that use absolute, hard coded design layouts. But, well
> structured content will render just fine in Portrait and Landscape.
> HOWEVER, you end up needing to scroll to more content, because the
> Landscape version of that content is going to expand to fill the screen,
> and require more scrolling.
>
> As such, research and design aware companies would do things like render
> menus to the side and shrink the main content. Or add FABs or trays for
> important features that they want to be available and visible to the user
> without scrolling.
>
> The content won't be "ugly" unless their developers are morons.
>
> Chris
>
>
> On Wed, May 1, 2019 at 12:55 PM Jonathan Avila <
> *jon.avila@levelaccess.com* <jon.avila@levelaccess.com>> wrote:
> Many apps have tab bar buttons at bottom   To keep these always in view
> you would need to switch to vertical placement.   This wouldn't be required
> for current SC but would be ideal.
>
> Jon
>
> Sent from my iPhone
>
> On May 1, 2019, at 10:22 AM, David MacDonald <*david100@sympatico.ca*
> <david100@sympatico.ca>> wrote:
>
> *CAUTION:*This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
> Michale G says:
>
> > Worse case scenario to meet the SC is the app will not change dimensions
> at all and you just get the same layout with a lot of gutter/whitespace in
> the other orientation.
>
> My guess is that Chris's solution doesn't do that.
>
>  "unlock the configuration, attach a ScrollView to your main content, and
> let your view readjust to the viewport change."
>
> Chris does this provide gutter space on the right if a portrait app was
> turned to Landscape, or does everything reorient including spacingto fill
> out the entire width. How easy is it to just keep the portrait view and
> throw in the correct black gutter space across dozens of form factors?
>
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
>
> Tel:  613-806-9005
>
> *LinkedIn * <http://www.linkedin.com/in/davidmacdonald100>
>
> *twitter.com/davidmacd* <http://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 Wed, May 1, 2019 at 9:57 AM Patrick H. Lauke <*redux@splintered.co.uk*
> <redux@splintered.co.uk>> wrote:
>
> On 01/05/2019 14:51, Michael Gower wrote:
> > But an 'ugly but functional' design in the alternate orientation is a
> > whole lot better
>
> I'll echo DMcD here though and say that most brand-aware/corporate
> clients will simply not want an "ugly but functional" experience
> (particularly one that can be triggered so easily by end users) unless
> absolutely forced to (which, until the introduction of this SC, they had
> no normative incentive to do).
>
> P
> --
> Patrick H. Lauke
>
> *www.splintered.co.uk* <http://www.splintered.co.uk>|
> *https://github.com/patrickhlauke* <https://github.com/patrickhlauke>
> *http://flickr.com/photos/redux/* <http://flickr.com/photos/redux/>|
> *http://redux.deviantart.com* <http://redux.deviantart.com>
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>
>