Nick Colley

Relevant PR: https://github.com/alphagov/accessible-autocomplete/pull/192

I have reviewed this issue, and some related alongside Hanna's findings and done some more investigation and chatted with the accessibility community and the team. ## Our current implementation is...

I have created two spikes to test: - [Using aria-live to announce state changes ](https://github.com/alphagov/govuk-frontend/pull/1561) - [Using visually hidden text to indicate state changes](https://github.com/alphagov/govuk-frontend/pull/1560) I've recorded the conclusions here: https://docs.google.com/spreadsheets/d/1i1yFXuv-mvvDpi36gd9ZFjRiaUM7m-1WppIZYnYbUts/edit?usp=sharing...

The Design System team met and discussed these findings. This pattern has been through a lot of user research by different service teams and we have not had any feedback...

Hey @dkrasmussen! Can you give us more information what you're trying to do so we can reproduce your issue? It would be good to have some code snippets too.

Hello @AlecRust , Thanks for raising this. It seems like the `aria-expanded` state should be consistent when showing 'no results', but I would need to properly think this through and...

From Hanna in the other thread: ### Error: "Radio inputs with the same name attribute value must be part of a group" #### Underlying issue A bit of a question...

I would propose given the complexity (and therefore how difficult we're finding to maintain this component) to intentionally keep this component very simple and have good guidance to integrate search...

@alexnewmannn appreciate you offering to help but we don't have a lot of time to work on features for this component, so we're prioritising bugs: for example accessibility issues. We'll...

Should this be documented somewhere? Edit: Actually, I've reread it this does not introduce anything new. 👍