RE: 4.2 - User interfaces.

Good, but i think must Be clear where we must refer to uaag (btw, i think that uaag are a separate issue and that we cannot ask this conformance inside wcag).
Otherwise we need to limit these requirements to custom interfaces / plugin:
- accessibility by keyboard interface;
- textual alternative text for image controls;
... (= software requirements inside section 508 law).

If we move outside plugin, where is our point break? If we have a multimedia objectfor eg, a developer would prefer simply to put a link that open the media content inside the default media player: this would Be good for software accessibility (the user can open multimedia contents using default browser for this kind of file) but this may cause that, for wcag conformance to guideline 4.2, we will have less embedded objects.
Btw, i prefer the opening of multimedia contents outside web browser, but is this that we want?


----- Messaggio originale -----
    Da: "Gregg Vanderheiden"<gv@trace.wisc.edu>
    Inviato: 12/03/05 21.00.03
    A: "'Roberto Scano - IWA/HWG'"<rscano@iwa-italy.org>, "w3c-wai-gl@w3.org"<w3c-wai-gl@w3.org>
    Oggetto: RE: 4.2 - User interfaces.
      
    -----Original Message-----
    We need at least decide if we are "Web Content Accessibility Guidelines" 
    or "Web Accessibility Guidelines". 
    
    
    
    I think we are writing "delivery unit accessibility guidelines" 
     
    Gregg
    
     -- ------------------------------ 
    Gregg C Vanderheiden Ph.D. 
    Professor - Ind. Engr. & BioMed Engr.
    Director - Trace R & D Center 
    University of Wisconsin-Madison 
    
    
    
    
        

[Messaggio troncato. Toccare Modifica->Segna per il download per recuperare la restante parte.]

Received on Saturday, 12 March 2005 23:26:51 UTC