You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Related to this: I recently did some testing on roles with presentational children What I found was that Browsers interpreted the requirements differently and SRs dealt with this sub optimally in some cases. It would be helpful for operability and user experience if in the case of User Agents SHOULD or SHOULD NOT, that some clear guidance be provided.
At the ARIA F2F we discussed how to better our relationship with screen reader developers: https://www.w3.org/2023/05/04-aria-minutes#t05
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.
The text was updated successfully, but these errors were encountered: