Mar. 31st, 2008
(no subject)
Mar. 31st, 2008 03:10 amSo tonight I decided to learn how to use the built-in screen reader on OS X, mostly out of curiosity but also because, hey, that would mean I could finally do some sort of proper accessibility testing on my websites. Unfortunately, it's not quite up to production quality - I seem to have already found two annoying bugs in my first 30 minutes of use.
On my copy of 10.4, at least, it seems to go into an infinite loop when reading certain header elements in Safari in "read all" mode. Which seems like an obvious glaring bug to have gotten through testing. And it fails to actually tell you the content of a UI control if it's ghosted (it just says "Dimmed button", for example, if your web browser's Forward button is ghosted), which seems kind of uninformative given that the whole point of ghosting controls is so that the user can still see what the function would be if it were enabled.
On the plus side, I am glad to have finally gotten some hands-on experience testing websites against a screen reader - now I have some ideas on how to improve the Brain Comics accessibility by reordering some of the page contents.
On my copy of 10.4, at least, it seems to go into an infinite loop when reading certain header elements in Safari in "read all" mode. Which seems like an obvious glaring bug to have gotten through testing. And it fails to actually tell you the content of a UI control if it's ghosted (it just says "Dimmed button", for example, if your web browser's Forward button is ghosted), which seems kind of uninformative given that the whole point of ghosting controls is so that the user can still see what the function would be if it were enabled.
On the plus side, I am glad to have finally gotten some hands-on experience testing websites against a screen reader - now I have some ideas on how to improve the Brain Comics accessibility by reordering some of the page contents.
(no subject)
Mar. 31st, 2008 03:10 amSo tonight I decided to learn how to use the built-in screen reader on OS X, mostly out of curiosity but also because, hey, that would mean I could finally do some sort of proper accessibility testing on my websites. Unfortunately, it's not quite up to production quality - I seem to have already found two annoying bugs in my first 30 minutes of use.
On my copy of 10.4, at least, it seems to go into an infinite loop when reading certain header elements in Safari in "read all" mode. Which seems like an obvious glaring bug to have gotten through testing. And it fails to actually tell you the content of a UI control if it's ghosted (it just says "Dimmed button", for example, if your web browser's Forward button is ghosted), which seems kind of uninformative given that the whole point of ghosting controls is so that the user can still see what the function would be if it were enabled.
On the plus side, I am glad to have finally gotten some hands-on experience testing websites against a screen reader - now I have some ideas on how to improve the Brain Comics accessibility by reordering some of the page contents.
On my copy of 10.4, at least, it seems to go into an infinite loop when reading certain header elements in Safari in "read all" mode. Which seems like an obvious glaring bug to have gotten through testing. And it fails to actually tell you the content of a UI control if it's ghosted (it just says "Dimmed button", for example, if your web browser's Forward button is ghosted), which seems kind of uninformative given that the whole point of ghosting controls is so that the user can still see what the function would be if it were enabled.
On the plus side, I am glad to have finally gotten some hands-on experience testing websites against a screen reader - now I have some ideas on how to improve the Brain Comics accessibility by reordering some of the page contents.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}