docs(site): Architecture tables are not keyboard-scrollable at narrow widths
Maintainers usually reply within 1 day
@devops-thiago is already working on this.
Since Oct 21, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- html
- Domain
- accessibility, documentation
Research direction
Start with the Architecture page’s horizontally scrolling table wrappers on the docs site and check how they behave at a 375px viewport. Make the wrappers keyboard-scrollable or let the tables wrap, then verify that axe reports no scrollable-region-focusable issue in light and dark mode and that the tables scroll with the keyboard.
Written by the indexing model from the issue text.
Description
Background
axe-core 4.10 reports scrollable-region-focusable on five tables of the Architecture page when the viewport is narrow enough for them to scroll horizontally. A keyboard user cannot scroll them, because the scrolling container has no tabindex and holds no focusable element. Lighthouse does not run this rule, so the page still scores 100. Found while checking #1132 (PR #1158); the issue predates that change.
Change required
Make the horizontally scrolling table wrappers on the docs site focusable (for example tabindex="0" with an accessible name), or let the tables wrap instead of scrolling.
Acceptance criteria
- axe reports no
scrollable-region-focusableon the Architecture page at a 375px viewport, in light and dark mode. - The tables can be scrolled with the keyboard.
- Dominant language
- Java
- Stars
- 35
- Forks
- 7
- Avg merge
- 9h 10m
- Merged PRs (30d)
- 189
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from devops-thiago/ThrillhouseBot
-
docs(site): repeated code-block landmarks fail landmark-uniquePossibly taken @devops-thiago claimed this 1 day ago. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
devops-thiago/ThrillhouseBot#1164 · 1 assignee ·
Maintainers usually reply within 1 day
-
docs(site): Mermaid edge-label contrast on Architecture and a table header on How it comparesPossibly taken @devops-thiago claimed this 4 days ago. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
devops-thiago/ThrillhouseBot#1132 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
fix(review): always name the linked issue and its unmet criterion in the summaryPossibly taken @devops-thiago claimed this 5 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
devops-thiago/ThrillhouseBot#1093 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
devops-thiago/ThrillhouseBot#321 ·
Maintainers usually reply within 1 day
-
docs: define versioning, deprecation, and support policyPossibly taken @devops-thiago claimed this 4 days ago. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
devops-thiago/ThrillhouseBot#46 ·
Maintainers usually reply within 1 day
All issues in devops-thiago/ThrillhouseBot
Similar issues
-
status: needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JabRef/jabref#17546 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
hiero-ledger/hiero-sdk-java#3010 ·
Maintainers usually reply within 1 day
-
Optimize consumer version heatmap aggregation to avoid repeated scansPossibly taken @praykaria31 claimed this today. Opentype/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Apicurio/apicurio-registry#10662 · 1 comment ·
Maintainers usually reply within 1 day
-
a:false-positive
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
status: waiting-for-triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
spring-projects/spring-boot#52347 ·
Maintainers usually reply within 2 days