Skip to content

Table accessability#131

Merged
alaric-rd merged 15 commits intomainfrom
61-table-accessability
Dec 12, 2024
Merged

Table accessability#131
alaric-rd merged 15 commits intomainfrom
61-table-accessability

Conversation

@alaric-rd
Copy link
Contributor

Closes #61

This grew into a wider accessibility audit.

  1. Used tabindex to make the focussed cell selectable via tabbing with the keyboard
  2. Made the browser's notion of focus follow our notion of focus
  3. CSS tweaks and ARIA roles to meet WCAG guidelines
  4. Various bug fixes in keyboard navigation
  5. Allowed tab to move browser focus out of the table, as opposed to emulating Excel's use of tab to navigate within a sheet

…key, rather than the *effective* end cell

We were getting stuck in loops where the actual end cell was a cell that, due to
merging, was expanding the selection further - and then trying to shift+arrow
in the opposite direction to that extension put the end cell back in the
original "actual" end cell, which then expanded out to put the selection
exactly back where it was.
...but tabbing out destroys the selection, which means our use case of
setting up a selection then tabbing to a submit button doesn't work.
Copy link
Contributor

@rossjones rossjones left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Tried it out and worked as expected.

@alaric-rd alaric-rd merged commit 04b6c80 into main Dec 12, 2024
@alaric-rd alaric-rd deleted the 61-table-accessability branch December 12, 2024 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Selecting cells using the table view has accessibility issues

3 participants