W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2021

Re: [csswg-drafts] [css-highlight-api] Figure out how highlights are exposed to the accessibility tree (#6498)

From: Daniel Libby via GitHub <sysbot+gh@w3.org>
Date: Thu, 05 Aug 2021 20:40:44 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-893781016-1628196043-sysbot+gh@w3.org>
UserAgent detected spelling and grammar errors (i.e. ::spelling-error and ::grammar-error) in Chromium do have a mapping to various AT APIs. These are serialized as part of the accessibility tree and as far as I can tell, this is not part of any of the Aria-related standards. For example on UIA on Windows spelling errors are exposed as a text range with an AnnotationType_SpellingError. Not sure how this would fit into the spec, but perhaps is a path forward (following the UIA example, there is an AnnotationType_Highlight).

For completeness, spelling and grammar errors that are computed by the webpage can be annotated with [aria-invalid](https://www.w3.org/TR/wai-aria/#aria-invalid). The corresponding concept for highlights would probably be the mark role (see https://w3c.github.io/aria/). However, these require additional DOM nodes, which is counter to the purpose of the HighlightAPI.


-- 
GitHub Notification of comment by dlibby-
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6498#issuecomment-893781016 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 August 2021 20:40:47 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:27:26 UTC