Bug 253209

Summary: AX: Enhanced Accessibility Mode breaks arrow-key scrolling for non-VoiceOver users
Product: WebKit Reporter: Cooper Barth <cooper_barth>
Component: AccessibilityAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WONTFIX    
Severity: Major CC: aboxhall, andresg_22, apinheiro, cfleizach, dmazzoni, ews-watchlist, jcraig, jdiggs, samuel_white, thomas_mchugh, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari 16   
Hardware: Mac (Apple Silicon)   
OS: Other   
Attachments:
Description Flags
Patch ews-feeder: commit-queue-

Cooper Barth
Reported 2023-03-01 17:29:50 PST
Enhanced Accessibility Mode breaks arrow-key scrolling for non-VoiceOver users.
Attachments
Patch (1.96 KB, patch)
2023-03-01 17:44 PST, Cooper Barth
ews-feeder: commit-queue-
Radar WebKit Bug Importer
Comment 1 2023-03-01 17:30:00 PST
Cooper Barth
Comment 2 2023-03-01 17:44:09 PST
Tommy McHugh
Comment 3 2023-03-01 17:50:30 PST
I am slightly concerned about not doing this for FKA given the similar AX model between it and VO
chris fleizach
Comment 4 2023-03-01 19:02:00 PST
Comment on attachment 465253 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=465253&action=review > Source/WebCore/accessibility/AXObjectCache.cpp:224 > + if (flag && client == kAXClientTypeVoiceOver) This is an SPI that expects to be set. This will break that SPI Also isn’t VO already setting this?
Cooper Barth
Comment 5 2023-03-03 15:38:51 PST
After some further investigation, agreed that this patch likely isn't the correct fix, seeing as we do need to enter AssistiveControl to enter Enhanced Accessibility Mode for other non-scrolling related functionality. A likely better fix would be to modify Enhanced Accessibility Mode to only disable scrolling if the client is VoiceOver. Ongoing discussion with the team as to whether this behavior should be enabled for Full Keyboard Access as well.
Cooper Barth
Comment 6 2023-04-13 11:29:26 PDT
Moving this to do not fix - we're making a change on our end to resolve the issue.
Note You need to log in before you can comment on or make changes to this bug.