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

Action-2023) - Proposed solution

From: Léonie Watson <tink@tink.uk>
Date: Mon, 4 Jul 2016 17:47:16 +0100
To: public-apa@w3.org
Message-ID: <115ac03b-a417-02fb-c854-2ab872c84912@tink.uk>
Janina & APA,

I took an action to look into the implications for screen magnification 
software, when the Pointer Lock API is used. Specifically, what happens 
when a pointerlockchange event is fired - engaging/disengaging the mouse 
as a control for the online environment (such as orientation within an 
online game).

I filed an issue against Pointer Lock on behalf of APA [1]. The 
conclusion is that this is a browser implementation issue - so there is 
a limit to how prescriptive the spec itself can be. The spec can advise 
implementors on important behaviours though, and so the following note 
will now be included before the spec moves to PR:

"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 
event is fired, web browsers therefore need to make sure the event is 
communicated to assistive technologies like screen magnifiers."

I won't be at the APA meeting on Wednesday. With my WP chair's hat on, 
it would be hugely appreciated if the APA WG could let me know whether 
this solution is agreeable though - because Pointer Lock is currently in 
transition to CR. Thanks.

[1] https://github.com/w3c/pointerlock/issues/1

@LeonieWatson tink.uk Carpe diem
Received on Monday, 4 July 2016 16:47:48 UTC

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