The lockscreen has a curtain that needs to be lifted to access the unlock/camera buttons. This does not work well with a screen reader, since it requires the user to go through a few extra steps to do something simple like unlocking the screen, which they do often. Screen reader mode requires a double tap when the virtual cursor is on a button to activate. So there is no danger of an accidental activation, and therefore having the curtain permanently expanded in screen reader mode makes sense.

Hey Eitan, Testing out your patches and they mostly look good. In firefox nightlty the lock screen reacts to your plugin which is awesome! My main concern is that I seem to be unable to activate the unlock button inside of nightly (and am not entirely sure how to activate this from a device). Is this the case for you as well? Also there is one little lint error that we should fix. Thanks!

Hi Kevin, on a device, once accessibility is enabled, when the focus is on an element, it is activated by a double-tap. This way, a blind user can touch elements without accidentally activating them. I do not yet know how this would translate to someone trying out the accessibility extension on Nightly on the desktop. I am a screen reader user myself, so my methods certainly would differ in this case.

Updates: - Conditionally remove 'triggered' class when screen reader is disabled. - Also deleted some obsolete 'triggered' class removal lines that followed.

Also removed whitespace :)

Landed in master: https://github.com/mozilla-b2g/gaia/commit/09e4e21f31dbd3b4a85a1919d0e28487f604e322

Are the changes to the apps/system/index.html required? Restructuring the divs for the lockscreen buttons breaks the tap highlighting (see bug 889925).