Summary of issues related to A11y

[ebonow]

Here is a list of outstanding issues related to accessibility. Version 5 included many new features to better support accessibility and it's unclear what issues should be closed and what issues still remain.

#1570 Adding support for aria-describedby attribute

- Has PR #4082

#1585 Screen reader read's selected value as 'blank'

#2456 A possible plan to improve v2 accessibility and make it ARIA compliant

#3351 Loading state not announced by screen reader

#3675 NVDA has issues reading options

#3818 Aria-expanded property is not getting populated in react-select

#4062 Keyboard accessibility fails when JAWS is ON

- Sean last commented on 9/13/21 and it's likely this can be closed

#4277 Grouped options breaks screen readers

- It seems unclear what behavior is recommended for grouped options

#4585 Screen reader is not reading focused option using Narrator

-Issue created before v5 release

#4813 Focus is lost on select field when using a screen reader, it is not possible to choose the option

- Unable to reproduce issue and author has yet to reply.
- From the observation though accessibility on the documentation site is extremely unfriendly as the focus outline has been forcibly removed from the view source/codesandbox icon buttons. I've added this to the improve documentation discussion list of todos.

#4814 Axe is reporting 'Elements must have sufficient color contrast' for input

_- Axe is reporting on this because the Placeholder and Input overlap which is by design. _
- Likely will close this but brings up a better discussion of perhaps entirely removing the placeholder component in the future in favor of using the placeholder attribute

#4832 Accessibility issue with combobox

- Unable to reproduce issue with mismatching ids auto-generated by instances.
- A different console error was discovered thought regarding the rendering of the AriaLiveRegion component.