This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
"4. HTML attribute to Accessibility API State and Property Mapping Matrix " Longdesc is not described. Please do. * Note that you do describe <frame> and <frameset>, despite that they too are obsoleted in HTML5 http://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html#el-47
(In reply to comment #0) > "4. HTML attribute to Accessibility API State and Property Mapping Matrix > > " Longdesc is not described. Please do. > > * Note that you do describe <frame> and <frameset>, despite that they too are > obsoleted in HTML5 > http://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html#el-47 Hi leif, this was an oversight due to the attribute table being sourced from the the HTMl5 spec. I have now added longdesc.
(In reply to comment #1) > Hi leif, this was an oversight due to the attribute table being > sourced from the the HTMl5 spec. I have now added longdesc. Referring to our conversation on Twitter, https://twitter.com/stevefaulkner/statuses/177775477753262080 could the text make clear that the MSAA mapping/implementatio is incorrect and misleading and unusable as a guide for understanding and implementing @longdesc?
bhl supplied pointer to firefox implementation: I'd normally look at what Gecko has done as part of baking IA2 into MSAA: https://mxr.mozilla.org/mozilla-central/source/accessible/src/html/nsHTMLImageAccessible.cpp need to update IA2 to reflect this
IA2 bug. I'm not the right owner.
I *think* this is about the HTML-AAM, specifically the mapping entries for @longdesc: http://rawgit.com/w3c/aria/master/html-aam/html-aam.html#att-longdesc I'm not the expert here, although it looks like the mappings are done. Resetting the assignee to the default.