-
Updated
Dec 28, 2021 - JavaScript
accessibility
Here are 2,438 public repositories matching this topic...
-
Updated
Jan 5, 2022 - TypeScript
-
Updated
Dec 3, 2021
-
Updated
Oct 30, 2021 - CSS
-
Updated
Jan 5, 2022 - TypeScript
-
Updated
Nov 23, 2021 - C
Examples
Opening this issue in case anyone wants to help. Recently, we've configured Storybook to import files from __examples__ folders inside Reakit component folders. This is how we're doing it:
Thos
-
Updated
Nov 22, 2021 - JavaScript
-
Updated
Dec 2, 2021 - TypeScript
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
-
Updated
Jan 3, 2022 - C#
-
Updated
Jan 5, 2022 - TypeScript
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
-
Updated
Dec 24, 2021 - Python
-
Updated
Dec 13, 2021 - JavaScript
-
Updated
Nov 27, 2021 - JavaScript
-
Updated
Jan 4, 2022 - TypeScript
-
Updated
Dec 3, 2021 - JavaScript
-
Updated
Apr 8, 2021 - JavaScript
-
Updated
Jan 3, 2022 - TypeScript
-
Updated
Jan 3, 2022 - JavaScript
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
-
Updated
Jan 27, 2020 - JavaScript
-
Updated
Dec 14, 2021
-
Updated
Dec 31, 2021 - JavaScript
-
Updated
Jan 4, 2022 - SCSS
-
Updated
Dec 20, 2021 - Java
I report here a warning that has appeared at various places in 2021.3beta2 (not tested the beta1) but was not present in 2021.2.
Maybe introduced by #12925? (Cc @michaelDCurran )
Also Cc @feerrenrut to decide if this issue should be in the 2021.3 milestone or not.
Steps to reproduce:
- Open a setting dialog, e.g. NVDA+control+D (formatting)
- Press space key to modify the state of t
Improve this page
Add a description, image, and links to the accessibility topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the accessibility topic, visit your repo's landing page and select "manage topics."
There are some props that aren't used by stately in ComboBoxProps, which can be confusing for users to know where to pass props: to
useComboBoxStateoruseComboBox.For example:
https://github.com/adobe/react-spectrum/blob/34717616f3a6555d3f4d6739635d3ac347b50a58/packages/%40react-types/combobox/src/index.d.ts#L41-L43
should move to Aria specific props (and also be included in the Spe