(In reply to Anna Yeddi [:ayeddi] from comment #3) > screen readers like NVDA won't go in Browse mode that overwrites the arrow nav pattern and is currently buggy Just for clarity, the behaviour you're seeing is expected in browse mode. Screen readers deliberately don't set focus when moving the browse mode cursor because setting focus can have unexpected side effects (including performance degradation) on modern websites. Note that alow vision NVDA user could enable various settings in NVDA menu -> Settings -> Vision to highlight when moving the browse mode cursor. Having said that, given that this page implements keyboard navigation with cursor keys and given that the experience is superior with the native keyboard navigation, we think role="application" is appropriate here.
Bug 1846572 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Anna Yeddi [:ayeddi] from comment #3) > screen readers like NVDA won't go in Browse mode that overwrites the arrow nav pattern and is currently buggy Just for clarity, the behaviour you're seeing is expected in browse mode; this is not a bug. Screen readers deliberately don't set focus when moving the browse mode cursor because setting focus can have unexpected side effects (including performance degradation) on modern websites. Note that alow vision NVDA user could enable various settings in NVDA menu -> Settings -> Vision to highlight when moving the browse mode cursor. Having said that, given that this page implements keyboard navigation with cursor keys and given that the experience is superior with the native keyboard navigation, we think role="application" is appropriate here.