[SF][Table][A11y]: [Activation Instructions Are Not Provided When There Is Single Row]

[tandan0813]

Describe the bug

Hi team,
There is an a11y issue reported that Selection announcement for single radio button is not provided. Arrow keys are used to navigate while enter / space is used for selection.

And the expected behavior is that the instructions to use enter / space key to select the row needs to be provided .

Is it reasonable?

Isolated Example

No response

Reproduction steps

...

Expected Behaviour

No response

Screenshots or Videos

No response

UI5 Web Components for React Version

2.18.0

UI5 Web Components Version

2.18.0

Browser

Chrome

Operating System

No response

Additional Context

No response

Relevant log output

Organization

No response

Declaration

• I’m not disclosing any internal or sensitive information.

[Lukas742]

Thanks for reporting! I'll forward this issue to our UI5 Web Components Colleagues as the affected component is developed in their repository.

[s-todorova]

Hello @UI5/ui5-team-tbl,

Could you please take a look at this issue? Sample

Best,
Siyana

[kaistephanrichter]

Hi, the example shows a single selection table with only one row. Single selection, represented by the radio button doesn't have a de-selection but only a selection. De-selection would happen by selecting another item in the table. In case the application wants to offer a "no-selection" row in the list, this would have to be an additional option that should always available, ideally in the beginning of the table.

You would need something like
[ ] No employee
[x] Employee X

select "No employee" to remove the selection.
[x] No employee
[ ] Employee X

The table doesn't know whether the business process allows for a none-selection but with the single selection can ensure that at least one entry is selected. If we would like to introduce an optional single selection this would have to be another visualization. The grid tables support this by displaying the square in the beginning. But this is a very uncommon visualization and behavior which we don't think should be introduced in the responsive table as well.