- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Sun, 4 Dec 2005 00:11:11 -0600
- To: <boland@nist.gov>, <w3c-wai-gl@w3.org>
Current plan is Jan 30 to Feb 3rd in Austin. Gregg -- ------------------------------ Gregg C Vanderheiden Ph.D. Professor - Ind. Engr. & BioMed Engr. Director - Trace R & D Center University of Wisconsin-Madison -----Original Message----- From: boland@nist.gov [mailto:boland@nist.gov] Sent: Saturday, December 03, 2005 9:18 AM To: Gregg Vanderheiden Cc: w3c-wai-gl@w3.org Subject: Next meeting? When and where is the next WCAG f2f meeting? Quoting Gregg Vanderheiden <gv@trace.wisc.edu>: > > Yes but it is the same time as the WCAG Face to Face so..... Can't come. > > > > Gregg > > -- ------------------------------ > Gregg C Vanderheiden Ph.D. > Professor - Ind. Engr. & BioMed Engr. > Director - Trace R & D Center > University of Wisconsin-Madison > > > -----Original Message----- > From: Roberto Scano - IWA/HWG [mailto:rscano@iwa-italy.org] > Sent: Friday, December 02, 2005 2:30 AM > To: 'Gregg Vanderheiden'; Bruce.Bailey@ed.gov; w3c-wai-gl@w3.org > Subject: RE: Missing criteria from WCAG 2.0? > > Thank you Gregg for clarify this for the group (my mistake about don't have > done it). This ISO will pobably be definitively discussed at the next WG 5 > meeting that will Be host here in Venice on 30th Jan 2006 to 2nd Feb. 2006 > (hosted by IWA/HWG and Engineering SpA). I think there will be also > possibility for discussion of ISO 9241-151 (ergonomics for world wide web > user interfaces) > > -----Original Message----- > From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf > Of Gregg Vanderheiden > Sent: Friday, December 02, 2005 4:26 AM > To: 'Roberto Scano (IWA/HWG)'; Bruce.Bailey@ed.gov; w3c-wai-gl@w3.org > Subject: RE: Missing criteria from WCAG 2.0? > > > > Hi > > Just for those not familiar with these guidelines. > > ISO 16071 is now 9142-171 and is heading for Candidate Draft. > It is originally based upon (and is harmonized with) HFES 200.3 > > Both are software accessibility guidelines. > > StickyKeys and functions like it are supposed to be done in OS and honored > by applications. But if an operating environment overrides the OS then it > inherits the responsibility for providing the OS functions. > > Gregg > > PS I have been helping to coordinate and harmonize between WCAG 2.0 and > both of these developing standards. > > > -- ------------------------------ > Gregg C Vanderheiden Ph.D. > Professor - Ind. Engr. & BioMed Engr. > Director - Trace R & D Center > University of Wisconsin-Madison > > > -----Original Message----- > From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf > Of Roberto Scano (IWA/HWG) > Sent: Thursday, December 01, 2005 3:35 PM > To: Bruce.Bailey@ed.gov; w3c-wai-gl@w3.org > Subject: RE: Missing criteria from WCAG 2.0? > > > Java is an application enviroment, with its own rules (java, for default, > hereditate only Java configuration like font, etc. And cannot hereditate OS > configuration. Like in ex-ISO 16071 (formely ISO 9241-171), these > requirements involve software applications interfaces that can only be > applied following OS accessibility or ISO standards (W3C don't define > accessibility for software interfaces), like Section 508 paragraph that you > cited. > > ----- Messaggio originale ----- > Da: "Bailey, Bruce"<Bruce.Bailey@ed.gov> > Inviato: 01/12/05 22.23.11 > A: "w3c-wai-gl@w3.org"<w3c-wai-gl@w3.org> > Oggetto: Missing criteria from WCAG 2.0? > > I am continuing to work on a mapping from 508 to WCAG 2.0. It seems to > me the following items are referenced by 1194.21 but not by WCAG 2.0. Are > these items applicable to Java apps? > > (b) Applications shall not disrupt or disable activated features of > other products that are identified as accessibility features, where those > features are developed and documented according to industry standards. > Applications also shall not disrupt or disable activated features of any > operating system that are identified as accessibility features where the > application programming interface for those accessibility features has been > documented by the manufacturer of the operating system and is available to > the product developer. > > (g) Applications shall not override user selected contrast and color > selections and other individual display attributes. > > (j) When a product permits a user to adjust color and contrast settings, > a variety of color selections capable of producing a range of contrast > levels shall be provided. > > Thanks for your consideration. > > > > > [Messaggio troncato. Toccare Modifica->Segna per il download per recuperare > la restante parte.] > > > > > > >
Received on Sunday, 4 December 2005 06:13:16 UTC