W3C home > Mailing lists > Public > public-apa@w3.org > July 2016

RE: Action-2023) - Proposed solution

From: White, Jason J <jjwhite@ets.org>
Date: Tue, 5 Jul 2016 12:52:42 +0000
To: "tink@tink.uk" <tink@tink.uk>, "public-apa@w3.org" <public-apa@w3.org>
Message-ID: <BY2PR0701MB19907C3DBE8B7CDCFA284F1BAB390@BY2PR0701MB1990.namprd07.prod.outlook.com>

> -----Original Message-----
> From: LĂ©onie Watson [mailto:tink@tink.uk]
> "Note: Magnification software increases the size of content on the screen. It
> uses the mouse to move the magnified point of focus around.
> When a pointer
> lock is initiated, the magnification software needs to switch to using the
> keyboard to move the magnified point of focus around instead. When a
> pointerlockchange event is fired, web browsers therefore need to make sure the
> event is communicated to assistive technologies like screen magnifiers."
[Jason] Are there established mechanisms (at least on desktop operating systems) for giving the notification? I don't recall there being such an event in accessibility APIs, for instance, nor whether screen magnifiers monitor those APIs.
It may be necessary for operating system and screen magnifier developers to implement their side of this requirement, if it isn't in place now. Is this a requirement that user agents can meet today?


This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.

Received on Tuesday, 5 July 2016 12:53:18 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:01 UTC