W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2016

Re: Question: testing for non-unique id values SC 4.1.1

From: Andrew Kirkpatrick <akirkpat@adobe.com>
Date: Mon, 3 Oct 2016 17:54:09 +0000
To: "jon.avila@ssbbartgroup.com" <jon.avila@ssbbartgroup.com>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Message-ID: <8A81F231-97C4-4AFE-8D75-8AEAE72596FC@adobe.com>
>>
>>>We ran into a page on the desktop where a left quote was used on an attribute on the HTML element along with a matching straight quote.  A desktop assistive technology couldn't see the page content correctly.   The page looked fine.
>
>> Fails 4.1.2
>
>How could this be a SC 4.1.2 issue?  It occurred on the HTML element itself which is not a user interface component and is not covered under SC 4.1.2.    it was already discussed on this list that 4.1.2 can only apply to individual components and not the page itself.

Sorry, I thought that this was a control for some reason. If this is just page content I’d likely say that it is a 1.3.1 issue.

>>>On Android we ran into an issue with TalkBack where a combo box was completely invisible in Firefox.  Turns out the first item in the option list had a blank value and no label attribute.  Blank values must have a label attribute to validate.  Adding the label attribute solved the issue.
>
>> Fails 4.1.2
>
>I don't think that's intuitive or clear at all.  The intended value is blank and was blank and nbs was used in the textContent of the option.  The fact that the label attribute should have been used doesn't fall under 4.1.2 because adding aria-label to the option element didn't solve the issue -- so even with an accessible name via ARIA the bug still existed.  So it met the criteria of name, role, state, and value.

Isn’t the issue that the value isn’t being read?  I might need to see an example to understand why this isn’t 4.1.2.

>>Any that cause problems that do not fail under any other SC?  :)
>
>ARIA markup is very particular about how the items are nested and where the tabindex is set, etc.  This doesn't relate to name, role, value, or events and isn't covered under 4.1.2.  The appropriate structure of the ARIA markup with required child elements is not clearly covered elsewhere.  I'm sure you will say it's covered un SC 1.3.1 -- but I don't think that's how it's currently seen by most of the world.

Sure, it won’t always be 4.1.2, but there is something going wrong in each of these circumstances that rolls up to a real problem for the user, right? I just haven’t seen any situations where a 4.1.1 failure isn’t also a failure of something else.

AWK
Received on Monday, 3 October 2016 17:54:40 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:06 UTC