W3C home > Mailing lists > Public > public-wai-eo-site@w3.org > February 2005

minutes Re: questions for discussion Re: ad-hoc WSTF discussion in 2 hours

From: Shawn Henry <shawn@w3.org>
Date: Tue, 08 Feb 2005 13:20:41 -0600
Message-ID: <42091109.4070600@w3.org>
To: public-wai-eo-site@w3.org

notes from yesterday's meeting are below.
the irc log is at: http://www.w3.org/2005/02/07-wstf-irc.html & http://www.w3.org/2005/02/08-wstf-irc.html

> 1. see how translations fit in
> - http://w3.org/2004/09/wai-nav/intro/accessibility.php#related
> - http://w3.org/2004/09/wai-nav/References/QuickTips/Overview.php#related
> - decouple with related pages?

decision: separate Translations & Related Pages into their own sections

> 2. revisit location of related pages
> - separate section under page contents ? (e.g.,
> http://www.w3.org/WAI/intro/components) pro: if landed on wrong page

option: related links in a section at the top, under page contents
pro - related items are available without scrolling or clicking (in page link)
pro - helpful if someone is on the "wrong" page, can see other page without scrolling or clicking (in page link)
con - clutters up the top of the page. increases cognitive load

option: related links at the bottom (with in page link at top that jumps down to it)
pro - simplifies the info above the fold, limits clutter, decreases congnitive load to process infomation above the fold
con - if the related pages are important, they are more likely to be missed at the bottom

notes:
- question: How many times will the related documents be in or outside of that level of the IA that you are currently on?
- if put the related pages at the top, could set "rules" to limit them to pages not already visible in the navigation

> 3. discuss navigation interaction
> - current page clickable, to parent?

agreement: no way

> 4. W3C Search issues
> - set aside from others?
> - other temp solution issues?

put at bottom

> 5. changes in short names
> - How People Use the Web > How People with Disabilities Use the Web
good
> - Quick Tips to Make Accessible > Quick Tips to Make Accessible Sites
good
> - WAI Groups > WAI Working Groups???
unnecessary. primary target for this link is not newbies
> - About the WAI Site > ???
> (see unrevised drafts: http://www.w3.org/WAI/about/site.html, 
> http://www.w3.org/WAI/about/usingsite.html)
try Site Help
> - Interdependent Components > ???
perhaps: How the Parts of Web Accessibility Work Together
action: shawn send brainstorms to EOWG list

> 6. task, "How do I make [forms, tables, etc.] accessible" - 
> http://www.w3.org/WAI/intro/html-techs.html

- justin concerned WCAG 1.0 HTML Techs too old. checking into.


> Shawn Henry wrote:
> 
>>
>> WAI Site Task Force of EOWG (WSTF) Ad-Hoc Meeting 7 February 2005
>>
>> Time:    6:00pm-8:00pm US Eastern Time, for other time zones see:
>>         http://www.timeanddate.com/worldclock/meeting.html
>> Bridge:    +1.617.761.6200,     conference code 9783# (WSTF#)
>> IRC:    channel: #wstf
>>     server: irc.w3.org
>>     port: 6665
>>
>> Please plan to be on IRC if at all possible.
>>
>> Redesign project page: http://www.w3.org/WAI/EO/2003/redesign.html
>>
>> Latest prototype: http://w3.org/2004/09/wai-nav/
>> IMPORTANT: status of above prototype:
>> * information architecture (IA) and layout: pretty much done
>> * visual design: close, but still needs significant tweaking
>> * markup: a total mess
>> * wai logo: just a placeholder
>> * links: many broken, to see which ones work, see:
>>    http://w3.org/2004/09/wai-nav/sitemap
>> Specific questions for discussion coming soon...
>>
>>
>> ===
>> Teleconference information:
>> - W3C Zakim Teleconference Bridge instructions: 
>> http://www.w3.org/2002/01/UsingZakim
>> - Zakim IRC Bot information: http://www.w3.org/2001/12/zakim-irc-bot
>> - A source for help with IRC (Internet Relay Chat):
>> http://www.irchelp.org/  
>>
> 
Received on Tuesday, 8 February 2005 19:20:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:20 GMT