Kynn, >2.1 Provide a variety of navigation mechanisms > > <glossary>Navigation mechanisms</glossary> help > the user find information on your site. Providing > more than one navigation mechanism makes content > easier to locate and use. > > ISSUE: What does "a variety" mean? By this guideline > I mean "use a site map, use a search feature, use navigation > bars" etc. This is your attempt to create a checkpoint that encompasses 2.5, right? [2.5 If search functions are provided, provide a variety of search options for different skill levels and preferences.] In that case then you might want to say, "provide more than one path or mechanism to find content." still pretty rough, but "more than one" might be a bit tighter than "a variety." then we could talk about the "scent of information" and the variety of ways people navigate information. It's like saying, "there are 5 paths to get from A to B and people will choose a path based on which stores they wish to pass or which park they want to walk through." >3.X Provide consistent interaction behaviors >(should follow WD-WCAG20-20010125 guideline 3.1) > > <glossary>Interaction behaviors</glossary> are the > results of user actions. They include, for example: > * events caused by the user activating a link > * rollover effects and popup menus > * form submission, after activating a submit > button > * interface controls within applets or scripts > > These actions should be predictable and sensible > to the end user; this is achieved by making the > interactions consistent, both within the site > and with commonly used models of computer > interaction. this is good. At the face to face we talked about "consistent" having two meanings in this context: 1. consistency with standard UI design. 2. consistent usage within a site. This ought to mentioned in the rationale as well, no? > ISSUE: Should there be a separate checkpoint for navigation > consistency? If so, how do we define navigation consistency? I think navigation is a subset of navigation and therefore a separate checkpoints is not necessary. --w -- wendy a chisholm world wide web consortium web accessibility initiative madison, wi usa tel: +1 608 663 6346 /--Received on Friday, 16 March 2001 15:51:42 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:09 GMT