![Haz on Twitter: "By using a composite role, you're telling screen readers that keystrokes shouldn't be interpreted as commands. Instead, when a composite widget gets focus, the screen reader will enter focus Haz on Twitter: "By using a composite role, you're telling screen readers that keystrokes shouldn't be interpreted as commands. Instead, when a composite widget gets focus, the screen reader will enter focus](https://pbs.twimg.com/tweet_video_thumb/EepBRWBWoAEYUwG.jpg)
Haz on Twitter: "By using a composite role, you're telling screen readers that keystrokes shouldn't be interpreted as commands. Instead, when a composite widget gets focus, the screen reader will enter focus
![Haz on Twitter: "Roving tabindex consists of setting tabindex="-1" on all interactive elements within the composite widget so they remain focusable, but not tabbable. Usually, the first item will get tabindex="0" so Haz on Twitter: "Roving tabindex consists of setting tabindex="-1" on all interactive elements within the composite widget so they remain focusable, but not tabbable. Usually, the first item will get tabindex="0" so](https://pbs.twimg.com/media/EepBIE5XYAAnkhO.png)
Haz on Twitter: "Roving tabindex consists of setting tabindex="-1" on all interactive elements within the composite widget so they remain focusable, but not tabbable. Usually, the first item will get tabindex="0" so
![Mechanism for setting the tabindex focus flag without sprouting tabindex attribute? · Issue #762 · WICG/webcomponents · GitHub Mechanism for setting the tabindex focus flag without sprouting tabindex attribute? · Issue #762 · WICG/webcomponents · GitHub](https://user-images.githubusercontent.com/285965/77138281-b707c100-6a2e-11ea-8245-b3f3d1581adc.png)