- From: David MacDonald <david100@sympatico.ca>
- Date: Fri, 13 Apr 2018 12:20:35 -0400
- To: Bryan Garaventa <bryan.garaventa@levelaccess.com>
- Cc: "Schnabel, Stefan" <stefan.schnabel@sap.com>, ARIA Working Group <public-aria@w3.org>
- Message-ID: <CAAdDpDY=AkUWTymo4bZxncFuyN=sjexp_43GQrDH+LYK513DnA@mail.gmail.com>
I think it should be flagged as a computation issue ... I see a lot of problems in the trenches as I work with developers... The trick is redundancy... can the user agents recognize identical strings of information and not pass that through Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Tel: 613.235.4902 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> On Fri, Apr 13, 2018 at 12:06 PM, Bryan Garaventa < bryan.garaventa@levelaccess.com> wrote: > Thanks, > > I understand, and have always thought the invisible loss of accessible > information was strange. > > > > Should this be raised as an issue to be added to the naming computation, > or should this be ignored as something everybody knows and just deals with? > > > > Thanks, > > Bryan > > > > > > Bryan Garaventa > > Accessibility Fellow > > Level Access, Inc. > > Bryan.Garaventa@LevelAccess.com > > 415.624.2709 (o) > > www.LevelAccess.com > > > > *From:* David MacDonald <david100@sympatico.ca> > *Sent:* Friday, April 13, 2018 5:42 AM > *To:* Schnabel, Stefan <stefan.schnabel@sap.com> > *Cc:* ARIA Working Group <public-aria@w3.org>; Bryan Garaventa < > bryan.garaventa@levelaccess.com> > *Subject:* Re: AccName question about multiple description edge case > > > > It is the expected result because the title is a swing attribute that > fills an empty accname or accdesciption > > > > My preference would be that if it is different then it is a concatenation > with the accdescrption... > > > > There a lot if override errors in the wild > > > > On Fri, Apr 13, 2018 at 5:34 AM Schnabel, Stefan <stefan.schnabel@sap.com> > wrote: > > Hi Bryan, > > I understood this as override accepted by the group ever since the very > beginning. > Not clear where exactly this is handled in the accessible description > computation requirements. > > Personally, I feel unhappy with this override. > > Regards > Stefan > > -----Original Message----- > From: Bryan Garaventa [mailto:bryan.garaventa@levelaccess.com] > Sent: Friday, April 13, 2018 9:31 AM > To: ARIA Working Group <public-aria@w3.org> > Subject: AccName question about multiple description edge case > > Hi, > I'd like to verify the expectation for the following testable statement. > > <input type="text" aria-label="LabelText" title="TitleText" id="test" > aria-describedby="descid"><div id="descid">DescriptionText</div> > > Current results: > > accName: "LabelText" > accDesc: "DescriptionText" > > The title is lost. Is this the expected result? > > Thanks, > Bryan > > > Bryan Garaventa > Accessibility Fellow > Level Access, Inc. > Bryan.Garaventa@LevelAccess.com > 415.624.2709 (o) > www.LevelAccess.com > > > -- > > Cheers, > David MacDonald > > > > *Can**Adapt* *Solutions Inc.* > > Tel: 613.235.4902 > > 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 Friday, 13 April 2018 16:21:03 UTC