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

There's been some delay on agenda space opening up to discuss this during CSSWG calls, so I wanted try again to see if we could make some progress here in the issue.

Considering the enum approach considered [here](https://github.com/w3c/csswg-drafts/issues/6498#issuecomment-908755397) and looking more at the current capabilities of UIA's [Annotation Type Identifiers](https://docs.microsoft.com/en-us/windows/win32/winauto/uiauto-annotation-type-identifiers) and Mac's [Attributed String Keys](https://developer.apple.com/documentation/foundation/nsattributedstring/key#:~:text=of%20the%20text.-,Accessibility%20Keys,-static%20let%20accessibilityAlignment), I'd like to propose starting with an enum with just these:

```js
enum HighlightType {
 // Exposed with AnnotationType_Highlight for UIA, accessibilityCustomText for Mac
 "highlight",
 // Exposed with AnnotationType_SpellingError for UIA, NSAccessibilityMisspelledTextAttribute for Mac
 "spellingerror",
 // Exposed with AnnotationType_GrammarError for UIA, NSAccessibilityMisspelledTextAttribute for Mac
 "grammarerror"
 // More can be added as use cases emerge and accessibility platforms add more text semantic types
};

[Exposed=Window]
interface Highlight {
  constructor(AbstractRange... initialRanges);
  setlike<AbstractRange>;
  attribute long priority;
  attribute HighlightType type; // Exposed to ATs. Default is "highlight".
};
```

This approach lets custom spellcheck achieve the same experience with accessibility tools as native spellcheck for UIA and Mac today, and leaves room to add more entries to the enum as use cases an support emerge. A custom string could be added in an L2 if the need for that level of flexibility emerges.

@frivoal @sanketj @dlibby- @lilles, any thoughts on this approach?

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 29 September 2021 23:50:14 UTC