Describe the bug
On https://tacc.utexas.edu/use-tacc/software-list/, the software table contains 200+ rows, each with a "Version Documentation" link. Once a keyboard user tabs into the table, they are forced to Tab through every single focusable link in all rows before focus can leave the table.
To Reproduce
- Go to https://tacc.utexas.edu/use-tacc/software-list/
- Press tab until focus enters the software list table
- Continue pressing tab.
Focus cycles through every "Version Documentation" link in every row before exiting the table.
Expected behavior
Tables containing many interactive elements should probably use the WAI-ARIA grid keyboard interaction pattern so that:
- tab moves focus into the table at a single entry point, and out again with one more tab
- Arrow keys navigate between rows/cells within the table
Alternatively, a "Skip table" / "Skip to next section" link placed before the table would allow keyboard users to bypass it entirely.
Screenshots

Additional context
- Not a "keyboard trap" (WCAG 2.1 SC 2.1.2), but significantly degrades usability for keyboard-only and assistive technology users.
- The WAI-ARIA Authoring Practices recommend using
tabindex="-1" on descendant focusable elements inside composite widgets, with arrow-key navigation handling added via JavaScript.
- Maybe useful: Infragistics Grid Keyboard Navigation
Describe the bug
On https://tacc.utexas.edu/use-tacc/software-list/, the software table contains 200+ rows, each with a "Version Documentation" link. Once a keyboard user tabs into the table, they are forced to Tab through every single focusable link in all rows before focus can leave the table.
To Reproduce
Focus cycles through every "Version Documentation" link in every row before exiting the table.
Expected behavior
Tables containing many interactive elements should probably use the WAI-ARIA grid keyboard interaction pattern so that:
Alternatively, a "Skip table" / "Skip to next section" link placed before the table would allow keyboard users to bypass it entirely.
Screenshots
Additional context
tabindex="-1"on descendant focusable elements inside composite widgets, with arrow-key navigation handling added via JavaScript.