Re: AccName uncertainty for form field label

Seems to me that if it were to label the nested input, then it’d only be doing so to mitigate against author error AND there must be no input with the ID that matched the label’s for attribute.

 

From: Sina Bahram <sina@sinabahram.com>
Organization: Prime Access Consulting
Date: Thursday, March 5, 2020 at 6:14 PM
To: 'Bryan Garaventa' <bryan.garaventa@levelaccess.com>, 'ARIA' <public-aria@w3.org>
Subject: RE: AccName uncertainty for form field label
Resent-From: <public-aria@w3.org>
Resent-Date: Thu, 05 Mar 2020 23:14:01 +0000

 

I think it’s completely ambiguous.

 

The ‘for’ attribute is pointing somewhere else, so we need to decide whether encapsulation supersedes programmatic linking.

 

If later on there was an input with an id of ‘test’, I do think that it should also be “email:” , which of course would be suboptimal from an accessibility perspective, but at least not the worst situation of being unlabeled.