- From: Chaals McCathie Nevile <chaals@yandex-team.ru>
- Date: Mon, 19 Oct 2015 11:21:40 +0200
- To: public-html-a11y@w3.org, "HTML Accessibility Task Force Issue Tracker" <sysbot+tracker@w3.org>
Hi, to close this action item: The editing task force are trying to work out how to deal with IMEs. The basic issue is that then "normal" text is entered, there are some key events that lead to a letter being generated: a, or F, or Я. But things get more complicated after that, whether it is because you have ñ or ∫ or 日本語. For plain text input, they can catch the keys themselves. This at least intersects with the problems we already have around accesskey and using javascript as an alternative. But with IMEs for handling complex scripts that don't fit on a keyboard, things get trickier. We are aware of issues like going into the text 日<b>本</b>語 to re-edit it, and having it turned into unpredictable but likely wrong things. What we are wondering is: Does the same thing happens for accessibility reasons? E.g. with people using assistive technologies to edit text from voice input? How well do assistive technologies interact with IMEs - the widest-spread being for CJK, although there are other languages like Vietnamese which use a keyboard setup that amounts to an IME. Note that the mechanics of how to handle "complex" text input is still open to debate, so it is timely to provide any information we find. Cheers Chaals -- Charles McCathie Nevile - web standards - CTO Office, Yandex chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Monday, 19 October 2015 09:22:15 UTC