15:48:09 RRSAgent has joined #a11y-bugs 15:48:09 logging to http://www.w3.org/2010/11/16-a11y-bugs-irc 15:48:17 Zakim has joined #a11y-bugs 15:48:28 rrsagent, this will be a11y 15:48:28 I'm logging. I don't understand 'this will be a11y', kliehm. Try /msg RRSAgent help 15:49:51 Meeting: HTML Accessibility Bug-Triage 15:49:53 Chair: Martin_Kliehm 15:49:54 Regrets: Laura_Carlson, Joshue_O_Connor 15:49:56 agenda+ Accessible fallback mechanisms for embedded content 15:49:57 agenda+ Assign homework for next week 15:50:51 agenda: http://lists.w3.org/Archives/Public/public-html-a11y/2010Nov/0203.html 15:51:38 rrsagent, draft minutes 15:51:38 I have made the request to generate http://www.w3.org/2010/11/16-a11y-bugs-minutes.html kliehm 15:51:56 rrsagent, make logs world-viewable 15:52:06 rrsagent, make logs world 15:52:40 rrsagent, set logs world 15:53:22 Marco_Ranon has joined #a11y-bugs 15:54:23 Hi Martin. Sure. i'm already online. can you see me. some people can't even if i'm available. 15:54:48 s/Hi Martin. Sure. i'm already online. can you see me. some people can't even if i'm available.// 15:57:18 rrsagent, draft minutes 15:57:18 I have made the request to generate http://www.w3.org/2010/11/16-a11y-bugs-minutes.html kliehm 15:58:38 WAI_PFWG(HTML_TF)11:00AM has now started 15:58:45 +kliehm 16:00:44 MichaelC has joined #a11y-bugs 16:01:17 zakim, move to next agendum 16:01:17 agendum 1. "Accessible fallback mechanisms for embedded content" taken up [from kliehm] 16:01:33 +Michael_Cooper 16:10:52 Question of how to proceed 16:11:12 think we should send analysis of issues and get discussion 16:11:21 think we should file bugs ourselves when some form of consensus is clear 16:11:37 I found some high-level issues in my review 16:12:00 there are 3 types of fallbacks: 1) non-support of the HTML element; 2) non-support of the loaded content technology; 3) accessibility 16:12:37 these are confounded and in practice if the browser supports the content technology it doesn't make the accessibility fallback available 16:13:19 use of attribute for fallback (e.g., @alt) means it can't be internationalized, contain rich content 16:14:12 http://dev.opera.com/articles/view/more-accessible-html5-video-player/ 16:14:16 present+ Marco_Ranon 16:14:19 in HTML 4 had no ability to mark "this element needs no fallback", leading to heuristic uses of @alt which have interoperability problems but are deeply philosophically entrenched 16:14:55 @title and @name have been used for accessibility fallbacks, but they have unspecified behavior in this scenario 16:16:06 q+ to talk about mixed fallback and other content 16:17:13 ack michael 16:17:13 MichaelC, you wanted to talk about mixed fallback and other content 16:18:35 I am also concerned that content models mix fallback elements with , , etc. that are relevant to the parent element 16:19:08 prefer an explicit element, e.g., , to contain the fallback content 16:22:28 Images and MathML have @alt and @alttext on the container element providing some kind of title or summary. Elements such as video, audio, SVG, source, and map has some kind of @alt on a child element, but nothing that serves as a title or summary. 16:23:41 there is need to "label" elements e.g.,