This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 12244 - Warn when interactive/forms associated content appears inside role=childrenArePresentational elements
Summary: Warn when interactive/forms associated content appears inside role=childrenAr...
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: a11y, aria
Depends on:
Reported: 2011-03-05 04:16 UTC by Leif Halvard Silli
Modified: 2011-08-04 05:16 UTC (History)
8 users (show)

See Also:


Description Leif Halvard Silli 2011-03-05 04:16:27 UTC
ARIA has the presentational children consept:

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.

    Internactive content:
    Form associated content
Comment 1 Michael Cooper 2011-03-08 16:25:34 UTC
Bug triage sub-team thinks this is not a A11Y TF priority, can be worked out by original filer.
Comment 2 Ian 'Hixie' Hickson 2011-05-06 00:56:26 UTC
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:

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.
Comment 3 Michael[tm] Smith 2011-08-04 05:16:18 UTC
mass-move component to LC1