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
Accessibility Bug: When the message strips are accessed, the information inside the message strips are not conveyed (screen reader) #3123
Comments
@Sanjay-1312 Please test this issue in this url https://deploy-preview-5458--fundamental-ngx.netlify.app |
Hello Colleagues, The issue is not fixed, hence i am re opening the issue. URL: https://deploy-preview-5458--fundamental-ngx.netlify.app |
@kavya-b This issue is not fixed it-seems. Kindly have a look. |
As discussed with @puru-hk and @Sanjay-1312, the only way we see to fix this in JAWS is to provide @Sanjay-1312 will follow up with his team to understand whether we need focus on the entire message strip and how can they test a strip without a close button, if it is expected that close button will read out the entire strip's information. |
@InnaAtanasova @droshev currently, we do not have focus specification by Fiori for Message Strip. However, it seems like this is necessary in order for screen readers(especially JAWS) to read the message strip content. Can you let us know if we can get the focus specs added to Message Strip visual specs or if we can use the general Focus Visual Concept spec to apply focus to Message Strip in order to address this a11y issue? It would also help if we get feedback from design team regarding this. Please help. This PR and issue is blocked until we are able to add focus to Message Strip container. |
@kavya-b the content in the message strip is custom and it is up to application developers to create. If the use case is to have focusable elements then the reader app will focus and read. We don't control what it is inside. |
@droshev I agree we don't have control on the content, but the a11y team's requirements say the following:
this way, focus on the whole message strip is no longer required, but extra information would have to be read out from the close button. request @Sanjay-1312 to add your thoughts and suggest if @droshev 's comment is okay then we can keep this issue closed, or reopen this issue as needed. |
This issue is not fixed. Hence reopening this issue. |
Hello Colleague, Retest has been taken reported issue still persist the same so please check and do the needful. Expected: The content inside the message strips should be conveyed properly when the message strips are accessed(screen reader) Retest environment: Regards, |
Hello Colleague, Retest has been taken with the below environment test results are below: Issue: When the message strip is accessed the information within the message strip is not read out. Expected behavior: Retest Environment: Regards, |
Fundamental core component: "Message Strip"
Description: When the message strips are accessed, the information inside the message strips are not conveyed (screen reader)
Expected: The content inside the message strips should be conveyed properly when the message strips are accessed(screen reader)
Attached the screenshot
Note: - Issue persists for all the message strips present within the ‘Message strip’ control.
The text was updated successfully, but these errors were encountered: