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 7634 - Text equivalent computation: should the user-entered value be part of the name?
Summary: Text equivalent computation: should the user-entered value be part of the name?
Status: RESOLVED WONTFIX
Alias: None
Product: ARIA
Classification: Unclassified
Component: Core AAM (show other bugs)
Version: 1.0
Hardware: PC Windows XP
: P1 normal
Target Milestone: ---
Assignee: Andi Snow-Weaver
QA Contact: ARIA UA Implementors
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-15 16:05 UTC by Andi Snow-Weaver
Modified: 2010-12-09 15:11 UTC (History)
1 user (show)

See Also:

Attachments

Description Andi Snow-Weaver 2009-09-15 16:05:29 UTC 
I'm not sure I agree with the idea of the user-entered value of a form element
contributing to the name... That should be the value in a name/value pair, not
part of the name.  That's what IE does.  Does FF add the user-entered value to
the name now?
Comment 2 Andi Snow-Weaver 2010-01-19 15:31:12 UTC 
Proposal:

In section 4.6.1, item 2B, 
http://www.w3.org/WAI/PF/aria-implementation/#mapping_additional_nd

<change>
For such cases, include the value of the embedded control as part of the text alternative in the following manner: 
</change>

<to>
For such cases, user agents MAY include the value of the embedded control as part of the text alternative in the following manner: 
</to>

Need to review this with ARIA TF since the same text is used in both the WAI-ARIA spec and the UAIG.
Comment 3 Andi Snow-Weaver 2010-10-28 15:28:48 UTC 
Cynthia to test what IE does for this case.
Comment 4 Cynthia Shelly 2010-11-11 02:12:06 UTC 
IE does not add the user-entered value of an <input type=text> to the name.  I tried it with and without labels, in IE8 and IE9 Beta.

I think IE's behavior is correct.  If the AT wants to repair by reading the value when the name is null, that's fine, but the browser should be reporting what is in the markup.
Comment 5 Andi Snow-Weaver 2010-11-11 12:26:05 UTC 
So we have a conflict. FF includes it, IE doesn't. 

Since this is in both the spec and the UAIG, we can't just change it in the UAIG. Note sent to PF mailing list:

http://lists.w3.org/Archives/Member/w3c-wai-pf/2010OctDec/0069.html
Comment 6 David Bolter 2010-11-11 13:52:55 UTC 
I'm checking with my team on this.