Layout is very confusing.
Sometimes it says “Label 0 button.”
No edit field to enter information for avatar skin tone and hair color options.
On some forms, there will be a checkbox. For instance, the screen reader might say: Skin tone light skin "checkbox not checked." If that is what I choose as skin tone, I would press spacebar to check the box. Hair color Red/brown "checkbox not checked." That is my hair color, so I would hit spacebar to check it.
Didn’t understand why there was a next button and a continue button
Notes from call with Becky 8-12-2020
She uses Jaws screen reader for Windows version 2020: https://www.freedomscientific.com/products/software/jaws/
screen readers need to know “next” is disabled in nav bar and that the whole nav bar is a supplemental tool, not how navigation through GI happens (instead that Continue button is way to move on)
Survey Monkey and Amazon are good website examples of speech friendly websites
https://www.amazon.com/gp/help/customer/display.html?nodeId=201829330https://www.afb.org/aw/18/5/15212 (see section on screen reader friendly option for amazon.com)
Legal Server is a good too
avatars need hidden checkbox for hair/skin tone and maybe avatar selectors that explain what user is picking
“graphics labeler” for images
She’s happy to do another test for us
mike’s thoughts and future Qs:
button navigation should auto focus main content so readers automatically read the next question text. also make a logical up/down keyboard nav experience - a shift tab up gets you to the nav bar, and a normal keyboard tab gets you to the first input field/button
navbar navigation should not focus the question text, but maybe starts reading it the content of that text in an aria attribute. For example, i’m on Enter Your Address page, and i keyboard nav back to ‘name’ - it should start reading - please enter your name …
Becky’s initial testing feedback:
Layout is very confusing. Sometimes it says “Label 0 button.” No edit field to enter information for avatar skin tone and hair color options. On some forms, there will be a checkbox. For instance, the screen reader might say: Skin tone light skin "checkbox not checked." If that is what I choose as skin tone, I would press spacebar to check the box. Hair color Red/brown "checkbox not checked." That is my hair color, so I would hit spacebar to check it. Didn’t understand why there was a next button and a continue button
Notes from call with Becky 8-12-2020 She uses Jaws screen reader for Windows version 2020: https://www.freedomscientific.com/products/software/jaws/ screen readers need to know “next” is disabled in nav bar and that the whole nav bar is a supplemental tool, not how navigation through GI happens (instead that Continue button is way to move on) Survey Monkey and Amazon are good website examples of speech friendly websites https://www.amazon.com/gp/help/customer/display.html?nodeId=201829330 https://www.afb.org/aw/18/5/15212 (see section on screen reader friendly option for amazon.com) Legal Server is a good too avatars need hidden checkbox for hair/skin tone and maybe avatar selectors that explain what user is picking “graphics labeler” for images She’s happy to do another test for us
Good example for us to use for “Accessibility” page on a2jauthor.org: https://help.surveymonkey.com/articles/en_US/kb/Accessibility-at-SurveyMonkey
mike’s thoughts and future Qs: button navigation should auto focus main content so readers automatically read the next question text. also make a logical up/down keyboard nav experience - a shift tab up gets you to the nav bar, and a normal keyboard tab gets you to the first input field/button navbar navigation should not focus the question text, but maybe starts reading it the content of that text in an aria attribute. For example, i’m on
Enter Your Address
page, and i keyboard nav back to ‘name’ - it should start reading -please enter your name …