Accessibility improvements

Hi there,

We’re using the OneSignal plugin on local government websites, which must adhere to WCAG 2.2 accessibility standards.

Currently, the onesignal-bell-launcher-button is not accessible via keyboard navigation because it is implemented as a <div> and not a <button>. It also can’t be closed by keyboard. This creates an issue for users who rely on keyboard navigation.

Specific Issue:

• (When users navigate the site with 400% zoom on a screen resolution of 1280×1024,) the black bar that expands with the message “Sign up for notifications” upon hover with mouse cannot be closed using the keyboard.
• This obstructs the underlying page content, and users are unable to read or interact with parts of the page when navigating with the keyboard.

WCAG Reference:

• 1.4.13 Content on Hover or Focus (Level AA): Interactive elements like this should provide a mechanism to close content triggered on hover or focus, accessible via both mouse and keyboard.

Could you update the implementation to replace the <div> with a semantic <button> ? And ensure that the expanding bar includes a keyboard-operable close mechanism?

Kind regards,
Yvette