23380 2013-09-27 09:36:17 +0000 review other aria state mappings to see if they need to be explicitly allowed 2014-01-13 16:49:36 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Windows NT RESOLVED WORKSFORME a11y, CR P2 normal --- 1 faulkner.steve faulkner.steve faulkner.steve lwatson mike public-html-admin public-html-wg-issue-tracking travil public-html-bugzilla oldest_to_newest 93941 0 faulkner.steve 2013-09-27 09:36:17 +0000 "Element that is disabled The aria-disabled state set to "true" Element that is inert The aria-disabled state set to "true" " Element that is a candidate for constraint validation but that does not satisfy its constraints The aria-invalid state set to "true" 98328 1 faulkner.steve 2014-01-13 16:49:36 +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: works for me Change Description: no chang Rationale: after discussion on ARIA call agreed that the current mappings are fine: http://lists.w3.org/Archives/Public/public-pfwg/2014Jan/0008.html