w3c / w3c/edit-context

ITextEditProvider::GetActiveComposition and GetConversionTarget

Open
#1 0 comments 0 reactions 1 assignee View on GitHub

@dandclark is already working on this.

Since Oct 23, 2023.

enhancement
Dominant language
HTML
Stars
48
Forks
13
PR merge metrics
No merged PRs in 30d

Description

ITextEditProvider::GetActiveComposition and GetConversionTarget are APIs that Windows provides to expose IME information for UI Automation. As of Feb 2022, these two APIs don't seem to be really used by popular screen readers like NVDA (no reference in the code base) or JAWS, however, it appears we have a gap in EditContext's API surface where browser vendors don't have a way to map these IME info (i.e. the ranges for active composition and conversion target, now stored in EditContext) to the DOM that authors created for the accessibility purpose. There doesn't seem to be an immediate impact but It would be great if EditContext can provide APIs to create the mapping (for the ranges) so the browser vendors can fully implement the TextEdit control pattern

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.