Next call: Tuesday March 10, 1:00 pm EST (pending call arrangement) To do: review checklist, consider additions to the list consider subtractions to the list, prioritize checklist items into 3 levels. Introductions Tom Wlodkowski NCAM Geoff Freed NCAM Gregg Vanderheiden Trace Wendy Chisholm (sp?) Trace David Poehlman Private consultant, user Kitch Barnicle AFB Jon Gunderson UIUC, Group Chairperson Evan Wies Immersion Jon welcomed participants and stated that one of the groups first goals was to determine the group's purpose. Jon began by stating his position that the groups needs to develop guidelines that will influence the accessibility of the web. These guidelines need to be sensitive to both browser developers and AT developers. The group needs to figure out the goals that must be achieved to in order to improve access while not getting bogged down in details. There will be many ways to implement certain recommendations. We can develop a list of current access strategies and the technologies available to implement these strategies. Jon asked the group if participants what they would like to see come out of this group. Gregg , as an editor of the page authoring guidelines, described three things he would like to see come out of this group's efforts. 1. create less work for page authors without limiting their creativity. i.e. build as much accessibility into the browser so the burden to create accessible pages is lowered 2. improve regularity - so authors will know what to expect (e.g. the browser automatically adjusts to show the complete alt tag) 3. build access into the browser that gives increased flexibility without adding to the set of "rules" that a page author must follow - if there are too many rules, they will not be followed. Gregg posed a question to Chuck Opperman regarding time lines for incorporating changes into the next version of Internet Explorer. Chuck said that comments would have to be in almost immediately, probably by CSUN at the latest. He could not promise that any recommendations would be incorporated. He stated that IE 5.0 will be released no later than the release of NT 5 but he could not give a calendar date. Chuck seconded Gregg's comment regarding reducing the work effort for authors to create accessible documents. He went on to say that he hope this group could provide direction on "best practices." For example, what is the best way to implement LONGDESC. There was some discussion regarding current accessibility in IE 5.0. Some of these enhancements will be shown at CSUN. These enhancements include: - improved keyboard support - better support of the DOM, DHTML object model - better deaf access related to background sounds etc. Chuck does not see a the UI group having a direct role in influencing the Microsoft's relationship with ISVs. Microsoft is already working to improve communication with ISVs. However, he sees the group influencing other browser manufacturers to incorporate accessibility which in turn helps the field know what "works" and what doesn't work. Chuck was asked if he and Microsoft would be open to giving presentations on MSAA and its relation to IE so that other browser developers can learn from the IE experience. David asked about getting more ISV input to the group and address the situation today as well as in the future. Jon has contacted several assistive technology developers. Kitch stated that, obviously, she hoped the group's work would lead to browsers that are accessible to individuals who are blind or visually impaired. She added that guidelines developed by the group would be valuable in AFB's advocacy efforts. It is important that we can tell developers what they need to do when we ask them to improve the accessibility of their products. She also asked if the group has thought about the approach they are going to take in regards to guidelines for type 1 browsers, those that are directly accessible, and type 2 browsers, those that are accessed through a layer of adaptive technology. She also asked if PC based browsers going to be distinguished from browsers for cell phones, PDAs and cars? Gregg suggested that we may need 2 documents, one more theory orientated and the second more implementation oriented. Developers do not want to be overwhelmed with a long list things to do. Developers need concrete, consistent recommendations. The group's recommendations need to be prioritized. He suggested three categories 1. critical needs (e.g. based on number of users, impact on users, impact on page authors) 2. important needs that should be considered 3. things that would be helpful Developers are most interested in how guidelines will impact "their" browser, not browsers in general. Chuck added that, rather than only giving manufacturers a list of high priority items, both high and low priority recommendations should be given to the developer so that any recommendations that can be implemented easily can be incorporated into the product. Gregg suggested that we may have to create two sets of guidelines one aimed at type 2 browsers and the other set aimed at type 1, or directly accessible, browsers. Software manufacturers such as Microsoft, IBM, Sun and others may be interested in guidelines for non-visual browsers for use in cars etc. Kitch asked about Spyglass's prism and others mentioned Opera as products we might want to look into regarding improved access. Chuck mentioned the need for better ideas on efficient keyboard navigation. ??? Chuck discussed MS HTML (formally code name Trident), a Microsoft component that basically controls the presentation of HTML in IE. MS HTML parses HTML, puts in the DOM, loads controls etc. MS HTML is used frequently in Windows 98, Windows NT 5.0, IE 4.0 and Outlook. It is used by AOL and compuserve in their browsers and it can be used by companies who want to use MS components but customize the look of their browsers. Chuck described some additional features in IE 4 that could be expanded to improve accessibility. These features are currently part of "power toys" scripts that can be downloaded from the MS site. For example, one script, activated by a right click, will add a list of the page links to the context menu, numbers are assigned to each link, users can then choose a link from this list. New scripts can also be created in visual basic. Information on these "power toys" can be found in the microsoft internet SDK. Chuck also requested feedback regarding accessibility on IE 4.0 for Solaris. Where to go from here? 1. Revise checklist so that it can be given to Microsoft and others at CSUN Participants should: 1. prioritize items on checklist 2. add items 3. remove items 4. request clarification on items