New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify which legend/figcaption/caption element to use #146

Merged
merged 2 commits into from Sep 7, 2018

Conversation

Projects
None yet
3 participants
@zcorpan
Member

zcorpan commented Aug 30, 2018

Fixes #145.

@@ -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>

This comment has been minimized.

@mcking65

mcking65 Aug 31, 2018

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?

@mcking65

mcking65 Aug 31, 2018

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?

This comment has been minimized.

@zcorpan

zcorpan Sep 1, 2018

Member

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.

@zcorpan

zcorpan Sep 1, 2018

Member

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.

@stevefaulkner stevefaulkner merged commit f311fe0 into w3c:gh-pages Sep 7, 2018

1 check passed

ipr PR deemed acceptable as non-substantive by @ylafon.
Details

@zcorpan zcorpan deleted the zcorpan:zcorpan/clarify-legend-figcaption-caption branch Sep 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment