12244 2011-03-05 04:16:27 +0000 Warn when interactive/forms associated content appears inside role=childrenArePresentational elements 2011-08-04 05:16:18 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED WONTFIX http://dev.w3.org/html5/spec/content-models.html#annotations-for-assistive-technology-products-aria a11y, aria P2 normal --- 1 xn--mlform-iua ian ayg cooper ian laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 46391 0 xn--mlform-iua 2011-03-05 04:16:27 +0000 ARIA has the presentational children consept: http://www.w3.org/TR/wai-aria/complete#childrenArePresentational For content that is the child of an element with a role of type "childrenArePresentational", ARIA 1.0 says that user agents SHOULD NOT expose them. Any button, link, etc inside a <div role=img><a href=link>text</a></div>, would thus normally not be accessible to AT users. Pointing to that link via aria-labelledby/-describedby would also not activate its interactivity - I don't think ARIA has any means bring back the interactivity of such an element - other than removing the parent role with the childrenArePresentational effect. Validators should warn when it detects interactive/forms associated content inside elements with a role which has the chilrenArePresentatinoal effect as it could mean that the author unintendedly hide some interactive/forms related content. References: Internactive content: http://dev.w3.org/html5/spec/content-models#interactive-content-0 Form associated content http://dev.w3.org/html5/spec/forms#form-associated-element 46545 1 cooper 2011-03-08 16:25:34 +0000 Bug triage sub-team thinks this is not a A11Y TF priority, can be worked out by original filer. 48162 2 ian 2011-05-06 00:56:26 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: I agree with the report, but it seems like something WAI-ARIA should require, not HTML: the same problem would exist if you were using SVG+ARIA or MathML+ARIA with no HTML in sight. 53678 3 mike 2011-08-04 05:16:18 +0000 mass-move component to LC1