🐛 Bug Report

In my next.js where I'm adding in React Spectrum, I placed the <Provider/> in my /pages/_app.tsx:

<SSRProvider>
  <Provider>
    {/* ... */}
  </Provider>
</SSRProvider>

Noticed this in reviewing #3165. In determining if an element is focused, axe-core looks at the disabled attribute. However it doesn't check if that attribute is allowed for the node. So the following link is incorrectly determined as not focusable:

<a href="foo.html" disabled>Hello</a>

This bug exists in lib/commons/dom/focus-disabled.js. The fix is to check `vNode.props.nod

Summary

Running the WAVE plugin shows not all text has sufficient contrast, and an empty link is present, these are minor issues and potentially false positives, as the site may serve as an example for others it would be great if at least all errors from automated tests are resolved.

Expected result

Running a tool such as the WAVE plugin on Chrome shows no errors.

Actual res

Describe the bug
Currently @duetds/date-picker does not work with Rollup (or I didn't get it to).
The problem appears to be a dynamic import statement with a template string:

return import(`./${bundleId}.entry.js${""}`);

Rollup seems to ignore these imports: "Dynamic imports on runtime are ignored by Rollup #2463"

**To

Take a look that I set clearable to true, so I'm not able open picker by clicking on clock ions in input top-right.

Let's have some hide-picker prop?

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

There is no documentation in the user guide or commands quick reference, for the context sensitive help feature, available on F1.

As a result, most users do not likely know about it.

Describe the solution you'd like

While I know it is not yet available in every dialog, or for every control; and it does have some bro