Now a little piece of criticism - aren't there already a dozen UI kits out there with all of these good traits (accessibility and so on), and with a gazillion components? As a tutorial it does sound good and I can see its valuable, however sometimes in "Dev Land" it seems we're eternally reinventing wheels that have been built a hundred times before.
Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
If you can link to a UI kit that is actually accessible that would be amazing!
I have yet to find one that doesn’t fail almost instantly and it has been a constant frustration of mine!
But if it is just that I have been unlucky then that will save me a tonne of work and would really be appreciated!
That is the main motivation behind the series, trying to find something that I can use in a project and know it is accessible from the start (and doesn’t have just 8 components as that seems to be the trend with things that are actually accessible 😜🤣)
The bit to criticise from reinventing the wheel perspective is the fact that all this writing is leading to a CMS....like those don't already exist in spades! 🤣
Hey wow really? You might be onto something then, the first UI framework with accessibility in mind, amazing! Really surprises me that none of these "great" frameworks got that right. Go for it, it might be a hit!
Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
Certainly won't be the first, but the aim is to be more complete than other accessible frameworks (you either have popular and complete but not accessible or accessible and incomplete it seems lol!) as most of them are very limited (it is like people only build 8-10 components then run out of ideas so you can never build a whole application from them!).
Who knows it may become the next big thing, or it may just end up as a pet project and something only I use! 🤣
Just because there is something, does not mean making another one is a bad idea. At least thats how I look at world where I can choose what I eat, drive, drink, watch, read, etc.
That's true, but if there are already 2 dozen other options then I wanna know what's the difference. But the author explained that none of the existing frameworks really got accessibility right, so there he has a point and I do see the added value then.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Now a little piece of criticism - aren't there already a dozen UI kits out there with all of these good traits (accessibility and so on), and with a gazillion components? As a tutorial it does sound good and I can see its valuable, however sometimes in "Dev Land" it seems we're eternally reinventing wheels that have been built a hundred times before.
If you can link to a UI kit that is actually accessible that would be amazing!
I have yet to find one that doesn’t fail almost instantly and it has been a constant frustration of mine!
But if it is just that I have been unlucky then that will save me a tonne of work and would really be appreciated!
That is the main motivation behind the series, trying to find something that I can use in a project and know it is accessible from the start (and doesn’t have just 8 components as that seems to be the trend with things that are actually accessible 😜🤣)
The bit to criticise from reinventing the wheel perspective is the fact that all this writing is leading to a CMS....like those don't already exist in spades! 🤣
Hey wow really? You might be onto something then, the first UI framework with accessibility in mind, amazing! Really surprises me that none of these "great" frameworks got that right. Go for it, it might be a hit!
Certainly won't be the first, but the aim is to be more complete than other accessible frameworks (you either have popular and complete but not accessible or accessible and incomplete it seems lol!) as most of them are very limited (it is like people only build 8-10 components then run out of ideas so you can never build a whole application from them!).
Who knows it may become the next big thing, or it may just end up as a pet project and something only I use! 🤣
Just because there is something, does not mean making another one is a bad idea. At least thats how I look at world where I can choose what I eat, drive, drink, watch, read, etc.
That's true, but if there are already 2 dozen other options then I wanna know what's the difference. But the author explained that none of the existing frameworks really got accessibility right, so there he has a point and I do see the added value then.