-
Notifications
You must be signed in to change notification settings - Fork 780
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VoiceOver doesn't read question titles because aria-label
is missing from question title HTML elements
#6859
Comments
) * work for the #6859 * work for the #6859 (remove code duplication) * work for the #6859 (other items) * work for the #6859 (fix markups) * work for the #6859 (fix markups-2) * work for the #6859 (fix markups-3) * work for the #6859 (fix markups-4) * work for the #6859 (fix ff tests) * work for the #6859 (review-1)
aria-label
is missing from question title HTML elements
Upon further research, it appears that the title of a Radiogroup question is not being read by a Voice Over screen reader when the Radiogroup appears on the first survey page and the survey.focusFirstQuestionAutomatic option is enabled (which is the default setting). However, the structure of the resulting form page seems to comply with accessibility standards. Additionally, we have tested the survey with other screen readers and confirmed that the title of a radiogroup question is correctly read by them (for example, we tested it with NVDA). Therefore, it seems to be a specific issue that is only reproduced on the Voice Over reader. Unfortunately, we may not be able to address this issue at the moment. To resolve this issue, we recommend disabling the survey.focusFirstQuestionAutomatic option. With this option disabled, Voice Over should correctly read the title of a radiogroup question even if the question appears on the first survey page. |
T14457 - Re: Accessibility Issue: Aria label missing.
https://surveyjs.answerdesk.io/internal/ticket/details/T14457
related issues:
The text was updated successfully, but these errors were encountered: