16625 2012-04-04 09:48:27 +0000 [AAPI]:handling of "interesting" markup combinations. 2014-12-14 22:39:17 +0000 1 1 1 Unclassified HTML WG HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) unspecified PC Windows NT NEW http://lists.w3.org/Archives/Public/wai-xtech/2012Apr/0006.html a11y P2 normal --- 1 faulkner.steve faulkner.steve bhawkeslewis hans.hillen jason mike public-html-admin public-html-wg-issue-tracking sideshowbarker+html-a11y-api oldest_to_newest 66407 0 faulkner.steve 2012-04-04 09:48:27 +0000 Hey Steve I think one absolutely critical area to think about from an interoperability perspective is handling "interesting" markup combinations. For example, if you have an <li> that does not have a <ol>/<ul> parent, what does that get mapped to? Or, if you have an <li> that has a <ol>/<ul> parent, but the parent has a role attribute that maps it to (say) the "button" role, what does the <li> get mapped to? 116286 1 jason 2014-12-14 22:39:17 +0000 I agree that "interesting" markup combinations are something that should be tested against the proposed mappings and the accessible name and description calculation, as part of the work in making sure we've got those right. For example, see bug 25371. But I'm not sure we should be looking at cases of invalid markup. Neither the <li> without a <ol>/<ul> (or presumably <menu type="toolbar">) parent, or an <ol>/<ul> with role="button" are permitted.