WebAIM - Web Accessibility In Mind

E-mail List Archives

weird focus behavior

for

From: Jonathan Cohn
Date: Apr 25, 2025 5:15PM

This does not sound like the write behavior on the part of the browser. If this is occurring in Chrome, have you tried Firefox?


> On Apr 25, 2025, at 2:03 PM, Mike Warner via WebAIM-Forum < <EMAIL REMOVED> > wrote:
>
> Well, this is interesting. As I'm testing a website using a keyboard
> without a screen reader, closing a dialog by hitting escape or tabbing to
> and activating a close button, the focus returns to the button that opened
> the dialog. When using JAWS and NVDA, the focus gets lost and goes to the
> body tag. When I have a live expression in the developer console to see the
> active element (document.activeElement), I can see clearly that the active
> element is the body after closing the dialog. That said, after closing the
> dialog, both screen readers announce the dialog opener button and if I do
> nothing else, hitting enter right after closing the dialog will open the
> dialog again. NVDA's focus indicator also shows that the body tag has the
> focus. Hitting the tab key after closing the dialog with NVDA or JAWS
> brings me to the skip menu, which is the first focusable element on the
> page.
>
> Has anyone else encountered this?
>
> Thanks,
> Mike Warner
> Director of IT Services
> MindEdge Learning
>