Re: [last call, S2] OS features adopted must be accessible

Al Gilman wrote:
> 
> In section 3.2 it says that the User Agent may pass through OS features as
> part
> of how they satisfy these guidelines.  It needs to be made clear that the OS
> features so adopted must be accessible to be part of meeting these guidelines.

Section 3.2 starts:

  "Developers are encouraged to adopt operating system conventions 
   and features that benefit accessibility to meet the requirements 
   of this document. However, if these features are not accessible, 
   developers must provide an alternative accessible solution."

Is that sufficient, in conjunction with:

   5.8 Follow operating system conventions that benefit accessibility. 
       In particular, follow conventions for user interface design,
keyboard
       configuration, product installation, and documentation. [Priority
2] 

If not sufficient, can you propose text?

Thank you,

 - Ian
 
> Al
> --
> Usage in headers.  Comments in response to the last call request for comments
> have been classified S1, S2, or E based on the following rough scale:
> 
> S1: Substantive matter of the first (highest) criticality or importance to the
> mission of the document.  The standard set is ineffective, the document is
> self
> contradictory, etc.
> 
> S2: Substantive matter of a somewhat lower criticality.  The document is hard
> to comprehend, does not align well with related WAI documents, etc.
> 
> E: Editorial matters.  Not regarded as substantive.
> 
> Re:
> 
> User Agent Accessibility Guidelines 1.0
> 
> W3C Working Draft 23 October 2000
> 
>    This version:
> 
> [9]<http://www.w3.org/TR/2000/WD-UAAG10-20001023>http://www.w3.org/TR/2000/W
> D-UAAG10-20001023

-- 
Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
Tel:                         +1 831 457-2842
Cell:                        +1 917 450-8783

Received on Monday, 13 November 2000 11:56:11 UTC