There’s a mistake on 8:10: when generic font-family is quoted it makes browser look for a font named 'sans-serif', not for a generic family. So it’s important to keep generic families as is, unquoted.
Does this app only work in web pages, text pages, and windows itself? I want to be able to read my screen when im inside apps, like games or text from an image/videos
What about repeating the error message if the user keeps clicking the button? I've tested on Voiceover and NVDA, and neither repeat the message for additional clicks. I've found a quick and dirty solution that works (toggling a space character), but this doesn't work on NVDA and IE combo.
Where does the focus go after the screen reader finishes reading content of role=alert? Is there a way to send the screen reader focus to a specific region or element after it finishes reading alert? Thanks
not necessarily. you could add an alert section to the page shell itself, load the views into the shell, and have them pipe out their alerts. that's what iron-a11y-announcer does I think elements.polymer-project.org/elements/iron-a11y-announcer
Rob Dodson looks like the DOM element is created in IronA11yAnnouncer.requestAvailability. Does that occur early enough for the Chrome voice over to catch it?
Rob Dodson looks like the DOM element is created in IronA11yAnnouncer.requestAvailability. Does that occur early enough for the Chrome voice over to catch it?
There’s a mistake on 8:10: when generic font-family is quoted it makes browser look for a font named 'sans-serif', not for a generic family. So it’s important to keep generic families as is, unquoted.
Yes. sans-serif isn't a font name exactly.
Does this app only work in web pages, text pages, and windows itself? I want to be able to read my screen when im inside apps, like games or text from an image/videos
What about repeating the error message if the user keeps clicking the button? I've tested on Voiceover and NVDA, and neither repeat the message for additional clicks. I've found a quick and dirty solution that works (toggling a space character), but this doesn't work on NVDA and IE combo.
Where does the focus go after the screen reader finishes reading content of role=alert? Is there a way to send the screen reader focus to a specific region or element after it finishes reading alert? Thanks
doesn't this mean that client-side routing precludes the inclusion of an alert role within the views dynamically rendered based on client-side routes?
not necessarily. you could add an alert section to the page shell itself, load the views into the shell, and have them pipe out their alerts. that's what iron-a11y-announcer does I think elements.polymer-project.org/elements/iron-a11y-announcer
Rob Dodson looks like the DOM element is created in IronA11yAnnouncer.requestAvailability. Does that occur early enough for the Chrome voice over to catch it?
Rob Dodson looks like the DOM element is created in IronA11yAnnouncer.requestAvailability. Does that occur early enough for the Chrome voice over to catch it?
it really depends on how you're using it, when you're loading in the view and when you're displaying the alert. my advice is test your setup to see
Thanks! Great tutorial!
nice use of clone ty!
Does paper-toast Polymer element have that implemented?
I believe so as it uses iron-a11y-announcer elements.polymer-project.org/elements/iron-a11y-announcer
Is JS Bin endorsed by Google?
hah um I don't know. It's a cool site that I like to use but I don't speak for all of Google
QbsidianH20
What about Windows - Edge and IE 11?
For IE11 I believe the most common screen reader is JAWS and I believe this should work there as well.
were you making video in the kindergarden?
yes