[whatwg] use of article to markup comments
Over on the HTML WG list [1] we have been discussing the use of the article element to mark up comments. I have sketched out a few alternative possibilities to the current recommendation in the spec of using the article element as it has been indicated by users who consume the semantics that its use is suboptimal. I am bringing this over here as well as one of the suggestions I have [2] made may include implementation changes [1] http://lists.w3.org/Archives/Public/public-html/2013Jan/thread.html#msg109 [2] http://www.html5accessibility.com/tests/comments.html -- with regards Steve Faulkner Technical Director - TPG www.paciellogroup.com | www.HTML5accessibility.com | www.twitter.com/stevefaulkner HTML5: Techniques for providing useful text alternatives - dev.w3.org/html5/alt-techniques/ Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Re: [whatwg] Assigning media resources represented as DOM objects to a media element
On Thu, Jan 24, 2013 at 11:51 AM, Robert O'Callahan rob...@ocallahan.org wrote: In fact, he cited you in his argument against src! Now that's ironic :-). :-) Context: http://lists.w3.org/Archives/Public/public-media-capture/2012Aug/0077.html I think overloading could work here actually, if getting .src returned the object and .getAttribute(src) returned about:objecturl or some such, but it does not matter much. I think if we add this we should also do it for img. -- http://annevankesteren.nl/
Re: [whatwg] use of article to markup comments
On 01/25/2013 03:44 AM, Steve Faulkner wrote: Over on the HTML WG list [1] we have been discussing the use of the article element to mark up comments. I have sketched out a few alternative possibilities to the current recommendation in the spec of using the article element as it has been indicated by users who consume the semantics that its use is suboptimal. I am bringing this over here as well as one of the suggestions I have [2] made may include implementation changes [1] http://lists.w3.org/Archives/Public/public-html/2013Jan/thread.html#msg109 [2] http://www.html5accessibility.com/tests/comments.html I would be concerned that recommending the use of ul would simply confuse matters further, and lead to messier, unnecessarily verbose markup. A clean list of comments is fine, but most comments end up tree-structured, not lists. Tree-uls are quite verbose compared to simply nesting articles. (It makes some sense, I suppose, to think of comments as a list, but *unordered*? If you're going to group them at all, wouldn't the order be important? Bruce Lawson ( http://lists.w3.org/Archives/Public/public-html/2013Jan/0111.html)'s observation that comments are heavily dependent on context would seem to support the idea that it *is* important, especially since some comments are responses to others.) Robin Berjorn ( http://lists.w3.org/Archives/Public/public-html/2013Jan/0115.html) made a suggestion to wrap comment article elements inside a details element, which seems like a good approach, both in terms of semantics and practical result. *However*, I don't see anything wrong or confusing about nested articles. I think it makes perfect sense. Someone (can't find it now) wrote that the goal of AT applications is to read the contents of the main article, without comments or other distractions - the fact that a comment article is nested inside another automatically implies that it is *supportive*, and not an integral part of the main article itself (it can be excluded without negative impact). -- Adrian Testa-Avila adr...@custom-anything.com http://www.custom-anything.com/contact follow on facebook http://www.facebook.com/customanything
Re: [whatwg] Feedback on a variety of elements
On Sat, 19 Jan 2013, Steve Faulkner wrote: On 19 January 2013 01:41, Ian Hickson i...@hixie.ch wrote: I don't see any useful explanation of how to use aria-haspopup here. suggest you look at definition of aria-haspopup in the ARIA spec That's what I looked at before this conversation began. My point stands. aria-has-popup is pointless because it doesn't define an interaction model. There's no useful way for an AT to expose it. -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Feedback on a variety of elements
Ian Hickson i...@hixie.ch wrote: My point stands. aria-has-popup is pointless because it doesn't define an interaction model. There's no useful way for an AT to expose it. oh I missed your point, suggest you bring it up with the browser implementers who have implemented aria-haspopup to map to corresponding properties in MSAA, IA2, ATK/AT-SPI, UIA and Mac AX accessibility API's and the AT's such as JAWS, VoiceOver, NVDA etc, that expose aria-haspopup, as provided by the browser, to users. [1] http://www.w3.org/WAI/PF/aria-implementation/#mapping_state-property On 25 January 2013 18:07, Ian Hickson i...@hixie.ch wrote: On Sat, 19 Jan 2013, Steve Faulkner wrote: On 19 January 2013 01:41, Ian Hickson i...@hixie.ch wrote: I don't see any useful explanation of how to use aria-haspopup here. suggest you look at definition of aria-haspopup in the ARIA spec That's what I looked at before this conversation began. My point stands. aria-has-popup is pointless because it doesn't define an interaction model. There's no useful way for an AT to expose it. -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' -- with regards Steve Faulkner Technical Director - TPG www.paciellogroup.com | www.HTML5accessibility.com | www.twitter.com/stevefaulkner HTML5: Techniques for providing useful text alternatives - dev.w3.org/html5/alt-techniques/ Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Re: [whatwg] Assigning media resources represented as DOM objects to a media element
On Sat, Jan 26, 2013 at 2:36 AM, Anne van Kesteren ann...@annevk.nl wrote: I think overloading could work here actually, if getting .src returned the object and .getAttribute(src) returned about:objecturl or some such, but it does not matter much. Then let's not change it again please :-). Rob -- Jesus called them together and said, “You know that the rulers of the Gentiles lord it over them, and their high officials exercise authority over them. Not so with you. Instead, whoever wants to become great among you must be your servant, and whoever wants to be first must be your slave — just as the Son of Man did not come to be served, but to serve, and to give his life as a ransom for many.” [Matthew 20:25-28]
