Q: Are the surveys keyboard accessible? It's seems like hit or miss when I tested it.
Users expect to be able to navigate forms, quizzes, and surveys using their desktop keyboard which is also necessary for most companies to meet WCAG or 508 Compliance requirements. How are you addressing this critical feature?
KirillTereshchenko
Dec 3, 2024A: Hi there,
Yes, it’s supported! You can answer by clicking Enter, using the arrow keys if it’s a swipe-style question, or pressing a number to respond to an NPS question.
SumoProPLUSI’ve tested this extensively and it is still hit or miss as the arrow keys don’t always work when it is a multiple choice question. Please fix this to allow accessibility with these types of questions.
Thanks for details! I will check and fix it.
marykentAgreed! The use of keyboard accessibility is very inconsistent. What's the point of having it work for some questions but not others (multiple choice questions, smiley face or star ratings). If you can allow the keyboard for NPS ratings that use numbers, then you can easily use the same approach with letters assigned to multiple-choice questions.
Also, you can easily assign letters or numbers to smiley faces and star ratings so users can easily select those with a keyboard. Simply place a small number or letter above or below those ratings. Otherwise, allow the use of arrows or the tab key to make those selections. This is how other survey providers do it (like Typeform). This way all the question types are fully accessible, not just two!
Hi Marykent,
Thank you for providing so many details! I’ll ensure that all question types, including Multiple, are fully accessible via keyboard.
What is the timeline for this?
You can track the progress here. I also recommend upvoting it to get notified when it’s released: https://feedback.getmetasurvey.com/p/keyboard-accessibility-for-all-question-types-p22eN9
SumoProPLUSEarlier you said you’ll fix this, but now you ask people to vote on it which raises concerns.
Many companies must ensure compliance with the accessibility requirements of WCAG (global), Section 508 and ADA (U.S.), and AODA (Canada). Therefore, since accessibility has legal implications, it should not be based on votes. Otherwise, this is a deal-breaker and forces us to look elsewhere.
I recommend upvoting the feature to receive notifications when it’s released. Of course, this is optional—it’s up to you!
This is confusing! If the reason for upvoting is simply to be notified of its release, then why hasn’t this item been added yet to the roadmap to show that it’s planned since you already stated you’ll fix the issue? It's currently one of the most-voted features!
Can you please update the status to show this?
Also, what is the estimated timeline for fixing this keyboard accessibility issue?