15:00:29 RRSAgent has joined #a11y-bugs 15:00:29 logging to http://www.w3.org/2011/09/13-a11y-bugs-irc 15:00:33 rrsagent, make log world 15:00:46 meeting: Bug Triage sub-team, HTML A11Y TF 15:00:49 chair: Léonie_Watson 15:05:41 zakim, this is 2119 15:05:41 ok, MichaelC; that matches WAI_PFWG(HTML_TF)11:00AM 15:05:46 zakim, who's on the phone? 15:05:46 On the phone I see ??P26, ??P32, ??P6, Michael_Cooper 15:06:19 present: Léonie_Watson, Everett_Zufelt, Hans_Hillen, Michael_Cooper 15:06:32 regrets: Gez_Lemon, Marco_Ranon, Joshue_O_Connor 15:09:32 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12776 15:10:25 MC: I don't think the tf needs to work on this 15:12:29 MC: if anything comes out of this, we can track it then 15:12:48 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12848 15:12:58 MC: we don't need to track this 15:13:56 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12873 15:15:40 LW: Reporter wants to add an example of alt text scenario 15:17:03 LW: Don't track, has already been fixed and closed 15:17:11 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12874 15:19:06 HH: This concerns http://www.w3.org/TR/2011/WD-html-alt-techniques-20110113/ 15:21:28 HH: Specifically, example 2.5: http://www.w3.org/TR/2011/WD-html-alt-techniques-20110113/#hag21 15:22:03 MC: Data table as alternative is more useful than image map regions with alt text. Don't track 15:22:17 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12875 15:22:59 MC: Don't track 15:23:09 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12876 15:23:23 LW: I don't think we need to track this one 15:23:35 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12877 15:24:00 LW: We don't need to track it 15:24:16 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12900 15:26:12 HH: Doesn't seem to be a11y related, should not need a11y keyword 15:26:41 MC: Landmark roles can be used instead of what the reporter is asking for 15:26:45 LW: don't track 15:27:01 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12964 15:27:56 LW: Taskforce should track this 15:28:08 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12971 15:30:54 MC: I don't think there is value in pushing this 'em' vs 'i' issue 15:31:01 LW: OK, we'll skip this one 15:31:37 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12984 15:31:57 LW: No need to track, duplicate of other alt related bugs 15:33:53 LW: We still needs Joshue's short list of bugs 15:34:29 scribe: MichaelC 15:35:02 topic: Bugs that may need a11y keyword 15:35:09 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12906 15:37:39 hh: add a11y and a11ytf keyword 15:38:02 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12985 15:40:20 hh: add a11y and a11ytf keyword 15:42:29 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12990 15:42:38 hh: not a TF priority 15:42:48 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12999 15:44:11 hh: complicated discussion in bug 15:46:39 mc: let's track, but not necessarily support, just follow 15:47:06 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12803 15:49:23 scribe: hhillen 15:49:26 LW: No need to track 15:49:44 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12834 15:51:21 LW: don't track 15:51:39 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12835 15:51:56 LW: Don't think we need to track this one 15:52:08 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12844 15:53:46 MC: I think this is one where we want to track it but not necessarily back it 15:54:28 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12885 15:57:27 MC: I don't think is has enough impact on accessibility at the moment but it may at some point 15:57:39 LW: Track it for now 15:57:59 http://www.w3.org/Bugs/Public/show_bug.cgi?id=12868 16:01:43 MC: I don't think we need to track it now, but it could come back later 16:02:09 HH: Doesn't seem high enough of a priority to track 16:02:30 LW: I'll take the a11ytf keyword out 16:04:52 EZ: None of my bugs were a11y related 16:04:55 topic: Bugs that don't need a11y keyword 16:07:04 -??P26 16:07:05 -??P6 16:07:10 -Michael_Cooper 16:08:22 Hans' list of items that doesn't need a11y keyword: 16:08:22 12898 : any idea when this will be up and running? 16:08:22 12899: select.size is an unsigned long limited to only non-negative numbers, but that concept doesn't exist 16:08:23 12901: Keep up the great work... One suggestion. Could you please align the Microdata part of the spec with Microformats and/or RDFa, instead of jnust defining yet another random markup. It would be really helpful for alot of developers who have invested time an 16:08:25 12902: Simplify input types (remove excessive date types) and add format attribute 16:08:27 12905: For the attribute "required" of checkbox element, I think it should be defined as "at least one is required" but not "which fields are required". So it's better use the same constraint validation with the radio element. That is if an element in the check 16:08:29 12907: The algorithm for parsing a legacy color value, steps 2 and 3, should be reversed. Given a case where string is a tab for instance, it should be treated as an empty string. 16:08:32 12908: How come we leave the first 128 characters and then divide the string into three equal parts? Last time I checked, 128 % 3 == 2. 16:08:35 12910: I think step 7 and 10 are pretty much the same thing, ie. s/[:alnum:]/0/g 16:08:37 12915: Note that Arabic and Persian Unicode digits could be used through UI 16:08:41 12918: I found that you limited the keywords acceptable for the meta-name attribute and for the link-rel attribute. In the specs you use exhaustive lists of allowed keywords. In my opinion you should only suggest keywords. See also http://webhel.blogspot.com/20 16:08:45 12923: Setting a reflecting attribute of type HTMLElement to something with no ID should set content attribute to empty string 16:08:48 12924: xml:base interaction with img element 16:08:50 12925: in the 1st example 3 'hr' are used like an anonymous 'h#' => 'hr' should move to 4.4. The final 'hr' is of a different kind and wouldn't be there if we had lists ('dl' here) nested inside 'p'. The second example is mostly like the first three 'hr', i.e. a 16:08:54 12926: The phrase "in a Document" is not consistently used in the specification 16:08:56 12927: Define what "content attribute's document" means 16:08:58 12929: [MIMESNIFF] needs to point to the draft by the websec working group 16:09:00 12930: Update CSS references (CSS 2.1 and CSS3 Color now a recommendation) 16:09:02 12931: On line 7 of the updateIndicator example, the attribute should be textContent instead of textContext 16:09:04 12935: should not auto-close ancestors 16:09:07 12937: Is there a fold/unfold TOC ? 16:09:08 12938: “The attribute value can remain unquoted if it doesn't contain spaces or […]” Please replace “spaces” with “space characters” (microsyntax) to avoid confusion. 16:09:11 12939: The group used to be defined as a very useful to represent tabular data. Among the various things needed for tabular data perusing is the data alignment. In v4.01 there is an "align" and a "char" attribute that make the attribute very useful t 16:09:15 12940: I suppose there's no longer a version number so no thing like "DOM5 HTML". 16:09:17 12942: Time element specification phrasing error (Section 4.6.10) 16:09:19 12943: Drop progress.position IDL or make it settable 16:09:21 12944: I found two useful references to XHTML5 in this document: 1.6 HTML vs XHTML States: " The second concrete syntax is the XHTML syntax, which is an application of XML. When a document is transmitted with an XML MIME type, such as application/xhtml+xml, then 16:09:25 12945: On setting, if the given element has an id attribute, then the content attribute must be set to the value of that id attribute. Otherwise, the IDL attribute must be set to the empty string." is strange and breaks reflection. If the given element isn't in 16:09:29 12946: first img element descendant of the element" doesn't define properly which element. First in document order? 16:09:32 12948: New feature request: GROUP tag What I'd like to achieve in HTML is to easily access a group of elements via Javascript using a single parent element (GROUP). The GROUP element would not under any circumstance affect the layout of the page, and would not b 16:09:36 12949: click() shouldn't have special powers over dispatching click event manually 16:09:38 12950: Require Byte-Order Mark (BOM) in UTF-8 encoded pages 16:09:40 12952: Remove typemustmatch 16:09:42 12955: Fire DOMContentLoaded at iframe when it is fired at contentWindow for convinience 16:09:44 12956: