aria-practices
content
aria-practices | content | |
---|---|---|
4 | 123 | |
1,161 | 8,867 | |
1.1% | 2.7% | |
8.0 | 10.0 | |
1 day ago | about 1 hour ago | |
HTML | Markdown | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
aria-practices
-
Here are the 10 projects I am contributing to over the next 6 months. Share yours
W3C Aria Practices
-
React Arborist – A full-featured tree component for React
I should apologize off-the-bat for not digging in too deeply, but how does this handle keyboard and screenreader accessibility?
W3C has some in-depth list of expected keyboard interactions, though I'm not sure how complete they are:
https://w3c.github.io/aria-practices/#TreeView
https://w3c.github.io/aria-practices/examples/treeview/treev...
I ask because I've tried to implement a [TreeGrid](https://w3c.github.io/aria-practices/#treegrid) myself before and... it's a lot of work. I'd love an accessible, keyboard-friendly React tree :).
-
Custom JavaScript controls can't capture the nuance of form fields (2021)
Yep I totally agree with this.
There are however a bunch of ARIA tags & best practices etc (https://w3c.github.io/aria-practices/) that exist to make popups and dialogs (and other things e.g. tree views or "email-inbox-style" "treegrids" etc) accessible (if implemented correctly).
I am conflicted about these - it is nice that there are ARIA tags for this, but it would also be nice if browsers "understood" aria tags and added some default behaviors (e.g. keyboard navigation). As it is, ARIA tags are essentially "pointless" to anyone who doesn't use an assistive technology, and so non-assitive-technology users nor developers benefit from using ARIA tags so they are often forgotten. If the browsers saw that there was an A11y-tree that matched a treeview or a treegrid, it would be really really nice if they applied some default common keyboard navigation implementation, rather than do nothing and leave it up to the developer to decide what keys do what on each and every site. .... Or on the other hand, is that too prescriptive and should we give developers and UX designers more leeway to design something better, rather than rely on browser-enforced defaults? I guess we are happy with browser defaults for basic inputs, but would we be for a treegrid?
-
4 takeaways from axe-con 2021
The ARIA practices GitHub is a good resource to see where certain patterns fall short.
content
-
Here are the 10 projects I am contributing to over the next 6 months. Share yours
MDN Web Docs content
-
The character encoding cheat sheet for JS developers
In this article, we've covered the basics of character encoding in JavaScript, including the different encoding standards, how they work, and how to work with them in Node.js and web browsers. We've also covered some best practices for working with character encoding in JavaScript and provided tips and techniques for debugging encoding issues. If you want to learn more about character encoding in JavaScript, there are several resources. The Unicode Consortium's website provides detailed information about the Unicode standard, while the Mozilla Developer Network has extensive documentation on character encoding in JavaScript. Additionally, there are several books on JavaScript that cover this topic in depth, such as "JavaScript: The Definitive Guide" by David Flanagan and "Eloquent JavaScript" by Marijn Haverbeke.
-
Explanation of CSS Gradients
Great job! You've learned all about gradients and now you can use them like a CSS expert. With these skills, you can make your websites more colorful and attractive. you can read more in MDN website.
-
10 JavaScript Sites Every Web Developer Should Know
(https://developer.mozilla.org/) MDN Web Docs is the go-to resource for comprehensive documentation on JavaScript. From beginner tutorials to advanced references, it covers everything you need to know about JavaScript, including syntax, methods, and APIs.
-
10 Websites Every Web Developer Should Bookmark
(https://developer.mozilla.org/) This is your official guide to all things web development, straight from the team behind the popular Firefox browser. MDN boasts comprehensive documentation on HTML, CSS, JavaScript, and web APIs, making it an invaluable reference for developers of all levels.
-
Developer should-know websites
MDN Web Docs, previously Mozilla Developer Network
-
🔥 Top 10 Best Websites to Learn Coding for Free! 💻
MDN Web Docs MDN Web Docs is an invaluable resource for web developers. From basic syntax to advanced concepts, you'll find comprehensive documentation on HTML, CSS, JavaScript, and more.
-
Next.js: consequence of AppRouter on your CSP
Nonce attribute from MDN
-
Web Development Tools and Resources
MDN Web Docs (Visit Site)
-
Symbiote.js 2.0
In Symbiote.js, almost everything you see should already be familiar to you, directly or indirectly. Unless you're new to frontend. And if you are a beginner, then you can learn the necessary basics on popular sites with documentation on modern specifications, for example MDN.
What are some alternatives?
react-arborist - The complete tree view component for React
Propeller - Propeller - Develop more, Code less. Propeller is a front-end responsive framework based on Google's Material Design Standards & Bootstrap.
react-table-library - :bento: React Table Library
sorbet - A fast, powerful type checker designed for Ruby
bootstrap-select - :rocket: The jQuery plugin that brings select elements into the 21st century with intuitive multiselection, searching, and much more.
synth - The Declarative Data Generator
standards-support - Contains documentation for Vispero software support of Web standards
proposal-pipeline-operator - A proposal for adding a useful pipe operator to JavaScript.
monaco-tree - Curiosity hacks with Monaco Editor's tree component
big-list-of-naughty-strings - The Big List of Naughty Strings is a list of strings which have a high probability of causing issues when used as user-input data.
aktenkoffer - 💼 Personal document management made easy.
eslint-plugin-no-unsanitized - Custom ESLint rule to disallows unsafe innerHTML, outerHTML, insertAdjacentHTML and alike