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

Updating example 2 in prog determined #3049

Closed
wants to merge 1 commit into from

Conversation

alastc
Copy link
Contributor

@alastc alastc commented Feb 21, 2023

Closes #3001

@@ -6,8 +6,7 @@
<a>user agents</a>, including <a>assistive technologies</a>, can extract and present this information to users in different modalities
</p>

<aside class="example"><p>Determined in a markup language from elements and attributes that are accessed directly
by commonly available assistive technology.
<aside class="example"><p>Determined in a markup language from elements and attributes that are exposed in the accessibility tree.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<aside class="example"><p>Determined in a markup language from elements and attributes that are exposed in the accessibility tree.
<aside class="example"><p>Determined in a markup language from elements and attributes that are accessed via the accessibility tree by commonly available assistive technology.

As I mentioned in a comment today, I'd prefer to keep "commonly available assistive technology" in both examples, consistent with 5.2.4 and "accessibility supported."

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'd keep the aspect of whether something is in the accessibility tree, and whether or not AT then accesses/uses it for anything, separate

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer 'exposed', as it is rather about clean html instead of depending on abilities of existing technologies.

@alastc
Copy link
Contributor Author

alastc commented Sep 6, 2024

Note that we did discuss this previously and had resolved to change the understanding document instead.

We can revisit, particularly with a new version, but we should look at updating the understanding doc.

An updated version shouldn't include term "accessibility tree".

@alastc alastc closed this Sep 6, 2024
@kfranqueiro kfranqueiro deleted the Issue3001-programmatically-determined branch October 28, 2024 17:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Programmatically Determined example describes outdated direct parsing of markup
5 participants