See also: IRC log
<ben> discussing: http://www.w3.org/WAI/GL/2005/06/30-tech-harvest-by-tech.html
<wendy> Link to a sequence of pages that provide function - not high priority
Text labels above and below the sensory content - medium priority.
Consider no-script element with no content - not a priority
Link to stable site that provides description of different options for real time captioning - move to general - medium priority.
Emphasis element and coloring rather than just using span with color - high priority.
(Similar to L1) - part of previous one.
Tabindex? May be covered by 2.4 - low priority note: doesnt apply to this success criteria.
bgsound, autoplay - High Priority around the practice.
Using foreground and background colors - high priority to work on.
onclick as mechanism to get focus - low priority or drop.
tabindex, though user agent issues - High priority.
Anchors on image buttons - high priority.
Redundant links for server-side image maps - low priority. Move into appendix
Use of <map> to allow keyboard navigation - Not sure what techinque is - is that a way of saying use client image maps? - If so, we already have a techinque for this. - remove technique.
Meta-refresh technique - we already have technique.
Foreground/background issues - Should be general technique - Move to general - high priority as a general technique.
<link> and <a> - low priority. take the existing ones.
Header elements - move to 1.3, it's already there.
Lists and groups of links - high priority.
onclick event handlers that take you to another page - high priority. Mark as possible script as well for cross reference.
Autosubmit combo boxes - should be included - high priority.
and it relates to scripts
Table of contents - general technique - medium priority at best maybe low.
Revise HTML 9.7 to be more general? - low priority.
Ideally, using <div> would help - low priority.
Headers - repeated under passing blocks of content - low priority.
Tables - low priority. really low?
note: not encouraged
Use spacer gif in link text so that it is not visible where alt for spacer gif gives additional clarification - becky: put it pretty low. Ben: we might want to talk about it. Maybe give it a medium priority.
there is some discussion on this, we may want to move this to high priority. Becky: We may want to propose this as a new techinque.
discuss title vs alt as a new techinque - high priority.
still medium on spacer gif.
For image maps, area element should exist in source code in reasonable order - David: is reasonable measurable? This may be a useful thing, but would be at mediom at best.
HTML forms, if multiple submit buttons, be sure the first one is the one you want to be default - becky: Medium to high priority. Not sure how to write the technique.
call it medium
Use of <link> element - existing
Text directionality - High priority
Use of meta tag with content-language - not lang attr - don't know if supported - Michael proposes medium - it needs investigation.
What to do if specify more than one language in header? - low priority.
<link rel="glossary"> - Medium Priority
Definition lists - kill.
Need an alternative to "target" since not allowed in strict HTML - high priority
Need an alternative to "target" since not allowed in strict HTML - High Priority. The violation of this is happening more and more. It is going to be a more of an issue with Ajax.
On leaving a data field - Kinda High Priority.
two techniques, more script then html and it's hight
Use links to cause page to refresh instead of automatic refresh - Medium
noframes, noscript - under 4.2 providing fall backs if outside your base line - David: high priority if not in base line. We do have techniques.
Fallback mechanism for applets (if applet not in baseline) need alternative mechanism for functionality - sounds like a general technique - this is saying you need functional fallback. Michael: this is hight priority. Becky: do you need a link to another page? It does effect the success of the base line. High Priority. Not sure where it goes, we do need to say something. David says maybe in HTML.
Label element for most controls, alt for image input, value for most buttons, text for button element - Existing may need to add one or two things.
"Creating Invisible labels for form elements" is mapped here. Should remap to L1SC4 - in css - controversial - existing in css
Using images as list item bullets (removed?) (1.1 L1 SC4) - should be in HTML to direct to css - medium
Background images are being used freq now for decorative images (1.1 L1 SC4) - high with a note telling dif btwn decorative and non decorative
Use CSS for non-essential background audio (1.1 L1 SC4) - medium
# Positioning, styling (1.3 L1 SC1) - existing - low
# Not using CSS as the only way to indicate a blockquote (1.3 L2 SC1) - kill!!!!!
covered in html
Don't put stuff out of sequence (1.3 L3 SC1) - medium - shawn has interesting input
maybe a high priority
bob easton - get him to add to the blog to encourage people to provide solutions
For background images and colors (1.4 L1 SC1) - layered divs - medium
Layered divs (1.4 L1 SC1) - high
Using foreground and background colors (1.4 L3 SC1) - medium
its about what code you use to make colors like bg transparent etc
<wendy> http://www.w3.org/TR/WCAG20-CSS-TECHS/#colors-backgrounds
Switch between using animated vs. Static images (2.2 L2 SC1) - kill
wc: maybe Yvette has a technique
... if so let her submit, she may be in the group for that, if so she's
welcome to do it
# Foreground/background issues (2.3 L3 SC1) - kill for css
Allow keyboard users to view skip links (2.4 L2 SC2) - wendy says wai site blends in that area but does not hide it, might be a technique - high
# Negative technique around illogical HTML source order corrected by CSS (2.4 L3 SC1) - kill
Make sure people notice the text summary by using diff. Presentation style (3.1 L3 SC5) - low
CSS inherit w/inherit property children will accept computed value of parent (3.2 L1 SC1) - medium - if you do it things will be more consistency
# CSS about indenting text. Not properly mapped. (3.2 L2 SC1) - high