Ryan Johnson

## `HTMLElement.prototype.tabIndex` broken with no intent to fix Edge 12-17 and IE incorrectly return `0` for non-interactive elements without an explicit `[tabindex]` attribute. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/4365703/ * This bug **will not be...

## Poor / Degraded Accessibility ### File Input (`input[type="file"]`) #### `input[type="file"]:active` never matches when using a keyboard * IE (all versions) * Edge 12-18 This prevents visual feedback when pressing...

Thanks for reporting this. We're in the process of finalizing our focus states and this will be updated accordingly, in the near future.

Also, to note, `user-select: none;` isn't guaranteed to prevent selection.

Unfortunately, we can't remove the outline on focus due to accessibility requirements and browsers haven't implemented the `:focus-visible` pseudo-selector to allow us to turn off the outline only for mouse...

For reference: * https://developer.paciellogroup.com/blog/2018/03/focus-visible-and-backwards-compatibility/ * https://drafts.csswg.org/selectors-4/#the-focus-visible-pseudo * https://caniuse.com/#feat=css-focus-visible

_additional context:_ In `v0.15.0-rc.0`, `` added functionality in an attempt to automatically update its control element to make it keyboard accessible. However, due to a bug with IE and Edge...

I can confirm that Edge 18 has fixed the bug.

Nothing can be done to fix IE, but we should update documentation to make consumers aware of the issue.

This is a valid bug. Because we're using `` elements to activate radio `` elements, the browser doesn't select the input unless it sees a `mouseup` event on the label,...