- From: David MacDonald <david100@sympatico.ca>
- Date: Wed, 12 Sep 2018 18:05:42 -0400
- To: Carolyn MacLeod <Carolyn_MacLeod@ca.ibm.com>
- Cc: bryan.garaventa@ssbbartgroup.com, jdiggs@igalia.com, nurthen@adobe.com, public-aria@w3.org
- Message-ID: <CAAdDpDYhmE9YjYGkEG6x+jhcuFgLOW4YGWsm=PHV3370LZo2yw@mail.gmail.com>
I agree with “foo baz” Title doesn’t apply to accname where a label is present ... On Wed, Sep 12, 2018 at 5:39 PM Carolyn MacLeod <Carolyn_MacLeod@ca.ibm.com> wrote: > The 2 spaces is for your simpler variant: > <label for="test">foo <input id="test" type="button" name="test" > title="bar"> baz</label> > > As for the CSS ::before and ::after content in test case 661 > <https://www.w3.org/wiki/AccName_1.1_Testable_Statements#Name_test_case_661>, > I guess the accessible name would be "foobaz" (no space?) and the > accessible description would be " bar " (with space before and after?), > except that I'm not really sure about those. > > Car > > > > ----- Original message ----- > From: Joanmarie Diggs <jdiggs@igalia.com> > To: Carolyn MacLeod <Carolyn_MacLeod@ca.ibm.com> > Cc: bryan.garaventa@ssbbartgroup.com, nurthen@adobe.com, > public-aria@w3.org > Subject: Re: AccName test expectations bug + prototype bug? > Date: Wed, Sep 12, 2018 4:51 PM > > 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 <jdiggs@igalia.com> > > To: Carolyn MacLeod <Carolyn_MacLeod@ca.ibm.com> > > Cc: bryan.garaventa@ssbbartgroup.com, nurthen@adobe.com, > > public-aria@w3.org > > 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://w3c.github.io/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://w3c.github.io/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://github.com/w3c/html-aam/issues/148 > > > > --joanie > > > > > > > > > > > > > > > > > -- Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Tel: 613-806-9005 LinkedIn <http://www.linkedin.com/in/davidmacdonald100> twitter.com/davidmacd GitHub <https://github.com/DavidMacDonald> www.Can-Adapt.com <http://www.can-adapt.com/> * Adapting the web to all users* * Including those with disabilities* If you are not the intended recipient, please review our privacy policy <http://www.davidmacd.com/disclaimer.html>
Received on Wednesday, 12 September 2018 22:06:17 UTC