-
Updated
Mar 6, 2021 - TypeScript
a11y
Here are 797 public repositories matching this topic...
-
Updated
Mar 6, 2021 - JavaScript
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
This is just a small quality-of-life improvement. Instead of having SerialVirtualNode default to nodeType 1, it would be good if it could determine the nodeType based on what it is passed:
new SerialVirtualNode({ nodeName: '#cdata-section' }).props.nodeType // 2
new SerialVirtualNode({ nodeName: '#text' }).props.nodeType // 3
new SerialVirtualNode({ nodeName: '#comment' }).props.nodeTySummary
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
Currently the webhint codebase doesn't follow its own best practice of using importHelpers: true to reduce the amount of redundant helper code generated by TypeScript (also requires adding tslib as a dependency). This causes unnecessary bloat in the built webhint code, particularly for large bundles like the bro
-
Updated
Mar 2, 2021 - JavaScript
-
Updated
Mar 6, 2021 - JavaScript
-
Updated
Jan 27, 2020 - JavaScript
-
Updated
Feb 24, 2021
-
Updated
Mar 6, 2021 - JavaScript
-
Updated
Feb 17, 2021 - JavaScript
-
Updated
Mar 2, 2021 - TypeScript
-
Updated
Feb 18, 2021 - Swift
-
Updated
Jan 29, 2021 - Less
-
Updated
Dec 11, 2020 - JavaScript
-
Updated
Dec 11, 2020 - JavaScript
-
Updated
Jan 6, 2021 - JavaScript
-
Updated
Dec 10, 2020 - SCSS
-
Updated
Jan 8, 2021 - HTML
-
Updated
Aug 24, 2020 - CSS
-
Updated
Feb 22, 2021
-
Updated
Jan 13, 2021 - JavaScript
Something must have changed in Chrome because the CSS asterisk is no longer positioned appropriately.
checking firefox, it still is positioned as intended.
Further investigation necessary.
Improve this page
Add a description, image, and links to the a11y topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the a11y topic, visit your repo's landing page and select "manage topics."
Expected Behavior
The documentation for formField should include an entry for
formField.error.size.Actual Behavior
There is no documentation for the theme field
formField.error.sizeeven though it appears to work.