Re: Regarding the accessible name for embedded section markup

The major user agents all seem to agree on the name – and it is what I logically expected.
There are a lot of elements in the testcase – can you point to the one where you believe the spec says something different?


James Nurthen (he/him)  |  Accessibility Engineer  |  Adobe  |  T 415 832 2734  |  nurthen@adobe.com



From: Bryan Garaventa <bryan.garaventa@levelaccess.com>
Date: Wednesday, December 2, 2020 at 10:28 AM
To: Aaron Leventhal <aleventhal@google.com>, Dominic Mazzoni <dmazzoni@google.com>, Joanmarie Diggs <jdiggs@igalia.com>, James Nurthen <nurthen@adobe.com>
Cc: ARIA <public-aria@w3.org>
Subject: Regarding the accessible name for embedded section markup

Hi,
I was recently asked to evaluate the following markup for its accessible name, which seems to be causing false fails in some cases.

Can you tell me what you think the accessible name for this link should be? The tricky bit is that the spec says it should be something different than what is intuitively expected.

<a id="test" href="/path/">
<figure>
<div>
<img alt="" src="/path/">
</div>
</figure>
<section>
<span>Make a Plan</span>
<h3>Do something.</h3>
</section>
</a>

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<http://www.levelaccess.com/>