[michiel] alt=search query of “brai” returns 7 results including: UEBOnline (the braille thing), How food affects your brain, How blind people write braille, the backwards brain bicycle, and a search result for “what does brain taste like”…
[robdodson] quick question. Does JAWS or NVDA support aria-controls? Using this example http://accessibility.athena-ict.com/aria/examples/tabpanel2.shtml VoiceOver only reads the content of the tab when you change it. It doesn't read the content of the tabpanel though it seems like it should. I'm wondering if other screen readers do, as that seems like the entire point of aria-controls
wouldn't it be highly annoying if every tab you were at started reading entire panels?
Wouldn't it just make you want to hurl?
it's like the bug I've got with our keyboardable calendars-- each time you switch to another month, the date numbers start getting read out (and in semi-random order). not cool.
Scenario: I have a button. With a checkmark as text and aria-label="Save". Wouldn't it always be better to have an offscreen <span>Save</span>, so the accessible name is more clear to AT like Dragon Naturallyspeaking?
Unless the aria-label is also considered by Dragon when looking for accessible name.
Never used dragon for Mac so can't help there. If it is the same x p i then things should be fine for aria. I took a look through the code and aria-label works (but strangely aria-labelledby is not everywhere)
An X p i is just a zip so easy to look at the code.
[sophieschoice_slack] Stupid question perhaps; but when you test with VoiceOver or with NVDA, what are the things you pay attention to? How to know something should be spoken or not?
Quick question: How are screen readers on smartphones used most commonly? Touch gestures, Bluetooth keyboards, something else?
I’m asking because I’ve noticed that in VoiceOver on iPhone, the left/right-swipe focus order is not the same as the keyboard focus order on desktop, since it also includes plain text parts.