IRC log of wai-wcag on 2004-01-07
Timestamps are in UTC.
- 15:05:53 [RRSAgent]
- RRSAgent has joined #wai-wcag
- 15:05:58 [wendy]
- zakim, who's on the phone?
- 15:05:58 [Zakim]
- On the phone I see Dave_MacDonald, ??P10, Michael_Cooper, Chris_Ridpath, ??P22, Wendy, David_D
- 15:07:19 [wendy]
- zakim, ??P10 is Ben
- 15:07:19 [Zakim]
- +Ben; got it
- 15:07:23 [wendy]
- zakim, ??P22 is Tom
- 15:07:23 [Zakim]
- +Tom; got it
- 15:08:50 [wendy]
- http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-TECHS-GATEWAY-20031205.html
- 15:14:23 [wendy]
- tom would like people familiar with other technologies to review, since he's been abstracting based on his knowledge of html. would like to know how to apply these things to other languages (e.g., how to write for svg)
- 15:16:30 [wendy]
- action: WAC contact Dean about SVG techniques and reviewing Gateway
- 15:17:46 [wendy]
- SVG WG working on authoring techniques and does it include an accessibility chapter?
- 15:17:56 [wendy]
- If so, are they using xmlspec or xmlspec-techs?
- 15:18:15 [wendy]
- If not, how do we incorporate svg accessibility techniques into our checklists?
- 15:24:31 [wendy]
- discussion about text of links (making sense out of context) as well as use of title on links.
- 15:26:57 [wendy]
- we have discussed this before, not sure when. part of the issue is that not all links can make sense out of context.
- 15:27:17 [wendy]
- for example, in a cms, when links are generated ("more") they may not be unique.
- 15:27:29 [wendy]
- also, if one word is linked within in a paragraph it might not make sense when read out of context.
- 15:27:56 [wendy]
- (matt may had a strong position in the previous discussion...related to cms and blogging and generated links)
- 15:28:46 [wendy]
- lisa has on her wish list that "document titles should be unique"
- 15:29:13 [wendy]
- if title element of each page is unique, then could put the title of the target page in the title attribute of the link
- 15:31:01 [wendy]
- need example of generated page that has a long, unusable title. google creates a title of the form, "google search: [search keywords]" e.g., "Google Search: test two three" where "test two three" are the search keywords.
- 15:32:49 [wendy]
- yahoo maps, for the generated map has a title of "Yahoo! Maps"
- 15:36:03 [wendy]
- issue for html techniques: tom's issue with lists being read incorrectly by jaws
- 15:36:24 [wendy]
- action: tom provide a summary of the issue running into with lists and jaws
- 15:37:52 [wendy]
- already 3 styles of text equivalent that come from html. will other technologies introduce other kinds?
- 15:37:57 [wendy]
- types?
- 15:39:02 [wendy]
- equivalent alternatives in smil: http://www.w3.org/TR/SMIL-access/#Equivalent
- 15:42:31 [wendy]
- tom reads example from gateway: For example in HTML text equivalents can be added using the alt, title and longdesc attributes. In some cases using title is more appropriate than alt text since most screen reader user agents allow reading the title as optional for people who want more information. An image might be used to represent the subsequent link is to a pdf. By using the title rather than alt attribute to signify that the link is to a pdf information is on
- 15:43:00 [wendy]
- discussion
- 15:43:22 [wendy]
- title for a link is a different issue (and usage) from title on image.
- 15:43:51 [wendy]
- distinct uses of title: on acronym, links, images. don't want to confuse.
- 15:44:17 [wendy]
- title as optional, additional information
- 15:44:23 [wendy]
- not a text equivalent
- 15:46:36 [Zakim]
- -Tom
- 15:56:46 [wendy]
- action: wendy dig up staff contacts or other team members who can review gateway for other technologies (timed text/smil, svg - dino, css - bert)
- 15:58:54 [wendy]
- action: ben bring michael's changes back into gateway and republish
- 16:00:26 [wendy]
- prefer to get review by others sooner rather than later to make sure we're not heading down the wrong path.
- 16:00:57 [wendy]
- no worries contacting staff contacts - they know how this works. ;)
- 16:01:34 [wendy]
- aim: publish techniques gateway before technical plenary
- 16:02:55 [wendy]
- action: wendy find out if publishing moratorium around t.p.
- 16:03:28 [wendy]
- perhaps more realistic to publish to tr *after* tech plenary, since gathering info and review during tech plenary.
- 16:03:39 [wendy]
- also, only a month from now that would need to pubslish to /TR.
- 16:03:53 [wendy]
- minimum: new internal draft before tech plenary
- 16:04:00 [Zakim]
- -David_D
- 16:04:22 [wendy]
- able to coordinate with euroaccessibility people at tech plenary?
- 16:05:26 [wendy]
- action: wendy check with judy about meeting with EA on or around tech plenary
- 16:06:19 [wendy]
- several people from EA will be at EOWG on Monday/Tuesday?
- 16:08:03 [wendy]
- another internal draft of html techniques before tech plenary
- 16:17:22 [wendy]
- action: chris talk with jenae about QA guidelines and testing strategy
- 16:17:44 [wendy]
- next week: continue review of QA document (intended for today)
- 16:22:31 [wendy]
- thread started by sailesh "Supporting Technology" as well as thread by Tim Boland "WCAG-CSS mapping part [1-3]"
- 16:22:44 [wendy]
- action: ben go through techniques issues in bugzilla to see if low-hanging fruit.
- 16:24:02 [wendy]
- action: wendy move css issues into bugzilla http://www.w3.org/WAI/GL/WCAG20/css-tech-issues.html
- 16:24:31 [Zakim]
- -Chris_Ridpath
- 16:24:32 [Zakim]
- -Michael_Cooper
- 16:24:34 [Zakim]
- -Ben
- 16:24:35 [Zakim]
- -Wendy
- 16:24:36 [Zakim]
- -Dave_MacDonald
- 16:24:37 [Zakim]
- WAI_WCAG(techniques)10:00AM has ended
- 16:24:38 [Zakim]
- Attendees were Dave_MacDonald, Michael_Cooper, Chris_Ridpath, Wendy, David_D, Ben, Tom
- 16:24:47 [wendy]
- don't think that bugzilla includes all of the css issues. css bugzilla: http://trace.wisc.edu/bugzilla_wcag/issuereports/css_issues.php
- 16:25:00 [wendy]
- zakim, bye
- 16:25:00 [Zakim]
- Zakim has left #wai-wcag
- 16:25:12 [wendy]
- RRSAgent, bye
- 16:25:12 [RRSAgent]
- I see 9 open action items:
- 16:25:12 [RRSAgent]
- ACTION: WAC contact Dean about SVG techniques and reviewing Gateway [1]
- 16:25:12 [RRSAgent]
- recorded in http://www.w3.org/2004/01/07-wai-wcag-irc#T15-16-30
- 16:25:12 [RRSAgent]
- ACTION: tom provide a summary of the issue running into with lists and jaws [2]
- 16:25:12 [RRSAgent]
- recorded in http://www.w3.org/2004/01/07-wai-wcag-irc#T15-36-24
- 16:25:12 [RRSAgent]
- ACTION: wendy dig up staff contacts or other team members who can review gateway for other technologies (timed text/smil, svg - dino, css - bert) [3]
- 16:25:12 [RRSAgent]
- recorded in http://www.w3.org/2004/01/07-wai-wcag-irc#T15-56-46
- 16:25:12 [RRSAgent]
- ACTION: ben bring michael's changes back into gateway and republish [4]
- 16:25:12 [RRSAgent]
- recorded in http://www.w3.org/2004/01/07-wai-wcag-irc#T15-58-54
- 16:25:12 [RRSAgent]
- ACTION: wendy find out if publishing moratorium around t.p. [5]
- 16:25:12 [RRSAgent]
- recorded in http://www.w3.org/2004/01/07-wai-wcag-irc#T16-02-55
- 16:25:12 [RRSAgent]
- ACTION: wendy check with judy about meeting with EA on or around tech plenary [6]
- 16:25:12 [RRSAgent]
- recorded in http://www.w3.org/2004/01/07-wai-wcag-irc#T16-05-26
- 16:25:12 [RRSAgent]
- ACTION: chris talk with jenae about QA guidelines and testing strategy [7]
- 16:25:12 [RRSAgent]
- recorded in http://www.w3.org/2004/01/07-wai-wcag-irc#T16-17-22
- 16:25:12 [RRSAgent]
- ACTION: ben go through techniques issues in bugzilla to see if low-hanging fruit. [8]
- 16:25:12 [RRSAgent]
- recorded in http://www.w3.org/2004/01/07-wai-wcag-irc#T16-22-44
- 16:25:12 [RRSAgent]
- ACTION: wendy move css issues into bugzilla http://www.w3.org/WAI/GL/WCAG20/css-tech-issues.html [9]
- 16:25:12 [RRSAgent]
- recorded in http://www.w3.org/2004/01/07-wai-wcag-irc#T16-24-02