[w3c/pointerlock] pointerlockchange and the accessibility tree (#1)

Filed on behalf of the APA WG.

When a pointerlockchange event is fired, the browser needs to reflect this in the accessibility tree. The accessibility tree is typically updated based on changes to the DOM, but it is not clear how a pointerlockchange event would be handled?

Screen magnification software zooms in on a small chunk of the screen until the content is dramatically increased in size. One mechanism for directing the area of focus is to use the mouse (to pan left/right etc.). In many respects it is a similar interaction to that proposed by Pointer Lock.

When a pointerlockchange event is fired, the screen magnifier will need to know whether to stop tracking the mouse movement (or resume tracking it). Otherwise it will continue to track mouse movement to direct the magnified viewport, preventing the pointer lock from working.

If the browser triggers an accessibility change event in response to the pointerlockchange event, this will signify to the magnification software (and other assistive technologies) that something significant has happened.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/pointerlock/issues/1