Enterprise: Accessibility: Datagrid does not announce selected row

Created on 25 Apr 2019  路  7Comments  路  Source: infor-design/enterprise

Describe the bug
The selected column in the datagrid is announced by AT as "row selected" instead of what user is selecting. It may be advisable to add the name of the item user is selecting to the select span name.

To Reproduce in Landmark
Steps to reproduce the behavior:

  1. Go to https://hcm-tampm01-prd.inforcloudsuite.com/hcm/EmployeeSelfService/form/Employee%287004,700417%29.LRCFullEmployeeProfile?csk.showusingxi=true&csk.JobBoard=INTERNAL&csk.HROrganization=7004&menu=LRCEmployeeMenu.MyProfile
  2. Click on any magnifying glass icon to launch a modal dialog
  3. While using AT, select a row within the datagrid
  4. AT does not announce the selected row.

How to Fix for EP

Expected behavior
AT should announce the selected option and not just that a row is selected.

Additional context

[3] accessibility datagrid landmark type

Most helpful comment

Those steps are correct. The suggestion here is that we add a short metadata descriptor to append to the aria-label to give it more context when selecting. For example, rather than just saying "Select", we could say "Select 52106 Monitor"

All 7 comments

Can i get a screen shot of this screen in Landmark?
Also how can i reproduce it on http://master-enterprise.demo.design.infor.com/components/datagrid/example-mixed-selection.html (actually for these issues thats the primary thing for US)

Below is an example of the datagrid in a modal dialog in Landmark:

Screen Shot 2019-04-25 at 4 10 38 PM

To recreate in the component library, follow the same steps from Landmark:

  1. While using AT, select a row within the datagrid
  2. AT does not announce the selected row

So meaning..

Those steps are correct. The suggestion here is that we add a short metadata descriptor to append to the aria-label to give it more context when selecting. For example, rather than just saying "Select", we could say "Select 52106 Monitor"

I'm skeptical that this is a good idea to implement. What if the columns are different or reordered? Happy to be convinced otherwise, but it seems like a one-off example and for Accessibility one can arrow through the row to discover the different pieces of information.

I was thinking that maybe..

  • we add a settings.columId that is the id of the column that is the "important" one (i thought we had a grid "id" column setting but not seeing one on quick glance
  • then this is added to the message in an audible span

Tested this on Chrome Vox and it's working correctly. This issue is now resolved.

Was this page helpful?
0 / 5 - 0 ratings