I made an open-source toolkit for developing with HTML, CSS, and JS. I started it because I wanted to speed up my workflow and make myself more productive. Then I realized that I want to share it with the world. I’m thinking about creating documentation that includes our guiding principles and techniques used to build and maintain the project.
You can see our collection of prebuilt components here:
I had a look at some of your components and was disappointed to discover they are not keyboard accessible. Do you have plans to improve accessibility of these components?
Outline is important for basic accessibility, meaning people who must navigate a page using only a keyboard due to various medical conditions. It also helps people who choose to navigate pages using only their keyboard, which is popular but not as important as taking considerations for people who have no other option. It’s ok to set outline to 0 in cases where you take special care in recreating a focus event so that you know where you’re currently selected.
aria-* attributes are also important for screenreaders and other assistive technology.