Re: Discussion: Change to SC 2.6.2 Orientation

Hi Jason, 
I do understand that exceptions or qualifications to a requirement need to be part of the SC text.
But as I understand it, the intended requirement is fully expressed in what Alastair suggests ("Content does not restrict the orientation unless one display orientation is essential") and has nothing to do with mechanisms for locking / switching. If instead we say something like "A mechanism is available to view and operate content in all display orientations" this can easily be construed by developers as a requirement to include a mechanism on the web page that would be neither necessary nor desirable in most cases. So we start an author requirement by stating something that is normally the OS's business. That seems like a bad design choice to me.
Detlev

--
Detlev Fischer
testkreis c/o feld.wald.wiese
Thedestr. 2, 22767 Hamburg

Mobil +49 (0)157 57 57 57 45
Fax +49 (0)40 439 10 68-5

http://www.testkreis.de
Beratung, Tests und Schulungen für barrierefreie Websites

White, Jason J schrieb am 18.10.2017 18:18:

> 
> 
>> -----Original Message-----
>> From: Detlev Fischer [mailto:detlev.fischer@testkreis.de]
>> Sent: Wednesday, October 18, 2017 12:04 PM
>> Sure, it would be. I would just prefer to see that in the Understanding doc
>> and
>> not overload the SC text too much. But if others think it has to be done, so
>> be it..
> [Jason] If an exception or qualification to a requirement isn't in the text of
> the SC, then it doesn't exist for normative purposes. The Understanding
> document can't alter the normative implications of the text of WCAG, so you
> can't put exceptions in there or qualify the meaning of a requirement in a way
> that isn't provided for in the SC text.
> 
> 
> ________________________________
> 
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom it is
> intended, even if addressed incorrectly. If you received this e-mail in error,
> please notify the sender; do not disclose, copy, distribute, or take any action
> in reliance on the contents of this information; and delete it from your
> system. Any other use of this e-mail is prohibited.
> 
> 
> Thank you for your compliance.
> 
> ________________________________
>

Received on Wednesday, 18 October 2017 16:51:39 UTC