4 ms·
How thoroughly do you test all of your components? For example, do you always test keyboard navigation when making changes to the styling of your components tha
by subsection1h 6y ago
How thoroughly do you test all of your components? For example, do you always test keyboard navigation when making changes to the styling of your components that might conflict with keyboard navigation?
The reason I'm asking is because I've used or evaluated dozens of CSS frameworks and React component libraries, including custom solutions developed by the companies I've worked for, and none of these solutions are as well-tested at Bootstrap. And one example of the issues I've encountered with these other solutions is bugs relating to keyboard navigation (e.g., Ant Design and Semantic UI were two of the worst offenders the last time I evaluated them).
For many developers nowadays who grew up with touch-based UIs and can't touch type, keyboard navigation might seem like an odd thing to focus on. But I've found that checking if CSS frameworks and React component libraries fully support keyboard navigation is a quick way to evaluate them, like how David Lee Roth evaluated concert promoters by asking them to remove brown M&Ms.
And if the teams that made Ant Design, Semantic UI, etc. can't adequately test their components, how capable is the average developer of creating their own well-tested CSS framework?
- ogre_codes 6y agoYou make one of the best arguments for Bootstrap. In general, my philosophy on components is: Don't reinvent the wheel. Whenever possible, I try to extend stock components rather than create something new. If you use a select instead of making some react-based div-popper thing, accessibility is included. It can be tougher to tweak them to look the way you want, but you don't have to worry as much about what a screen-reader is going to do with it, etc. Totally agree about how bad some sites are with regards to accessibility.