Clarify which legend/figcaption/caption element to use #146
Conversation
| @@ -5583,9 +5583,9 @@ <h3><code>fieldset</code> and <code>legend</code> Elements</h3> | |||
| <h4><code>fieldset</code> Element Accessible Name Computation</h4> | |||
| <ol> | |||
| <li>If the <code>fieldset</code> element has an <a href="https://www.w3.org/TR/wai-aria-1.1/#aria-label"><code>aria-label</code></a> or an <a href="https://www.w3.org/TR/wai-aria-1.1/#aria-labelledby"><code>aria-labelledby</code></a> attribute the <a class="termref">accessible name</a> is to be calculated using the algorithm defined in <a href="" class="accname">Accessible Name and Description: Computation and API Mappings 1.1</a>. </li> | |||
There was a problem hiding this comment.
I actually do not understand why there is any remaining need for conditional language here. Might this be a hold-over from back in the days when the accessible name computation spec was an "ARIA-only" thing buried inside the UAIG?
In other words, why are there naming algorithms being defined outside the accname spec? The accname spec defines when to use content or title. So, why can't the accessible name calculation be used all the time? If every element has its own algorithm, testing name computation will continue to be unnecessarily complex, or perhaps more accurately, impossibly complex.
@accdc, @joanmarie, @jnurthen, does this make sense to you?
There was a problem hiding this comment.
I can envision there being a generic algorithm that applies to all HTML/SVG elements, which has an element-specific hook that fieldset, table etc can define to let legend/caption go in between ARIA attributes and the title attribute. But this is basically an editorial detail.
…idn't yield anything
Fixes #145.