Comment Summary 2-6-2

Orientation

Draft: Current: Content is not locked to a specific display orientation, and functionality of the content is operable in all display orientations, except where display orientation is essential for use of the content.

Proposed: A mechanism is available to view and operate content in portrait and landscape orientation, except where a specific display orientation is essential. (delete definition)

Document in understanding the issue about small iOS devices not supporting rotation fully and that resulting in forcing users to use the device in portrait mode. App devs can support this, even if the OS doesn't. Document that "essential" includes limitations of hardware, implementation (e.g. kiosk, seatback displays)

Issues:

Issue 509: Response ?? Sent to Steve

Issue 496: Response...we are documenting in the Understanding. App developer can build to this requirement, even if the OS (iOS) doesn't.

Issue 465: Response same as 496

Issue 461: Response this is actually about the new definition, but we reverted back to the previous WCAG 2.0 version. Closed

Issue 361: Response we believe we have under Additional Sensor input..... Closed.

Issue 360: Response we defined them in the SC does not refer to locking orientation but the assurance of content can be displayed under both orientations.

Issue 336: Response The bulk of your content refers to a now changed version of Essential definition and we will update in the Understanding document.

Issue 265: Response Closed

Issue 193: Response (same as 496, 465)...we are documenting in the Understanding. App developer can build to this requirement, even if the OS (iOS) doesn't.

Link to Open Issues on GitHub

http://github.com/w3c/wcag21/issues?q=is%3Aissue+is%3Aopen+label%3A~comment-orientation