The simplest way to create progressive web apps across platforms and devices. Start here. This repo is home to several projects in the PWABuilder family of tools.
Elements that contain scrollable content (such as divs or iframes) cannot be scrolled using keyboard navigation (e.g., arrow keys or tab + arrow keys).
How do we reproduce the behavior?
Repro Steps:
Open the given PWA Builder URL in Anaheim dev browser.
Run the Fast pass from the AI4W.
Observe the issue.
What do you expect to happen?
Users should be able to navigate through and scroll within elements containing scrollable content using keyboard controls, ensuring all content within these elements is reachable and usable.
What environment were you using?
Test Environment:
OS Build: Windows 11 Enterprise Insider Preview 24H2 (26120.461)
Edge Browser: Version 123.0.2400.1 (Official build) dev (64-bit)
URL: https://docs.pwabuilder.com/#/home/pwa-workshop
Tool: AI4W
Additional context
Element path:
.language-bash[data-lang="bash"]:nth-child(45) > .language-bash
How to fix:
Fix any of the following:
Element should have focusable content
Element should be focusable
User Impact:
Users who rely solely on keyboard navigation (e.g., individuals with mobility impairments or who cannot use a mouse) may be unable to access all content within scrollable elements.
What happened?
Elements that contain scrollable content (such as divs or iframes) cannot be scrolled using keyboard navigation (e.g., arrow keys or tab + arrow keys).
How do we reproduce the behavior?
Repro Steps:
What do you expect to happen?
Users should be able to navigate through and scroll within elements containing scrollable content using keyboard controls, ensuring all content within these elements is reachable and usable.
What environment were you using?
Test Environment:
OS Build: Windows 11 Enterprise Insider Preview 24H2 (26120.461) Edge Browser: Version 123.0.2400.1 (Official build) dev (64-bit) URL: https://docs.pwabuilder.com/#/home/pwa-workshop Tool: AI4W
Additional context
Element path: .language-bash[data-lang="bash"]:nth-child(45) > .language-bash
How to fix: Fix any of the following: Element should have focusable content Element should be focusable
User Impact: Users who rely solely on keyboard navigation (e.g., individuals with mobility impairments or who cannot use a mouse) may be unable to access all content within scrollable elements.
WCAG Reference: https://www.w3.org/WAI/WCAG22/Understanding/keyboard
Attachments: