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 23380 - review other aria state mappings to see if they need to be explicitly allowed
Summary: review other aria state mappings to see if they need to be explicitly allowed
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, CR
Depends on:
Blocks:
 
Reported: 2013-09-27 09:36 UTC by steve faulkner
Modified: 2014-01-13 16:49 UTC (History)
6 users (show)

See Also:

Attachments

Description steve faulkner 2013-09-27 09:36:17 UTC 
"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"
Comment 1 steve faulkner 2014-01-13 16:49:36 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:

   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