8000 Develop concept/styling for direct advice for how AT/screen readers should interpret specs · Issue #96 · w3c/aria-common · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Develop concept/styling for direct advice for how AT/screen readers should interpret specs #96

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.

Sign up for GitHub

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

Jump to bottom
Open
pkra opened this issue Jun 13, 2023 · 1 comment
Open

Develop concept/styling for direct advice for how AT/screen readers should interpret specs #96

pkra opened this issue Jun 13, 2023 · 1 comment

Comments

@pkra
Copy link
Member
pkra commented Jun 13, 2023

Original at w3c/aria#1942

One thing that came out of the discussion was that some ATs would appreciate guidance on how to implement support for new ARIA features. We will explore a process for drafting AT guidance directly in the spec under the feature and role. As part of the consensus process we can get feedback from ATs through our many personal relationships.

Additionally it seemed like there was some consensus to use "should" and "may" with respect to ATs, and acknowledged that often we mean screen readers specifically.

This issue is for the editor team to explore the styling of these sections and to provide draft guidance for a recent feature, for example, the annotation roles.

As discussed in this week's call https://lists.w3.org/Archives/Public/public-aria-editors/2023Jun/0002.html, this issue to get a design working.
@pkra
Copy link
Member Author
pkra commented Jun 13, 2023

From the minutes:

jamesn: exactly
... we need to prototype something
mattking: I'd suggest not just 1 style but all 3 styles immediately
... and not just visual
jamesn: I'd like a prototype that can be extended that way
mattking: right. just don't paint yourself in a corner
jamesn: right. e.g. background color could get difficult
... e.g., https://speced.github.io/bikeshed/#tracking-vectors //
https://infra.spec.whatwg.org/#tracking-vector
pkra: I'd like to try to pick up on the visual cues for notes, examples etc

@pkra pkra mentioned this issue Jun 13, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pkra
0