Skip to content
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 doesn't work in all tables #414

Open
alexeysvyridov opened this issue Mar 27, 2023 · 3 comments
Open

accessibility doesn't work in all tables #414

alexeysvyridov opened this issue Mar 27, 2023 · 3 comments

Comments

@alexeysvyridov
Copy link

Hi, as i know the rsuite-table is supporting accessibility, but it doesn't work...

Versions

react version - 18.2.0
rsuite-table - 5.10.1

What is the expected behavior?

Table - navigation by column with ctrl + option (arrows) - accessibility

What is the current behavior?

image

accessibility doesn't work, it doesn't navigate by column

What are the steps to reproduce?

it's doesn't work in all Tables (Virtualize)

@simonguo
Copy link
Member

Hi @alexeysvyridov
Currently Table is only associated with ARIA roles, keyboard interaction is missing.

I will plan to perfect the keyboard interactions.

@alexeysvyridov
Copy link
Author

I mean that some things are blocking accessibility when screen reader is activated. it's not handlers by keybord, it's just navigation by cells.
after some investigation I found two things, which blocking accessibility:
file Table.tsx - row 1056 translateDOMPositionXY: translateDOMPositionXY.current I just set to null
and usePosition row 189 : commented // updatePosition(nextDuration, nextBezier);
It will work, but then I have some problems with css, I made positon rs-table-row.rs-table-row to position: initial !important
after that I have some issues with css, I don't see one row of table, I guess, he does't calculate the height of one row.
hopefully my description will help you to make a quick fix.

@simonguo
Copy link
Member

simonguo commented Apr 3, 2023

@alexeysvyridov
Do you have this problem if you try to use [email protected] version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants