What fresh hell is THIS now? - Patrick Lauke
figcaption
for an image should be used in addition to alt
text rather than an alternative to alt
text?
input:-webkit-autofill
background color?
[ken.petri] When using mobile screen readers, a normally interactive element that is visually obscured by another element cannot be interacted with.
For example, say you have a footer-like bar that sticks to the bottom of the viewport, position:fixed. If you swipe to a button that is "underneath" your sticky footer thing you will hear the screen reader announce that the button is a button and hear its accessible name. But if you "double-tap" to click the button, the tap/click event is not passed to the button. It is "absorbed" by your sticky footer thing. Apparently, the mobile screen readers' swipe focus rectangle is literally where the actual click event occurs -- not on the DOM node but on the physical screen, wherever the rectangle gets painted.
Does anyone know a way to address this issue?
We want the sticky footer thing but we need a way to make sure that stuff that is focused by the screen reader always gets positioned "above" that sticky footer. A mobile screen reader will perform a scroll when it detects that a swiped to element is outside of the standard viewport. However, there is no calculation that takes into consideration the vertical space consumed by the sticky footer thing.
We could force the scroll by listening for events, but focus/blur listeners won't do the job, since Android Talkback is not passing an event when an interactive element is swiped to/off of.
Anyone encounter such an issue before? Any clever (or dead obvious) solutions?