- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Thu, 12 Sep 2013 08:51:34 -0500
- To: Greg Lowney <gcl-0039@access-research.org>
- Cc: WAI-UA list <w3c-wai-ua@w3.org>
- Message-ID: <CA+=z1Wm3xFu-4bnNeGVDG30+J0TaEw3h_shKeEOmKexpd1VByQ@mail.gmail.com>
+1 I like the new wording, it leaves little doubt as to what is an exception. to make it easier to read, here is the proposal with no extra markup Proposed new wording for paragraphs 7 and 9 7. Platform Limitations: If the platform does not support capabilities necessary for some UAAG 2.0 success criteria, list the success criteria and the features. For these listed technologies, the declarations section can claim that the success criteria do not apply due to platform limitations. Note: For the purpose of paragraphs 7 and 9, platform includes only the hardware, operating system, or cross-platform operating environment, as these generally cannot be replaced without substantially changing the target market. For example, if the user agent runs on an operating system that does not provide platform accessibility services, a conformance claim for this configuration can list the result for each related success criterion as "Not applicable due to platform limitations", and describe the specific platform limitation. However, if the user agent designers choose to use a widget library that does not support the platform accessibility services, they could not claim an exemption based on that decision. 9. Declarations: For each success criterion, provide a declaration of either: a. whether or not the success criterion has been satisfied; or b. declaration that the success criterion is not applicable and a rationale for why not from the following choices, along with appropriate details: 1. Not applicable due constraints of the platform, as per Paragraph 7 above (e.g. color handling when the browser is designed for a monochrome device, video handling in a purely audio browser, or interprocess communication on an operating system that does not support multitasking) 2. Not applicable due to a constrained input set (e.g. audio requirements when a help system that only displays text content from HTML files included with the product) 3. Not applicable due to limited output modalities (e.g. video handling in a browser that only does audio output, even though the platform may support video) For comparison, here is the existing wording: 7. Platform Limitations: If the platform (hardware or operating system) does not support a capability necessary for a given UAAG 2.0 success criterion, list the success criterion and the feature (e.g. a mobile operating system does not support platform accessibility services, therefore the user agent cannot meet success criterion 4.1.2). For these listed technologies, the user agent can claim that the success criteria do not apply. 9. Declarations: For each success criterion, provide a declaration of either a. whether or not the success criterion has been satisfied; or b. declaration that the success criterion is not applicable and a rationale for why not On Thu, Sep 12, 2013 at 3:56 AM, Greg Lowney <gcl-0039@access-research.org>wrote: > I have two open action items about clarifying the paragraphs in the in > the Conformance section that deal with how the "Not Applicable" exemption > can be used in conformance claims. The goal is to restrict these to a > limited set of reasons, in order to avoid leaving it so broad or subjective > that the exemption could be applied to almost anything. > > Proposed new wording for paragraphs 7 and 9 (Asterisks enclose added or > substituted text, and square brackets indicate where text was deleted but > not replaced. Note that all but one of the changes in paragraph 7 are > merely changing singular to plural.) > > 7. Platform Limitations: If the platform [] does not support > *capabilities* necessary for *some* UAAG 2.0 success *criteria*, list the > success *criteria* and the feature*s*. For these listed technologies, the > *declarations section* can claim that the success criteria do not apply > *due to platform limitations*. [] > > *Note: For the purpose of paragraphs 7 and 9, platform includes only > the hardware, operating system, or cross-platform operating environment, as > these generally cannot be replaced without substantially changing the > target market. For example, if the user agent runs on an operating system > that does not provide platform accessibility services, a conformance claim > for this configuration can list the result for each related success > criterion as "Not applicable due to platform limitations", and describe the > specific platform limitation. However, if the user agent designers choose > to use a widget library that does not support the platform accessibility > services, they could not claim an exemption based on that decision.* > > 9. Declarations: For each success criterion, provide a declaration of > either: > a. whether or not the success criterion has been satisfied; or > b. declaration that the success criterion is not applicable and a > rationale for why not *from the following choices, along with appropriate > details: > 1. Not applicable due constraints of the platform, as per > Paragraph 7 above (e.g. color handling when the browser is designed for a > monochrome device, video handling in a purely audio browser, or > interprocess communication on an operating system that does not support > multitasking) > 2. Not applicable due to a constrained input set (e.g. audio > requirements when a help system that only displays text content from HTML > files included with the product) > 3. Not applicable due to limited output modalities (e.g. video > handling in a browser that only does audio output, even though the platform > may support video)* > > For comparison, here is the existing wording: > 7. Platform Limitations: If the platform (hardware or operating system) > does not support a capability necessary for a given UAAG 2.0 success > criterion, list the success criterion and the feature (e.g. a mobile > operating system does not support platform accessibility services, > therefore the user agent cannot meet success criterion 4.1.2). For these > listed technologies, the user agent can claim that the success criteria do > not apply. > > 9. Declarations: For each success criterion, provide a declaration of > either > > a. whether or not the success criterion has been satisfied; or > b. declaration that the success criterion is not applicable and a > rationale for why not > > Thanks, > Greg > -- Jim Allan, Accessibility Coordinator & Webmaster Texas School for the Blind and Visually Impaired 1100 W. 45th St., Austin, Texas 78756 voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/ "We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Thursday, 12 September 2013 13:51:57 UTC