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 23376 - ARIA: Strong Native Semantics table should defined implicit non-required state on form elements (Currently defines required state, but not the implicit inverse)
Summary: ARIA: Strong Native Semantics table should defined implicit non-required stat...
Status: RESOLVED DUPLICATE of bug 23377
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y Task Force (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: This bug has no owner yet - up for the taking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 23377 23378
  Show dependency tree / graph
 
Reported: 2013-09-26 23:28 UTC by James Craig
Modified: 2014-05-08 17:57 UTC (History)
1 user (show)

See Also:

Attachments

Description James Craig 2013-09-26 23:28:39 UTC 
@required is a Boolean attribute in HTML.
@aria-required is a "true/false" (boolean) attribute in ARIA.

The spec currently defines in the Strong Native Semantics table that:

input element that is required = The aria-required state set to "true"…
select element with a required attribute = The aria-required state set to "true"…
textarea element with a required attribute = The aria-required state set to "true"…

but since the HTML host language attribute is Boolean, the same elements *without* the required attribute defined are implicitly *not* required. Therefore, the strong native semantics table should also include:

input element that is not required = The aria-required state set to "false"…
select element without a required attribute = The aria-required state set to "false"…
textarea element without a required attribute = The aria-required state set to "false"…

Otherwise, the spec is implying that "HTML true is in conflict with ARIA false" but "HTML false is not in conflict with ARIA true", and defining one-way conflict resolution does not make sense for a Boolean state like this.


Likewise:
Element that is disabled = The aria-disabled state set to "true"

So the table should also include:
Element that is not disabled = The aria-disabled state set to "false"
Comment 1 James Craig 2013-09-26 23:29:11 UTC 
Related to bug 23370
Comment 2 James Craig 2013-09-27 17:34:56 UTC 
Duping out to the clone.

*** This bug has been marked as a duplicate of bug 23377 ***
Comment 3 James Craig 2014-05-08 16:42:45 UTC 
I think this one was resolved erroneously. Both of the cloned issues tackle a different problem.
Comment 4 James Craig 2014-05-08 17:55:40 UTC 
(In reply to James Craig from comment #3)
> I think this one was resolved erroneously. Both of the cloned issues tackle
> a different problem.

Sorry. I mixed up 23370 and 23377. I do agree that this is a duplicate of bug 23377.

*** This bug has been marked as a duplicate of bug 23377 ***
Comment 5 James Craig 2014-05-08 17:57:27 UTC 
Continuing list discussion. I think the HTML spec is no longer in conflict with itself, but I still think it should be in the Strong table, not the Implicit (Weak) table.