Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aria live regions #77

Open
1 task done
Lewiscowles1986 opened this issue Jan 20, 2021 · 4 comments · May be fixed by #78
Open
1 task done

Aria live regions #77

Lewiscowles1986 opened this issue Jan 20, 2021 · 4 comments · May be fixed by #78

Comments

@Lewiscowles1986
Copy link
Contributor

Lewiscowles1986 commented Jan 20, 2021

Is your feature request related to a problem? Please describe.

I've been working with ARIA a little more lately and mixing with people that know a lot more about this than me.

After reading https://dev.to/savvasstephnds/the-problem-with-autocomplete-and-how-to-fix-it-2ill

I Tested plete.dev and it seems that we may be able to get a better screen-reader support for plete using ARIA live regions.

Describe the solution you'd like

As a user with a need for screenreader functionality, I would like to have the list of items read out, and each highlighted item read as the user moves (using cursor keys) between them, so that prior to selecting an option; I can be contextually aware of where I am, and make the correct choice.

Describe alternatives you've considered

I am interested to hear of alternatives. Perhaps making each choice a button would allow for reading, but it feels like an abuse of the DOM.

Motivation and involvement

  • I / My organization is willing to commit to development and maintenance of this feature / request
  • [] I / My organization wish to financially contribute to the development of this feature / request
  • [] This would be nice to have, but I wish to have no involvement

Proof of concept

Is there any prior-art or a proof-of-concept; perhaps another project using this one?

If You are interested in this, I would be happy to create a proof-of-concept.

Additional context

I tested using https://chrome.google.com/webstore/detail/screen-reader/kgejglhpjiefppelpmljglcjbhoiplfn

I Would be happy to produce a screen recording of the current behavior and post recordings of the proposed improvement.

@Lewiscowles1986
Copy link
Contributor Author

I've come across something during spelunking this... The spec for aria-autocomplete mentions implementations MAY want to implement aria-activedescendant property .

It seems that this may be enough. live-region was not enough to announce the items selected.

During testing, I personally found the announcement confusing and opted to use template literals to append Choice: ${label}. to the elements when not yet selected. It may be incorrect and would likely need testing by people who use accessibility features, to ensure I'm not engaging in well-meaning hot-takes; that do not help the users.

@Lewiscowles1986
Copy link
Contributor Author

I Just checked using JAWS. The way that screen reader works seems to break the normal operation of Plete using a keyboard. There might be more to this still.

@Lewiscowles1986
Copy link
Contributor Author

Plete-Chromebook-ARIA-hack-WiP.zip
So I don't lose this if it takes a while to come back to; here's the current hacking at output.

@mroderick
Copy link
Owner

I think improved ARIA and screenreader support would be a great addition to this project 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants