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 19715 - incorrect ARIA errors reported
Summary: incorrect ARIA errors reported
Status: RESOLVED FIXED
Alias: None
Product: HTML Checker
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Michael[tm] Smith
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-26 10:04 UTC by steve faulkner
Modified: 2013-04-20 07:10 UTC (History)
1 user (show)

See Also:


Attachments

Description steve faulkner 2012-10-26 10:04:11 UTC
when checking this page: http://juicystudio.com/tpg/rbc/combo.html

none of the ARIA errors appear to be correct.
<li> allows role="option" and any of the aria-* attributes used.

aria-activedescendent does not have have to be a desccednent element as reported;
"Error: The aria-activedescendant attribute must refer to a descendant element."
if the aria-owns property is used to point to a non DOM descendent (which it is)

Also on the qa-dev the follwoing error (incorrectly)on the input type=text element:
"Error: Attribute readonly not allowed on element input at this point."
Comment 1 Michael[tm] Smith 2013-04-20 07:09:00 UTC
(In reply to comment #0)
> when checking this page: http://juicystudio.com/tpg/rbc/combo.html
> 
> none of the ARIA errors appear to be correct.
> <li> allows role="option" and any of the aria-* attributes used.

Fixed now, I think. You can test at http://validator.w3.org/nu/

> aria-activedescendent does not have have to be a desccednent element as
> reported;
> "Error: The aria-activedescendant attribute must refer to a descendant
> element."
> if the aria-owns property is used to point to a non DOM descendent (which it
> is)

Fixed now, I think. See http://validator.w3.org/nu/

> Also on the qa-dev the follwoing error (incorrectly)on the input type=text
> element:
> "Error: Attribute readonly not allowed on element input at this point."

Fixed now. But not yet pushed to qa-dev. Please test at http://validator.w3.org/nu/ instead.