Skip to content
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

Definition of children presentational eroneously states that making presentational is equivalent to hiding all descendants. #491

Closed
mcking65 opened this issue Dec 1, 2016 · 4 comments
Milestone

Comments

@mcking65
Copy link
Contributor

mcking65 commented Dec 1, 2016

Section 5.2.8 Presentational Children
defines children presentational true as:

The DOM descendants are presentational. User agents should not expose descendants of this element through the platform accessibility API.
If user agents do not hide the descendant nodes, some information may be read twice.

So, it is saying that making something presentational hides all descendant nodes from the accessibility API.

While role none says:

Many individuals erroneously consider role="presentation" to be synonymous with aria-hidden="true", and we believe role="none" conveys the actual meaning more unambiguously.

And aria-hidden is defined as:

Indicates whether the element is exposed to an accessibility API.

These are the same words used to define children presentational true.

I think section 5.2.8 needs to be reworded to state something more like:

The DOM descendants are presentational. User agents SHOULD expose only the text content of descendants of this element through the platform accessibility API.

@mcking65 mcking65 added ARIA editorial a change to an example, note, spelling, grammar, or is related to publishing or the repo labels Dec 2, 2016
@joanmarie
Copy link
Contributor

This change appears to be modifying a normative statement. There's also a chance it may impact implementations and presentation by assistive technologies. In particular, the opening report quotes spec text which states "If user agents do not hide the descendant nodes, some information may be read twice." If we make the change proposed, in which we explicitly tell user agents to include the text content, might we be in danger of having screen readers present some information twice? I don't think we can answer that question for certain without some further investigation and testing.

Because of the above (normative statement + may actually impact user experience), I do not think this is an editorial change. Thus I'm going to remove that label. Because normative changes would require exiting and re-entering CR, something the Working Group determined it did not want to do, changes in this area will have to wait until 1.2.

@joanmarie joanmarie added ARIA 1.2 and removed ARIA 1.1 editorial a change to an example, note, spelling, grammar, or is related to publishing or the repo labels Oct 26, 2017
@jnurthen jnurthen added this to the ARIA 1.2 milestone Dec 4, 2018
@jnurthen jnurthen removed ARIA labels Dec 4, 2018
@jnurthen
Copy link
Member

jnurthen commented Dec 4, 2018

@mcking65 If you think there is something that needs changing here can you please submit a PR. I'm not convinced there is any change that needs to be made.

@mcking65
Copy link
Contributor Author

mcking65 commented Dec 5, 2018

joanmarie wrote:

If we make the change proposed, in which we explicitly tell user agents to include the text content, might we be in danger of having screen readers present some information twice? I don't think we can answer that question for certain without some further investigation and testing.

When children presentational is true, isn't the text content present? It sure appears to be.

@jnurthen jnurthen modified the milestones: ARIA 1.2, ARIA 1.3 Nov 19, 2019
@JAWS-test
Copy link
Contributor

I think the ticket can be closed because in ARIA 1.2 it says correctly:

However, the text content of any excluded descendants is included.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants