Accessibility features

[simeonkerkola]

I'm submitting a ...

• bug report
• feature request
• support request

What is the current behavior?

Keyboard control works great, but still lacking many accessibility features.

What is the expected behavior?

vue-simple-suggest to be more screen reader friendly.

Including:

• Necessary aria tags
• Using a ul and li tags for suggestions.
• Clearing the hovered data when list closes or re-renders.
• Note about accessibility when using custom inputs to README
• Anything else?

What is the motivation / use case for changing the behavior?

Something closer to the WAI ARIA 1.1 spec

[simeonkerkola]

I could submit a pull request.

[Raiondesu]

Hello, @sssmi. :)
Sorry for late reply.

We plan to implement ARIA spec for the v2.0.

A PR to the current version would be highly welcome, though!

[Raiondesu]

Ok, so the PR is finally merged into dev! We're gonna make a minor release soon.

I'm going to keep the issue open for task-tracking purposes for the 2.0 version.

[pyryhei]

Hi!

I am experiencing a drop in Lightouse accessibility score. vue-simple-suggest input element fails with error [aria-*] attributes do not have valid values

I think this is caused by the aria-controls attribute being present even when the actual list element with listId is not. This means there's no element with the id that the aria-controls is pointing to until the v-if condition of the list is fulfilled.

Should the aria-controls attribute maybe be added dynamically simultaneously with the v-if condition of the list element being fulfilled?