o interact with this element using the keyboard, replace the non-widget role, 
*and/or* use the explicit `tabindex="-1"` attribute to remove the element from the keyboard focus (tab) order
- **Or**, if users *should* be able to interact with this element using the keyboard, use a valid widget role

### Examples:

This first example is a simple focusable *toggle button*. 
JavaScript and CSS would need to be added to provide the appearance and full button functionality:

```
<div id="saveChanges" tabindex="0"