archive-org.com » ORG » H » HWG.ORG

Total: 1187

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • hwg-w3c mailing list archives: February 2001
    archives February 2001 Jan 2001 Mar 2001 Date Author Subject 3 Feb 2001 Kynn Bartlett Fwd Please review Web Content Accessibility Guidelines 2 0 Working HWG hwg w3c mailing list

    Original URL path: http://archives.hwg.org/hwg-w3c/2001/02 (2016-02-13)
    Open archived version from archive


  • hwg-w3c mailing list archives: March 2000
    list archives March 2000 Feb 2000 Apr 2000 Date Author Subject 1 Mar 2000 Kynn Bartlett CC PP Requirements and Architecture Working Draft Published HWG hwg w3c mailing list archives

    Original URL path: http://archives.hwg.org/hwg-w3c/2000/03 (2016-02-13)
    Open archived version from archive

  • hwg-w3c mailing list archives: September 2000
    Aug 2000 Oct 2000 Date Author Subject 21 Sep 2000 Ann Navarro News Release from the W3C WAI program director to speak at White Hou HWG hwg w3c mailing list

    Original URL path: http://archives.hwg.org/hwg-w3c/2000/09 (2016-02-13)
    Open archived version from archive

  • hwg-w3c mailing list archives: September 1999
    September 1999 Aug 1999 Oct 1999 Date Author Subject 3 Sep 1999 Kynn Bartlett Heads up Last Call for Authoring Tool Accessibility Guidelines HWG hwg w3c mailing list archives maintained

    Original URL path: http://archives.hwg.org/hwg-w3c/1999/09 (2016-02-13)
    Open archived version from archive

  • Fwd: Please review: Web Content Accessibility Guidelines 2.0 Working Draft by Kynn Bartlett <kynn-hwg(at)idyllmtn.com>
    development but feedback in the early stages of document development is especially useful At this stage we invite comments on two mailing lists For any comments that you want to be sure are registered with the WCAG Working Group regarding the January 25th WCAG 2 0 Working Draft please send them to w3c wai gl at w3 org by Thursday 22 February 2001 For general discussion about this Working Draft please comment on w3c wai ig at w3 org That discussion will be monitored to some extent by the WCAG Working Group but it does not guarantee that every issue raised there will be registered with the Working Group for formal discussion The WCAG Working Group welcomes comment on any aspect of the draft but is particularly interested in feedback on the following issues 1 Are the checkpoints and guidelines in the WCAG 2 0 Working Draft easier to understand than in WCAG 1 0 Has terminology been used that is hard to understand We realize that filling in the Glossary will help with some of these issues Are there terms that are not listed in the Glossary that should be 2 This initial public WCAG 2 0 Working Draft does not have as much explanation for each guideline as WCAG 1 0 This is partially because the WCAG Working Group has discussed a three layered approach with the first layer being more explanatory what are the basic ideas about Web content accessibility how can this document be referenced etc the second layer being the guidelines and checkpoints explaining how to make a Web site accessible and the third being techniques tests and or examples that would help explain how to implement this in different Web technologies What do people think about this approach It might be hard to imagine

    Original URL path: http://archives.hwg.org/hwg-w3c/4.2.0.58.20010203102527.00afdaf0@garth.idyllmtn.com (2016-02-13)
    Open archived version from archive

  • News Release from the W3C - WAI program director to speak at White House sponsored event by Ann Navarro <ann(at)webgeek.com>
    accessibility of the Web for people with disabilities highlighting solutions developed by WAI to produce a Web that is more usable by all WAI works by bringing together industry disability organizations accessibility researchers and government explained Brewer We can show that accessible design is not only possible but is also good design and well within reach of all Web content publishers WAI s recent achievements include the development of guidelines for the creation of Web content that can be accessed by any user regardless of disability as well as guidelines for the production of software that makes it easier to produce accessible Web content automatically The Web Content Accessibility Guidelines serve as a definitive resource for Web designers to produce sites that work for the widest possible audience and have received international endorsement About the Web Accessibility Initiative WAI The World Wide Web Consortium s W3C commitment to lead the Web to its full potential includes promoting a high degree of usability for people with disabilities WAI in coordination with organizations around the world pursues accessibility of the Web through five primary areas of work technology guidelines tools education and outreach and research and development About the World Wide Web

    Original URL path: http://archives.hwg.org/hwg-w3c/4.3.1.2.20000921123916.02cc2380@pop.mm.com (2016-02-13)
    Open archived version from archive

  • CC/PP Requirements and Architecture Working Draft Published by Kynn Bartlett <kynn(at)idyllmtn.com>
    server The origin server uses the user agent profile to produce and deliver content appropriate to the client device In addition to computer based client devices particular attention is being paid to other kinds of devices such as mobile phones 1 2 Executive summary of requirements The requirements on the framework emphasize three aspects Flexibility extensibility and distribution The framework must be flexible since we can not today predict all

    Original URL path: http://archives.hwg.org/hwg-w3c/4.2.0.58.20000301143621.00aef100@mail.idyllmtn.com (2016-02-13)
    Open archived version from archive

  • Fwd: Last Call review of User Agent Accessibility Guidelines 1.0 by Kynn Bartlett <kynn-hwg(at)idyllmtn.com>
    and issues 1 Do you understand the Guidelines and Checkpoints or do they need clarification 2 Do you find the documents Guidelines and Techniques themselves usable Can you find what you are looking for 3 Two checkpoints numbers here require user agents to make available to users information about the current input configuration e g keyboard input These checkpoints 20 have been assigned different priorities Priority 1 for 20 user specified configuration and Priority 2 for author specified configuration e g access keys The Working Group did not reach consensus on whether these two checkpoints should be merged into a single checkpoint and what the priority of such a checkpoint would be 4 Checkpoint 6 1 Priority 1 asks user agents to implement the 20 accessibility features of supported specifications 20 In the Authoring Tool Guidelines Proposed Recommendation 20 checkpoints that refer to content accessibility do so by Relative Priority This means that the priority of the checkpoint in the UAGL depends on how much you wish to conform to the Web Content Accessibility Guidelines 6 There has been a suggestion to make 6 1 a checkpoint with a Relative Priority rather than Priority 1 The Working Group did not reach consensus on whether the burden of doing so complicating the priority definition outweighed the benefit 20 of consistency among the three sets of Guidelines Also it is 20 not clear that a Priority 3 requirement in WCAG would always be 20 a Priority 3 requirement in UAGL i e it may be more important to implement a feature than for the author to supply it 20 Comments on the proposal to make 6 1 a Relative Priority checkpoint are welcome DEPENDENCIES AND REVIEW The Working Group thanks all who have contributed to the Guidelines and Techniques document The Working Group also thanks in advance those people who have committed to reviewing 4 the Last Call Working Draft 20 1 Jim Fruchterman 2 Doug Geoffray 3 Ben Wiess 4 T V Raman 20 5 Fraser Shein 6 Bryan Campbell 20 7 Peter Korn 8 Lakespur Roca 9 Earl Johnson 10 Mike Paciello 11 Janina Sajka 20 12 Liam Quinn 13 Eric Freese 14 George Madaus 15 John Gardner 16 Gregg Vanderheiden 17 Markku T Hakkinen 18 Geoff Freed 19 Patrick Sheehan 20 Richard Primack 21 H E5kon Wium Lie 22 Chuck Hitchcock All Group Chairs are also invited to send their comments to 20 the above address 20 The Working Group has identified dependencies with the following W3C Working Groups and requests review from them Even if review is not possible we request that the Chairs listed below announce their review intentions to w3c wai ua a public mailing list 1 WAI Protocols Formats WG Co Chairs Al Gilman and Daniel Dardailler 20 UAWG provides input on accessibility requirements with regard to W3C technologies for which PFWG manages dependencies 2 WAI Web Content Accessibility Guidelines WG 20 Co Chairs Chuck Letourneau and Gregg Vanderheiden Trace 20 UAWG ensures that the

    Original URL path: http://archives.hwg.org/hwg-w3c/4.2.0.58.19991106142353.00b7b100@mail.idyllmtn.com (2016-02-13)
    Open archived version from archive



  •