abaevbog

> OK, so @adomasven called it — JAWS is hard-coding support for Mozilla. Pretty much! There is a config file that sets which apps and how are to be handled....

A few followup thoughts: - Going back to MozillaWindowClass is great as it seems to fix itemTree and fixes inputs in itemPane and everywhere else in the main window. That...

I have another thought here to potentially address JAWS not properly working in our dialogs. In my last comment, I think overthought things a bit. Since it is the dialog...

The accessibility side looks good to me - the rows labels are announced when the input is focused as expected which is great! I am noticing something buggy with the...

@windingwind this is great! Besides voiceover, I checked this with NVDA and JAWS, and the tab names all get announced as expected after searching. JAWS tends to be somewhat picky,...

@windingwind great, it all sounds good now! As far as the last point, I didn't actually realize that a hovered `X` is also focusable on tab. I think that it...

Great! Yeah, I think not including the hovered row's `X` into tab navigation feels more straightforward (and consistent with Firefox too). My only remaining question is why is title skipped...

Hm, yeah. It is seemingly not possible to move into the context menu via keyboard at all ... It's strange because there were some issues with the options from the...

Another strange behavior I noticed while working on this to record: annotations can become impossible to select via keyboard if the context menu is closed by clicking outside of it...

This approach of having a focusable wrapper with `aria-description` works fine but it is unfortunate that in that case we have an extra tabstop which makes it inconsistent with other...