![]() Is it that screen reading software a bit like CSS of the 1990s-just not properly developed/supported yet? I wouldn’t have thought so. So, my question: are screen readers really so hard to use and/or test, or am I missing something? I’d like to do the right thing and understand accessibility issues from this point of view, but there seems little incentive to bother. But OMG $1000 bucks! I don’t want to pay that just to test out accessibility. (Perhaps it was the keyboard at fault, as I couldn’t find equivalent keys to the Windows ones that are meant to turn it off and control it.) In the end, in panic, I just uninstalled it, because I couldn’t do anything in Windows without it following me around. ![]() Maybe it’s because I’m using a Mac keyboard, but I couldn’t get it do do anything! The damned program just kept screaming at me and repeating everything I was doing (like an annoying kid) as I tried to get it to read out a web page. OK, so I try NVDA, a free download for Windows. Man, I’d hate to be relying on that thing. ![]() A lot of them simply don’t work, and they are far from comprehensive. It has a nice voice sound, but I couldn’t figure out how to navigate a web page with it even with my eyes open, reading the instructions. I work mainly on a Mac (I have Windows installed on the Mac, and thus use it with a Mac keyboard, which may be a cause of problems in regard to screen reading software). I’d like to get a better handle on accessibility, and one facet of doing so (I assume) is to try out some screen readers. ![]()
0 Comments
Leave a Reply. |