E-mail List Archives
Re: Unexpected Voiceover Tab Order and Focusing on Hybrid App
From: Jonathan Avila
Date: Mar 12, 2015 7:25AM
- Next message: Gunderson, Jon R: "Re: JAWS 15 Vs JAWS 16 (Carousel widget example)"
- Previous message: Patrick H. Lauke: "Re: Unexpected Voiceover Tab Order and Focussing on Hybrid App"
- Next message in Thread: Graham Armfield: "Re: Unexpected Voiceover Tab Order and Focusing on Hybrid App"
- Previous message in Thread: Patrick H. Lauke: "Re: Unexpected Voiceover Tab Order and Focussing on Hybrid App"
- View all messages in this Thread
> If it's a hybrid app, wouldn't this need use JavaScript's focus() method? (serious question, as I've not played with building hybrid apps myself).
Yes, if the issues are in the webview portion of the app then all standard HTML reading order and focus control mechanisms would apply. That is, reading order would be controlled by the order of the document object model and focus could be set with .focus() etc. With hybrid apps it's not always clear what content is native or web. One trick I use is to turn the rotor -- if I see web options in the rotor I know I'm in a web view -- otherwise I am in a native portion of the app. Both would contain heading rotor options if that is in your rotor -- so you can't rely on the headings option to make this determination.
Jonathan
--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
<EMAIL REMOVED>
Phone 703.637.8957
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter
- Next message: Gunderson, Jon R: "Re: JAWS 15 Vs JAWS 16 (Carousel widget example)"
- Previous message: Patrick H. Lauke: "Re: Unexpected Voiceover Tab Order and Focussing on Hybrid App"
- Next message in Thread: Graham Armfield: "Re: Unexpected Voiceover Tab Order and Focusing on Hybrid App"
- Previous message in Thread: Patrick H. Lauke: "Re: Unexpected Voiceover Tab Order and Focussing on Hybrid App"
- View all messages in this Thread