- From: David MacDonald <david100@sympatico.ca>
- Date: Wed, 12 Jul 2017 10:33:02 -0400
- To: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
- Message-ID: <CAAdDpDZe=rD=qRA2rLp_ZSpCTW2nEXQyPX1NguKj7tupHKf8AQ@mail.gmail.com>
Yesterday we came to a consensus that it is worth exploring moving the proposed SCs, 62, 63, 71 to the conformance section. This is a start to that conversation. === SC's in question === #62 Keyboard with AT: All functions available by keyboard are still available by keyboard after accessibility-supported assistive technology that remaps keystrokes is turned on. #63 Touch with AT: All functions available by touch are still available by touch after platform assistive technology that remaps touch gestures is turned on. #64 Non-interference with AT: Content does not interfere with the normal operation of the platform assistive technology, or a mechanism is available to override the interference, unless: it is essential for use of the content, and the user is warned before using the component. === Summary of SC Requirements === - #62 Is largely covered by 2.1.1 but it adds a requirement for keyboard to work when Platform screen readers such as VoiceOver are enabled - #63 requires everything to still work when platform screen readers are enabled - #64 Requires that the content not interfere with the operation of platform screen readers. The proposal is to sum up all of these in the conformance section by ensuring that the definition of a page, includes different versions of the page that are delivered based on the size of the screen. H A paragraph would be added to the conformance section something like this: ===Proposed addition to conformance === The full page includes each variation of the page that is automatically generated by the content for various screen sizes. Each of these variations (or their respective conforming alternate versions) needs to conform in order for the entire page to conform. However, if a user actively chooses a setting on the page that optimizes or personalizes the state of the page for accessibility reasons, this new state does not necessarily need to conform, because the conforming version can be reached by undoing the setting. **************** It would be placed after the last paragraph in the section "Understanding Requirement 2" just before the Notes at the end of the section.https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-conformance-requirements-head If we did this, I think the intentions of these SC would be met in the conformance section and we could retire these proposals. This proposal is a result of extensive discussions with Patrick and Gregg and my own thoughts. 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>
Received on Wednesday, 12 July 2017 14:33:36 UTC