- From: Joanmarie Diggs <[email protected]>
- Date: Wed, 12 Sep 2018 16:50:40 -0400
- To: Carolyn MacLeod <[email protected]>
- Cc: [email protected], [email protected], [email protected]
Aw hell. Two spaces? I'll comment on the issue as I think user agents might be simplifying whitespace. (Which isn't necessarily a bad thing.) Thanks! --joanie On 09/12/2018 04:47 PM, Carolyn MacLeod wrote: > Ah, good. > > So I agree with your initial assessment that the accessible name should > be "foo baz" (with 2 spaces) from the wrapping label element. Also, the > accessible description should be "bar" from the title (since it was not > used in the name calculation). > > Sorry to take so long to come to the same conclusion, but I had to walk > through all the hoops to get there. <grin> > > Car > > > ----- Original message ----- > From: Joanmarie Diggs <[email protected]> > To: Carolyn MacLeod <[email protected]> > Cc: [email protected], [email protected], > [email protected] > Subject: Re: AccName test expectations bug + prototype bug? > Date: Wed, Sep 12, 2018 4:11 PM > > On 09/12/2018 04:05 PM, Carolyn MacLeod wrote: > > HTML AAM section 5.1 > > > <https://93seqoby0t.proxynodejs.usequeue.com/html-aam/#input-type-text-input-type-password-input-type-search-input-type-tel-input-type-url-and-textarea-element> > > (which does NOT apply, because type="button") says to use label > element > > first, otherwise use title. > > > > But HTML AAM section 5.2 > > > <https://93seqoby0t.proxynodejs.usequeue.com/html-aam/#input-type-button-input-type-submit-and-input-type-reset> (which > > is the one for type="button", so does apply) *does not mention label > > element* at all (other than by reference to AccName), so it would > > resolve to title. > > That's a bug which the HTML-AAM editors are planning to fix. See > https://93to8ehqgm.proxynodejs.usequeue.com/w3c/html-aam/issues/148 > > --joanie > > > > >
Received on Wednesday, 12 September 2018 20:51:17 UTC