Open Bug 1160785 Opened 7 years ago Updated 2 months ago
Reader Mode availability could be announced by accessibility
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/600.5.17 (KHTML, like Gecko) Version/8.0.5 Safari/600.5.17 Steps to reproduce: 1. Load webpage with Reader Mode available Actual results: Sighted user noticed reader mode button appeared. VoiceOver user did not notice it, unless they took the effort to with VoiceOver cursor to the location bar. Expected results: Sighted user noticed reader mode button appeared. VoiceOver user noticed availability of Reader Mode without any effort as VoiceOver spoke announcement that Reader Mode is available (this is what Safari does).
Status: UNCONFIRMED → NEW
Ever confirmed: true
I looked at this. The problem is that the order of these 2 events is not deterministic: 1. Reader Mode button state change 2. webView:didFinishNavigation: (where we post AXScreenChanged) I.e. most of the time, 2. happens after 1., so we can pass AXScreenChanged the parameter to say that reader mode is available (when it is, as learned from the Browser's ReaderMode helper's state). But sometimes 2. happens before 1., which makes it unreliable. So currently this is not reliably possible without some more involved tracking of state and of this actual order.
Assignee: dusek → nobody
You need to log in before you can comment on or make changes to this bug.