Sniffer should not suggest <label for> attribute for <input> fields with the "hidden" attribute

[vick08]

Presently, Sniffer flags the fields with the "hidden" attribute with an error because they do not have the associated label. This is obviously incorrect since "hidden" fields are used for passing the information to the server.

[luketw]

Hi,
When you mean "hidden" attribute, you mean <input type="hidden"> I take it, or are you referring to something else?
What is the exact message and standard reference you are getting? I'm trying to work out where I'm even looking at <input type="hidden">, so some details on the message you're getting would be helpful.

Thanks.

[vick08]

The message can be anything related to the input field, e.g. "absent label", "duplicated ID" or whatever else. I just got something like this: "Message Duplicate id attribute value some_id found on the web page."
I think the tool should basically ignore any field with the "hidden" attribute.

[luketw]

Hi,

Sorry for the length of time it took to get back to this.

Duplicate IDs cannot be ignored even when the input is hidden because that makes the document not well-formed, or at least failing http://www.w3.org/TR/WCAG20-TECHS/F77.html. Just because it's hidden, doesn't mean that it stops JavaScript from getting to it, and that's a problem in terms of programmatically determining what that ID represents.

I'm going to merge the "absent label" handling into #107. What will happen is the same as with hidden input types: if there is a label for a hidden attributed input then it will emit a warning, otherwise ignore it.

[vick08]

Thank you for your understanding. We are just trying to be pragmatic and want to make sure that the tool is usable in as flexible environment as possible.
This solution works for now.

On Nov 11, 2014, at 1:38 PM, Luke Wright notifications@github.com wrote:

Hi,

Sorry for the length of time it took to get back to this.

Duplicate IDs cannot be ignored even when the input is hidden because that makes the document not well-formed, or at least failing http://www.w3.org/TR/WCAG20-TECHS/F77.html. Just because it's hidden, doesn't mean that it stops JavaScript from getting to it, and that's a problem in terms of programmatically determining what that ID represents.

I'm going to merge the "absent label" handling into #107. What will happen is the same as with hidden input types: if there is a label for a hidden attributed input then it will emit a warning, otherwise ignore it.

—
Reply to this email directly or view it on GitHub.