jadelennox (
jadelennox) wrote in
dw_accessibility2009-10-13 10:57 pm
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Entry tags:
screen reader testers needed!
I've made a modified version of the account creation page in order to address bug 1016. I've tested it with JAWS 10 and nVDA, but I know my experience testing as a sighted user is imperfect and doesn't really produce the experience of knowledgeable full-time screen reader users.
I'd love to get several testers trying out this page, with only a multitude of testers with a variety of tools. Because the new page uses WAI-ARIA accessibility encoding, it will have extra features that are only available to people using the newest tools(for example JAWS 10). However, it should still be reporting accurate errors for people using screen readers that don't have WAI-ARIA functionality.
If you are a screen reader user, I would love it if you test that page. Try a bunch of things. Try to create accounts both correctly and incorrectly. Try to create accounts with bad passwords or usernames you've already used. Let me what works and what doesn't!
(You should know something I discovered to much frustration during testing: if you test to make sure that it insists you be over 13 based on your birthday, and then you try again with a much older birthday, the system has a timeout to make sure that you aren't just gaming the system and changing the year of your birth.)
Let me know how the tests go, and tell me what screen reader/operating system/browser combination you are using.
Thank you so much!
I'd love to get several testers trying out this page, with only a multitude of testers with a variety of tools. Because the new page uses WAI-ARIA accessibility encoding, it will have extra features that are only available to people using the newest tools(for example JAWS 10). However, it should still be reporting accurate errors for people using screen readers that don't have WAI-ARIA functionality.
If you are a screen reader user, I would love it if you test that page. Try a bunch of things. Try to create accounts both correctly and incorrectly. Try to create accounts with bad passwords or usernames you've already used. Let me what works and what doesn't!
(You should know something I discovered to much frustration during testing: if you test to make sure that it insists you be over 13 based on your birthday, and then you try again with a much older birthday, the system has a timeout to make sure that you aren't just gaming the system and changing the year of your birth.)
Let me know how the tests go, and tell me what screen reader/operating system/browser combination you are using.
Thank you so much!
no subject
And testing completed. That page is beautiful. Just absolutely wonderful. We created an account, and then tested on bad birthdays, bad passwords etc and it seems that the form works and works properly. Beautiful beautiful.
no subject
no subject
no subject
no subject
Thank you Yvi!
no subject
no subject
I might also suggest moving the error messages up above the table with the form, rather than leaving them below, because it took me a second of 'eh...?' to find them.
Jaws 10.latest/IE 7.
no subject
Also, I wanted the error messages to be above the table, but what I found was that the only way I could get Jaws to automatically announce them to me (using Jaws 10, Firefox 3.5, Jaws default configuration) was if I put them exactly where they were. Is that me misunderstanding Jaws? I wanted to make sure that it was very clear to people what the errors were because the bug as framed by
Thank you so much for making the time.
no subject
For a form that works, oh, hmm. Well, I mean, it's simpler, but the log in screen for gmail works perfectly. As do polls on both LJ and DW. Re cursors: it's actually the PC cursor that's hopping, not the Jaws cursor (though I suppose the Jaws cursor might be moving and I wouldn't know it). PC cursor = my focus point, visually invisible. Jaws cursor = mouse pointer.
Also, poking at it again, I find that when I enter the form and tab field to field filling it in, it works very nicely all the way through except at the very last tab from checkbox to the button at the bottom, the tab to the button doesn't work. Jaws doesn't announce the button when you tab, though if I arrow over it it is clearly there and properly identified. I have no idea about that one, either.