See also: IRC log
Proposed HTML Technique for L1SC1: using meta name="dc:language" to specify language
not support to make sufficient. add it to our "optional techniques/someday pile" bugzilla bug
General Technique for L3SC2: internal linking - clarify in the guide that there are at least 2 sufficient techniques to chose from (internal linking and rel=glossary)
<scribe> ACTION: john? write guide for l3sc2, include options for 2 sufficient techniques (internal linking OR rel=glossary) [recorded in http://www.w3.org/2005/09/21-wcag-teamb-minutes.html#action01]
Proposal to divide the General Technique for L3 SC3 into 3 General Techniques, plus a new one
<scribe> ACTION: becky write guide doc with the 4 sufficient techniques (Using inline expansion OR Using a Glossary page OR Searching an online dictionary of acronyms OR and Using a Dictionary Cascade.) - just choose one [recorded in http://www.w3.org/2005/09/21-wcag-teamb-minutes.html#action02]
looking for evidence about abbr and reading disability.
Proposals for General Technique for L3 SC4
http://lists.w3.org/Archives/Public/public-wcag-teamb/2005Sep/0031.html
writing section headings for scannability.
1. Help users find the information they are looking for. Write section titles that are meaningful and will help users scan documents quickly
and easily. To speed scanning, help users quickly tell when sections don't contain what they are looking for.
restating the SC?
accessibility benefit?
serial access forced to skim.
2. Write section titles that clearly indicate the topic of their section. Each section should only cover one specific idea.
3. The first section title should let the user know why the page or document is important.
what is a section?
need defn of section? L3SC4 Section titles are descriptive.
4. Users should be able to get a summary or overview of the content by skimming just the section titles. Make the structure clear and obvious.
5-9 in email
would we have to replace "abstract" with "abstract for wcag 2.0"
how much context can we assume for a title?
in this proposal, assume no context - can't even assume w/in the document
even if linking into middle of document should be able to get some context from title element
<scribe> ACTION: loretta and diane? - draft guide for l3sc4, propose defn of section, propose examples for each technique to help us better understand, use the 1.1 mock-up to group techs into sufficient and optional [recorded in http://www.w3.org/2005/09/21-wcag-teamb-minutes.html#action03]
Guide for L3SC5, - looks good
<scribe> ACTION: john and bengt? work up guide for l3sc5 into template and submit to group [recorded in http://www.w3.org/2005/09/21-wcag-teamb-minutes.html#action04]
HTML Technique for L3SC51: Use titles to summarise the content
HTML Technique for L3SC5: using title for translations of foreign passages or phrases
HTML Technique for L3SC5: using title to explain jokes
HTML Technique for L3SC5: using title to summarize or simplify content
several concerns: using title attribute or element? overloading title? difficult to define humor much less explain.
when the SC talks about a supplement to "text" is it the whole delivery unit or could it be anyone passage?
<scribe> ACTION: wendy to add thse to our "optional" bug [recorded in http://www.w3.org/2005/09/21-wcag-teamb-minutes.html#action05]
HTML and CSS Techniques for L3SC5: Using role to specify structure and types of content
CSS Technique for L3SC5: Helping the user follow the structure of the document
add to optional bin
at SC level, don't distinguish between acronym and abbreviation because these are HTML-specific issues?
resolution: *not* propose combining of l3sc2 and sc3.
<scribe> ACTION: becky repropose defn of abbreviation and acronym, propose SC w/out "acronym," draft guide for l3sc3, proposed a combined html technique for abbr and acronym [recorded in http://www.w3.org/2005/09/21-wcag-teamb-minutes.html#action06]