15:56:28 RRSAgent has joined #a11y-bugs 15:56:28 logging to http://www.w3.org/2010/11/23-a11y-bugs-irc 15:57:26 Meeting: HTML Accessibility Bug-Triage 15:57:28 Chair: Martin_Kliehm 15:57:30 Regrets: Laura_Carlson, Marco_Ranon 15:57:32 agenda+ Finde scribe 15:57:33 agenda+ Accessible fallback mechanisms for embedded content 15:57:35 agenda+ Sifting of NEW bugs 15:57:37 agenda+ Assign homework for next week 15:58:15 agenda: http://lists.w3.org/Archives/Public/public-html-a11y/2010Nov/0229.html 15:58:41 I'm logging. I don't understand 'draft logs', kliehm. Try /msg RRSAgent help 15:58:56 I'm logging. I don't understand 'make logs', kliehm. Try /msg RRSAgent help 15:59:33 I have made the request to generate http://www.w3.org/2010/11/23-a11y-bugs-minutes.html kliehm 16:01:43 WAI_PFWG(HTML_TF)11:00AM has now started 16:01:49 +kliehm 16:03:41 I have made the request to generate http://www.w3.org/2010/11/23-a11y-bugs-minutes.html kliehm 16:05:42 +Michael_Cooper 16:10:09 zakim, move to next agendum 16:10:09 agendum 1. "Finde scribe" taken up [from kliehm] 16:10:33 zakim, move to next agendum 16:10:33 agendum 1 was just opened, kliehm 16:10:44 zakim, close this item 16:10:44 agendum 1 closed 16:10:45 I see 3 items remaining on the agenda; the next one is 16:10:47 2. Accessible fallback mechanisms for embedded content [from kliehm] 16:11:05 zakim, move to next agendum 16:11:05 agendum 2. "Accessible fallback mechanisms for embedded content" taken up [from kliehm] 16:29:21 Discussion of uses cases 16:29:25 considered the following: 16:29:27 Short text alternative can substitute for the object, sometimes on its own and sometimes complemented by an additional "long text alternative". Normally, short text alternatives aren't provided if direct accessibility is possible, but it may still be used if direct accessibility for whatever reason isn't enabled (e.g., canvas makes a simple image and there is no need to enable full shadow... 16:29:28 ...DOM support). 16:29:30 Long text alternative can substitute for the object, fairly completely. Normally it complements a short text alternative but in the case of transcripts may stand on its own. 16:29:31 Label identifies the object and tells the user if they want to go into it more. This has both non-accessibility and accessibility use cases. Frequently confounded with short text alternatives, it's a distinct use case and optimally should have a different implementation. Generally, if a label is provided, a short text alternative would be redundant and is not separately required. 16:29:33 Summary is more than a short text alternative, but not the complete replacement that a long text alternative should be. Like a label, it may help a user decide whether to explore more, or may be a sufficient overview of the object in many cases. 16:29:37 Advisory / tooltip is a kind of text label that is usually displayed as a tooltip. Although frequently taken from short text alternatives or captions, this is not an accessibility use case. It is in the table to show that it is a distinct use case and should not be confounded with other accessibility fallbacks. 16:29:41 Idiosyncratic direct accessibility means the object content itself provides ways to make it accessible, e.g., caption formats in video, features of SVG, the shadow DOM of canvas, etc. Generally, if a format supports direct accessibility it may still benefit from a label, but should not require a short or long text alternative. However, some objects may not enable the direct accessibility and... 16:29:46 ...still require external text alternatives, such as a short text alternative for a simple image implemented with canvas, or a transcript (i.e., long text alternative) for an audio. Note that for embed and object, this depends on features of the loaded content language, so these elements may or may not require separate fallbacks within the HTML. 16:29:50 Specify none needed is for formats that need to be able to indicate that they are "presentational" and no accessibility fallback is needed. 16:30:12 discussed which of these use cases apply to which types of embedded content 16:31:10 action: Michael to send his embedded content analysis to the task force list 16:32:28 zakim, move to next agendum 16:32:28 agendum 3. "Sifting of NEW bugs" taken up [from kliehm] 16:33:03 http://www.w3.org/Bugs/Public/show_bug.cgi?id=10660 16:33:03 http://www.w3.org/Bugs/Public/show_bug.cgi?id=10660 16:36:42 Marco_Ranon has joined #a11y-bugs 16:48:48 http://www.w3.org/Bugs/Public/show_bug.cgi?id=11140 16:49:01 related to the above 16:51:24 http://www.w3.org/Bugs/Public/show_bug.cgi?id=11999 16:52:10 s/11999/11199/ 16:56:35 Bug triage sub-team thinks this is not a HTML A11Y TF priority. The primary 16:56:37 accessibility need is to provide headings at all; providing them in an outline 16:56:38 or clearly associated with landmarks is helpful but only if implemented 16:56:40 consistently. Further, HTML 5 provides various ways to achieve this (though 16:56:42 none of them are mandatory). There could be some value in looking more closely 16:56:44 at section types aka landmarks in HTML.next, but don't think we should in the 16:56:45 HTML 5 timeframe. Furthermore, the issue is more with user agent presentation 16:56:47 existing heading features than with the HTML spec itself. 16:56:58 http://www.w3.org/Bugs/Public/show_bug.cgi?id=11207 16:59:44 Bug triage sub-team think this is a HTML A11Y TF priority, is already in active discussion with the media sub-group. 17:00:09 http://www.w3.org/Bugs/Public/show_bug.cgi?id=11238 17:03:32 Adding a11yTF keyword 17:03:34 http://www.w3.org/Bugs/Public/show_bug.cgi?id=11242 17:07:32 Bug triage sub-team agrees this is an A11Y TF priority. However, it is clear this will come back as needsinfo in its current state. Assigning to Rich to address within the canvas sub-team and provide the needed info. Assign to Ian when complete. 17:07:35 http://www.w3.org/Bugs/Public/show_bug.cgi?id=11279 17:09:44 Bug triage sub-team doesn't think this is a A11Y TF priority. It's not an HTML feature, just a spec clarity issue. Our understanding is there is a specific reason for the phrasing approach, and doesn't need task force involvement. 17:11:36 zakim, move to next agendum 17:11:36 agendum 4. "Assign homework for next week" taken up [from kliehm] 17:12:09 Homework for next week: shepherding Michael's post regarding embedded content to the list. 17:13:00 -kliehm 17:13:01 -Michael_Cooper 17:13:03 WAI_PFWG(HTML_TF)11:00AM has ended 17:13:05 Attendees were kliehm, Michael_Cooper 17:13:19 regrets- Marco_Ranon 17:13:29 present+ Marco_Ranon 17:13:38 I have made the request to generate http://www.w3.org/2010/11/23-a11y-bugs-minutes.html kliehm 17:14:03 present+ Martin_Kliehm 17:14:06 I have made the request to generate http://www.w3.org/2010/11/23-a11y-bugs-minutes.html kliehm 17:14:31 present- kliehm 17:14:35 I have made the request to generate http://www.w3.org/2010/11/23-a11y-bugs-minutes.html kliehm 17:14:51 scribe: MichaelC 17:15:07 I have made the request to generate http://www.w3.org/2010/11/23-a11y-bugs-minutes.html kliehm 17:15:41 scribe: Martin_Kliehm 17:15:48 I have made the request to generate http://www.w3.org/2010/11/23-a11y-bugs-minutes.html kliehm 17:17:55 zakim, please part 17:17:55 Zakim has left #a11y-bugs 17:18:03 rrsagent, please part 17:18:03 I see 1 open action item saved in http://www.w3.org/2010/11/23-a11y-bugs-actions.rdf : 17:18:03 ACTION: Michael to send his embedded content analysis to the task force list [1] 17:18:03 recorded in http://www.w3.org/2010/11/23-a11y-bugs-irc#T16-31-10