search

w3c / aria-common

Shared files for the ARIA repositories
Other
8 stars 15 forks source link

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

Open pkra opened 1 year ago

pkra commented 1 year ago

Original at https://github.com/w3c/aria/issues/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 commented 1 year ago

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