RE: Decision for AccName and figcaption

Got it, thanks, so basically full removal from AccName mappings.


Bryan Garaventa
Principal Accessibility Architect
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com<mailto:Bryan.Garaventa@LevelAccess.com>
415.624.2709 (o)
www.LevelAccess.com<http://www.levelaccess.com/>

From: Scott O'Hara <scott.ohara@microsoft.com>
Sent: Monday, November 1, 2021 10:50 AM
To: Bryan Garaventa <bryan.garaventa@levelaccess.com>; Accessible Rich Internet Applications Working Group <public-aria@w3.org>
Subject: RE: Decision for AccName and figcaption

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

We had initially discussed description, but conversation turned to revising the mapping to be more inline with an aria-details association.  This being particularly due to the fact that figcaptions can contain highly structured content, as we discussed as an example of having a table within a figcaption for a graph that serves as the primary content of the figure.

From: Bryan Garaventa<mailto:bryan.garaventa@levelaccess.com>
Sent: Monday, November 1, 2021 1:46 PM
To: Scott O'Hara<mailto:scott.ohara@microsoft.com>; Accessible Rich Internet Applications Working Group<mailto:public-aria@w3.org>
Subject: [EXTERNAL] RE: Decision for AccName and figcaption

Thanks,
From a mapping perspective, instead of name, was there agreement to make this a description instead? I recall lots of discussion but not a resolution.
All the best,
Bryan


Bryan Garaventa
Principal Accessibility Architect
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com<mailto:Bryan.Garaventa@LevelAccess.com>
415.624.2709 (o)
www.LevelAccess.com<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.levelaccess.com%2F&data=04%7C01%7Cscott.ohara%40microsoft.com%7C3b2bc3735ff64606cd0a08d99d5f7eaa%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637713855763853195%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=OvwwIfuJrH5MOwmCC%2BcbYO4pz8bbPEaaf3y1fH4rDRM%3D&reserved=0>

From: Scott O'Hara <scott.ohara@microsoft.com<mailto:scott.ohara@microsoft.com>>
Sent: Monday, November 1, 2021 6:47 AM
To: Bryan Garaventa <bryan.garaventa@levelaccess.com<mailto:bryan.garaventa@levelaccess.com>>; Accessible Rich Internet Applications Working Group <public-aria@w3.org<mailto:public-aria@w3.org>>
Subject: RE: Decision for AccName and figcaption

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi Bryan,

Haven't been able to make the necessary changes in HTML AAM yet, but when the WG discussed we were going to move away from figcaption participating in accName for figure.

From: Bryan Garaventa<mailto:bryan.garaventa@levelaccess.com>
Sent: Friday, October 29, 2021 2:26 PM
To: Accessible Rich Internet Applications Working Group<mailto:public-aria@w3.org>
Subject: [EXTERNAL] Decision for AccName and figcaption

Hi,
Has consensus been reached regarding the AccName determination for figcaption?

If yes, can someone please summarize the expected behavior from an AccName perspective as to which properties should be set when applied within a figure?

Thanks,
Bryan


Bryan Garaventa
Principal Accessibility Architect
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com<mailto:Bryan.Garaventa@LevelAccess.com>
415.624.2709 (o)
www.LevelAccess.com<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.levelaccess.com%2F&data=04%7C01%7Cscott.ohara%40microsoft.com%7C3b2bc3735ff64606cd0a08d99d5f7eaa%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637713855763863153%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CsD3ZXB96VCehYmRfsAhygweTIcyQpUC6YBCu08xwqE%3D&reserved=0>