This is the second of four planned questionnaires for participants in the Accessibility Guidelines Implementation project for the HTML Writers Guild, described at: http://www.hwg.org/opcenter/projects/agi.html You should have already completed the first questionnaire; if you have not, please send email to agi-contact@hwg.org requesting a copy of it. Please complete the following information and return this via email to agi-contact@hwg.org. Privacy note: The answers you provide will not be posted publically; general statistics (such as "20% of the participants found section A-12 to be too confusing") may be posted on the Guild's web site. Specific comments made may be shared with the World Wide Web Consortium's Web Accessibility Initiative participants, including the authors/editors of the page author guidelines under evaluation. Introduction: The purpose of this questionnaire is to gauge your opinions of the WAI's page author guidelines. Note that these are a RELATIVELY NEW VERSION of the Guidelines, released on April 14, 1998. Please go now and read them over, and either take notes on them or have the guidelines open while you answer these questions. You can find the latest copy at: http://www.w3.org/TR/WD-WAI-PAGEAUTH.html This is required reading for answering this questionnaire! General Instructions: The general idea of this questionnaire is to see what you think of the guidelines _before_ attempting to implement them. However, we realize that some of you may already be working on accessibility considerations on your web pages, and that's great. What we'd like you to do is evaluate the guidelines from the standpoint of someone reading them for the first time, and not necessarily as someone who has tried them -- in other words, how do these look at first glance? If you've tried certain elements of the Guidelines and they worked, or didn't work, ignore that for now, and try to remember your original feelings. If that doesn't make sense, just ignore the paragraph above and simply answer questions. *grin* Each section of this questionnaire will refer to a specific part of the page authoring guidelines, and will ask you for your quantified opinion, and your additional comments. By "quantified opinion", I mean that we'll ask you for a number, to rate your reaction to the section of guidelines. The scale is: 1 - Strongly agree 2 - Agree with most of it 3 - Ambivalent 4 - Disagree with some of it 5 - Strongly disagree 0 - This doesn't seem to apply to me or my pages ? - I don't understand these guidelines at all By "agree", we mean "this is something I want to use on my pages". You may find things you don't wish to do, for what- ever reason (such as "looks too hard", or "too much work", or "the client isn't paying me for that"), so don't be afraid to disagree -- you may also think that they don't go far enough or that something should be "required" when it's only "recommended". In these cases, please list your specific suggestions or comments -- positive or negative -- in the "comments" section. If your web design doesn't involve the section in question -- for example, if you don't use frames or multimedia in your web design -- feel free to answer with a "0". If you just aren't sure what the guidelines are trying to say, answer with a question mark (?) or the letter Q. Each section will list the general heading, a summary of the guidelines under each category, and provide a space for your responses. You're only "required" to rate each section, but if you want you may comment on specific guidelines point by point, if you feel there are things you wish to say. Keep in mind that these guidelines are a "work in progress"; your feedback may prove to be invaluable in writing the next version of these guidelines. Thank you for your cooperation and participation in this project! (BTW, you can cut out anything above this line in your reply, if you like.) SECTION "ZERO": Identification In this section, you tell us who you are, so we can keep track of who's answered our questionnaires. The information you supply below should be the same as that which you gave for Questionnaire #1. Your name: Your email address: Your web page name: Your web page URL: SECTION ONE: Style and Structure Summary: 1. [Required] All elements comply with an HTML 4.0 definition and CSS-1. 2. [Required] Pages are readable and usable without style sheets (e.g., when the browser does not support them or the user has turned them off). 3. [Required] Headings are nested properly and are not used for formatting. 4. [Required] List structure and list items are correctly encoded with proper HTML elements. 5. [Required] Scrolling or blinking text are not used. 6. [Recommended] Text is formatted through style sheets, not by representing it with a graphic (which cannot be searched). 7. [Recommended] Invisible or transparent images are not used to force layout. Style sheets are used to control layout. 8. [Recommended] Deprecated presentation elements and attributes as well as B and I are not used. 9. [Recommended] HTML structural elements are only used to convey meaning, not presentation. 10. [Recommended] HTML presentation elements are only used to convey presentation, not structure. 11. [Recommended] Horizontal rules, acronyms, and abbreviations have titles. Your Ranking: [1=strongly agree, 5=strongly disagree, 0=not applicable, ?=Don't understand this] Comments: SECTION TWO: Images and Image maps Summary: 1. [Required] All images and image maps have alternative text. 2. [Required] Graphics that present important information (especially charts, tables, and diagrams) have an associated longer description of the graphic (i.e., via a description link or the "longdesc" attribute) Furthermore, authors have included internal text in images for formats that support it. 3. [Required] All image maps are accessible and keyboard navigable.  Furthermore: For each client-side image map, each of the map's links has an associated description. For each server-side image map, a list of the map's links are provided as text links (on the same page, on an alternative page that is accessible, or within the body of the OBJECT element). 4. [Recommended] Images used as links have descriptive link titles. 5. [Recommended] ASCII art has been replaced by images with alternative text. Your Ranking: [1=strongly agree, 5=strongly disagree, 0=not applicable, ?=Don't understand this] Comments: SECTION THREE: Applets and Scripts Summary: 1. [Required] Alternative presentations of content are provided for applets and scripts that convey information. 2. [Required] Alternative mechanisms are provided for applets and scripts that perform an important function (other than the presentation of information). 3. [Required] Applets that require user interaction that cannot be duplicated in an alternative format are directly accessible. 4. [Required] The user can freeze any moving or blinking text. 5. [Recommended] Applets have alternative text ("alt" on APPLET, "title" on OBJECT). 6. [Recommended] Scripts and applets are keyboard operable. Your Ranking: [1=strongly agree, 5=strongly disagree, 0=not applicable, ?=Don't understand this] Comments: SECTION FOUR: Audio and Video Summary: 1. [Required] All audio information has an associated transcript. 2. [Required] All video information has an associated audio description. 3. [Required] All video information has an associated transcript. 4. [Required] Transcripts and audio descriptions are synchronized with audio/video information, either directly or via a synchronization file. 5. [Recommended] Sounds that play automatically have a visual notification that the sound is playing. 6. [Recommended] Links to very short sounds have titles. Your Ranking: [1=strongly agree, 5=strongly disagree, 0=not applicable, ?=Don't understand this] Comments: SECTION FIVE: Tables Summary: 1. [Required] Table cells are explicitly associated with row and column labels. 2. [Required] Tables are not used to arrange text documents in columns. 3. [Recommended] Tables are not used merely for the purposes of page layout (use style sheets instead). 4. [Recommended] Tables of text and numbers are available in a linear fashion on an alternative page. 5. [Recommended] Lengthy row and column labels are abbreviated. 6. [Recommended] Table summaries are available. 7. [Recommended] For more complex tables, information is grouped into categories. 8. [Recommended] Alt-text does not wrap in tables used to position graphics. 9. [Recommended] A phone number, fax number, or e-mail address is provided if tables can not be made accessible. Your Ranking: [1=strongly agree, 5=strongly disagree, 0=not applicable, ?=Don't understand this] Comments: SECTION SIX: Links Summary: 1. [Recommended] Link text makes sense when read out of context, but is not too verbose. 2. [Recommended] Lists of links have non-link, printable characters (surrounded by spaces) between them. 3. [Recommended] Links have keyboard shortcuts. Your Ranking: [1=strongly agree, 5=strongly disagree, 0=not applicable, ?=Don't understand this] Comments: SECTION SEVEN: Frames Summary: 1. [Required] Each frame document (the FRAMESET element) has a non-frame alternative (e.g., the NOFRAME element). 2. [Required] An image does not appear directly in a frame but is part of a document included in a frame. 3. [Required] All frames have titles. 4. [Recommended] Links to descriptions of the purpose and layout of frames are provided. Your Ranking: [1=strongly agree, 5=strongly disagree, 0=not applicable, ?=Don't understand this] Comments: SECTION EIGHT: User-Input Forms Summary: 1. [Required] Image maps are not used to create graphical "submit" buttons. 2. [Required] Each label is associated with its form control. 3. [Required] Images used as "submit" buttons have alternative text. 4. [Recommended] A logical tab order is specified (with the "tabindex" attribute). 5. [Recommended] Related controls are grouped (with the FIELDSET element). 6. [Recommended] Groups of controls are labeled (with the LEGEND element). 7. [Recommended] Menu options are grouped (with the OPTGROUP element). 8. [Recommended] Edit boxes and text areas have default, place-holding characters. 9. [Recommended] An alternative phone number, fax number, e-mail address, or postal mail address is provided for submitting information. 10. [Recommended] Form elements have keyboard shortcuts (with the "accesskey" attribute). SECTION NINE: If All Else Fails... Summary: If after best efforts, a page is still not accessible, provide a link to an alternative page that is accessible, has equivalent information, and is maintained with the same frequency as the inaccessible page. Your Ranking: [1=strongly agree, 5=strongly disagree, 0=not applicable, ?=Don't understand this] Comments: SECTION TEN: Overall Opinion Section These are yes-no questions about the guidelines document as a whole, but you may give freeform longer explanations if you like. Overall, do you like the guidelines document? Are the guidelines too long, too short, or just right in size? Are these too technical or not technical enough? Is there anything that isn't included which you feel should be included? Is there too much emphasis on HTML 4.0 features or is it appropriate? Is there too much emphasis on stylesheets or is it appropriate? Do you understand the difference between [Required] and [Recommended]? Do you feel this is an important distinction? Do you understand the difference between [Interim] and [New] strategies, and unlabeled strategies? Do you feel this is an important distinction? Has your analysis of the guidelines given you new insight into accessible web page authoring? Have I convinced you yet that I ask too many questions? END OF QUESTIONNAIRE #2. Please email completed questionnaires to agi-contact@hwg.org. If you need an alternate way to submit your answers, please write to me at kynn@hwg.org to arrange this. Please do not send your reply to agi-project@mlists.com. Replies are requested by Sunday, April 26, but this is not a firm deadline; respond when you are able. Thank you again for answering and participating!