RE: AccName question about multiple description edge case

“The trick is redundancy... can the user agents recognize identical strings of information and not pass that through”

If this is dealt with in the spec, I’m sure this can be done, since it is already happening in some browsers when the description and name properties match, so description is suppressed so that only name is set. Technically this is possible, it just needs to be dealt with in the algorithm.

Bryan Garaventa
Accessibility Fellow
Level Access, Inc.
[email protected]
415.624.2709 (o)
www.LevelAccess.com

From: David MacDonald <[email protected]>
Sent: Friday, April 13, 2018 9:21 AM
To: Bryan Garaventa <[email protected]>
Cc: Schnabel, Stefan <[email protected]>; ARIA Working Group <[email protected]>
Subject: Re: AccName question about multiple description edge case

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



CanAdapt Solutions Inc.

Tel:  613.235.4902

LinkedIn
<https://t6uflukgva.proxynodejs.usequeue.com/in/davidmacdonald100>

twitter.com/davidmacd<https://jq7yqtejv6.proxynodejs.usequeue.com/davidmacd>

GitHub<https://93to8ehqgm.proxynodejs.usequeue.com/DavidMacDonald>

www.Can-Adapt.com<https://lnt1xckgwg.proxynodejs.usequeue.com/>



  Adapting the web to all users
            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<https://9yftkkgar6.proxynodejs.usequeue.com/disclaimer.html>

On Fri, Apr 13, 2018 at 12:06 PM, Bryan Garaventa <[email protected]<mailto:[email protected]>> 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.
[email protected]<mailto:[email protected]>
415.624.2709 (o)
www.LevelAccess.com<https://nhfjemsxwq.proxynodejs.usequeue.com/>

From: David MacDonald <[email protected]<mailto:[email protected]>>
Sent: Friday, April 13, 2018 5:42 AM
To: Schnabel, Stefan <[email protected]<mailto:[email protected]>>
Cc: ARIA Working Group <[email protected]<mailto:[email protected]>>; Bryan Garaventa <[email protected]<mailto:[email protected]>>
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 <[email protected]<mailto:[email protected]>> 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:[email protected]<mailto:[email protected]>]
Sent: Friday, April 13, 2018 9:31 AM
To: ARIA Working Group <[email protected]<mailto:[email protected]>>
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.
[email protected]<mailto:[email protected]>
415.624.2709 (o)
www.LevelAccess.com<https://nhfjemsxwq.proxynodejs.usequeue.com/>

--

Cheers,
David MacDonald



CanAdapt Solutions Inc.

Tel:  613.235.4902

LinkedIn
<https://t6uflukgva.proxynodejs.usequeue.com/in/davidmacdonald100>

twitter.com/davidmacd<https://jq7yqtejv6.proxynodejs.usequeue.com/davidmacd>

GitHub<https://93to8ehqgm.proxynodejs.usequeue.com/DavidMacDonald>

www.Can-Adapt.com<https://lnt1xckgwg.proxynodejs.usequeue.com/>



  Adapting the web to all users
            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<https://9yftkkgar6.proxynodejs.usequeue.com/disclaimer.html>