paperbits/paperbits-demo

[Screen readers - API Management - Table]: Screen Reader is not identifying the visually appearing table present, while navigating using table shortcut key 'T'.

JMach1 opened this issue · 0 comments

TL;DR

Table widget is not recognized as a table by Narrator.
Screen Reader is not identifying the visually appearing table present in the page while navigating using table shortcut key 'T'.

component: paperbits-core\src\table

Related issue (same component): #215

MS task

https://msazure.visualstudio.com/One/_workitems/edit/15430867

User Experience:
Users Who rely on screen readers are getting confused and will not know that table is present in the page if narrator is not recognizing the table present in the page while navigating using table shortcut key 'T' hence get to failed proper information.

Note: User credentials should NOT be included in the bug.
Repro-Steps:
Open Azure portal with valid credentials and create a API Management.
Select Developer Portal (Preview) button and select it.
Navigate to the https://accessibility.developer.azure-api.net/signin-sso?token=1&201906090559&Sg/pisCBkhUDO4/kkfFGp5bBz7eQmw3UXhNmBz+YTvVnNuwUXn1KIx657NMEkAW86ywLo2OiBTGd3NTNbLR3Qw==
Navigate to the Left nav and select Pages button.
Navigate to the Pages window. select API Reference option.
Navigate to the any editable control details and select Add widget.
Navigate to the Table and select it.
Table will be added.
Verify whether screen Reader is identifying the visually appearing table present, while navigating using table shortcut key 'T'.
Actual Result:
Screen Reader is not identifying the visually appearing table present in the page while navigating using table shortcut key 'T'.

Observation:

When user invokes Table shortcut key(T), narrator is narrating as "There are no table in the page".

JAWS: When user invokes Table shortcut key(T), JAWS is narrating as "There are no table in the page".

NVDA: When user invokes Table shortcut key(T), Narrator is narrating as "There are no table in the page".

Expected Result:
Screen reader should be identify the visually appearing table present in the page while navigating using table shortcut key 'T'.

Ex: When user invokes Table shortcut key(T), narrator should narrate as "Cell Table with 1 row and 3 Columns".

Note:
Screen Reader is not identifying the visually appearing table present, while navigating using table shortcut key 'T'.throughout the Application.
MAS Reference:
MAS 1.3.1 – Info and Relationships
Reference Links:
Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.
External Bug Process: If this bug belongs to external team, mark it as resolved/done and assign it back to the tester with notes on where to file/route the bug. For more information, please use this External Bug Process (sharepoint.com) “HCL Staff should not log any third-party external bugs. Should be routed to eDAD team”.
Please reach out to C&AI Teams channel for any process related queries.