This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
As a frequent "validator"-user I noticed that not using WAI-ARIA for lists (ul/li) is suddenly flagged as an Error. This is the case today, but was not 2 days ago, on thursday. Has the use of aria for lists suddenly become mandatory, or is this a validator issue?
It's a validator issue. I made some updates today today to the ARIA support and it seems I likely introduced some unintended change. Thanks for the heads up. I will look into it and fix it as soon as possible and then respond here again.
Great to hear! Thought I was in trouble there... In any case, looking forward to the fix.
OK, I've fixed it now, and pushed the fix to http://validator.w3.org/nu/ and http://validator.w3.org Thanks again for reporting this quickly
I've noticed I still get an aria error for an input button (<input type="submit" value="submit" name="submit" class="submit-button"/>): "Element input is missing one or more of the following attributes: aria-checked, aria-expanded, aria-valuemax, aria-valuemin, aria-valuenow, aria-valuetext, role." The list errors are all gone now!
(In reply to comment #4) > I've noticed I still get an aria error for an input button (<input > type="submit" value="submit" name="submit" class="submit-button"/>): > > "Element input is missing one or more of the following attributes: > aria-checked, aria-expanded, aria-valuemax, aria-valuemin, aria-valuenow, > aria-valuetext, role." Thank you thank you thank you for catching this! Fixed and pushed to http://validator.w3.org/nu/ Definitely let me know if you find any more problems
Will do! Thanks for the swift response!