I believe the summary element should be considered an interactive element and that there shouldn't be any errors thrown when a click listener is attached to it:

// currently flags the following:
// jsx-a11y/click-events-have-key-events
// jsx-a11y/no-static-element-interactions
<summary onClick={clickHandler} />

[The spec does list details element as interactive](https:

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

RawGit has been placed in sunset mode, with a disclosure that support may end in October 2019.

jsDelivr offers a RawGit migration, so here's Google's inert polyfill re-hosted:
https://cdn.jsdelivr.net/gh/GoogleChrome/inert-polyfill@v0.1.0/inert-polyfill.min.js

Now that custom properties have been added to the switch module, I should add a section to the contributing guide, regarding the intended use & strategy for custom props going forward,

The links list feature in JAWS does not show the accessible description that is provided by aria-describedby or the title attribute when an accessible name is present. This information is important to users. Screen reader users demand this information be available in the accessible name instead -- but showing the accessible description would allow users to access it while using compliant code s

In both FF and Chrome, when I tab from a header on an expanded panel, the focus leaves the header but does not appear to go anywhere. Especially for 'rookie' users, this is highly confusing at some point. The user must press TAB again to put focus on the first focusable element.
This 'missing' focus item occurs using SHIFT+TAB as well.

While testing the modal for accessibility with various screen reader and browser combinations (NVDA + FIREFOX, JAWS + IE, VOICEOVER + IOS) the results are not as expected.

When the modal window displays, NVDA reads the whole content automatically which is ok but with JAWS and VOICEOVER the content is not read at all.

Moving the focus to the content will read the content but not the inputs i