Productivity · Developers · Stable
Inadequate built-in UI controls lead to poor user experience and accessibility issues
Users struggle with non-extensible built-in controls that are not user-friendly and often fail to meet accessibility standards.
Who experiences it: Developers
Momentum
0%
Pain
85
Competition
90
Opportunity
66/100
Signals over time
5 observed signals across 1 sources, tracked for 48 days. Confidence: medium.
What people are saying Observed
“Yes, yes they do. WXDragon for Rust, for example, provides quite good accessibility. And maybe accessibility would be better for frameworks like QT or DearImGUI if (1) people didn't act like the web was some paragon of accessibility (hint: it really, really isn't, not when websites misuse web APIs -- which happens quite frequently) and (2) UI framework developers didn't just make a UI framework that looked sexy but left accessibility on the floor. What's oddly being ignored in this entire thread (so far, as of the time of writing) is that back in 2017-2018 Discord was an Electron app and was completely inaccessible. The web did not magically bring accessibility to the table -- we disabled people had to go yell at Discord to fix their shit, and even then it took them like 2-3 years, and even now Discord has some very very weird accessibility issues that will randomly crop up here and there.”
Hacker News · frustration
“You just don't get it, do you? What I'm saying is that your approach can _never_ lead to a good UI toolkit. You've made a funny toy that renders three boxes that can never work in the real world. Not only is your frame time in the milliseconds on a browser (on a 5080 too), you've made a toy prototype that covers 1% of the necessary features, claimed that it's entirely complete and declared yourself winner (and that implementing the rest would have zero impact on that performance, lol) It's now been three times you ignore the reality of the world, loudly proclaim yourself winner then proceed to drop 90% of what is necessary. No shit, you can draw empty boxes in 2ms and badly shape text in 3. >I would love to hear how handling taps, adding a mobile-friendly layout to the demo, handling selection or accessibility would change the calculus on that. Because now for half of these, you are involving the CPU again, with endless back and forths. Keep repeating it until you have something that works and congratulations, you have more or less exactly what browsers do today. Considering the hubris, the loud proclamations that you're right and that the whol”
Hacker News · frustration
“> Built-in things aren't extensible - there's no way to have a number type input that doesn't suck without doing it yourself, and then you need to opt into extra song and dance for your element to participate in form submission data. This is the bane of every UI out there. "I hate the inbuilt controls so I'm going to write something better that doesn't look terrible!". Then they build some half-arsed thing that doesn't do accessibility right and only works properly on an up-to-date Chrome-based browser in a US locale with javascript enabled. The built-in controls should always be used, not because they look pretty, but because they work the same across all websites. Users don't have to guess how this site's bespoke time-picker works (and how it doesn't). It won't fail in unexpected ways. It'll deal with your locale's date format so you don't accidentally specify the 5th of June when you meant the 6th of May. Not everything has to be pretty all the time. Functional works, too.”
Hacker News · frustration
“> Built-in things aren't extensible - there's no way to have a number type input that doesn't suck without doing it yourself, and then you need to opt into extra song and dance for your element to participate in form submission data. This is the bane of every UI out there. "I hate the inbuilt controls so I'm going to write something better that doesn't look terrible!". Then they build some half-arsed thing that doesn't do accessibility right and only works properly on an up-to-date Chrome-based browser in a US locale with javascript enabled. The built-in controls should always be used, not because they look pretty, but because they work the same across all websites. Users don't have to guess how this site's bespoke time-picker works (and how it doesn't). It won't fail in unexpected ways. It'll deal with your locale's date format so you don't accidentally specify the 5th of June when you meant the 6th of May. Not everything has to be pretty all the time. Functional works, too.”
Hacker News · frustration
“> Built-in things aren't extensible - there's no way to have a number type input that doesn't suck without doing it yourself, and then you need to opt into extra song and dance for your element to participate in form submission data. This is the bane of every UI out there. "I hate the inbuilt controls so I'm going to write something better that doesn't look terrible!". Then they build some half-arsed thing that doesn't do accessibility right and only works properly on an up-to-date Chrome-based browser in a US locale with javascript enabled. The built-in controls should always be used, not because they look pretty, but because they work the same across all websites. Users don't have to guess how this site's bespoke time-picker works (and how it doesn't). It won't fail in unexpected ways. It'll deal with your locale's date format so you don't accidentally specify the 5th of June when you meant the 6th of May. Not everything has to be pretty all the time. Functional works, too.”
Hacker News · frustration
Why now? AI inference
Existing solutions Observed
- Bootstrap · free · complaints: Limited built-in components for complex UIs, Can lead to a generic look if not customized, Accessibility issues with default components
- Ant Design · free (open source), paid plans for enterprise features · complaints: Complexity can be overwhelming for new users, Customization can be challenging, Accessibility issues with some components
- jQuery UI · free · complaints: Outdated design and components, Limited accessibility features, Performance issues with larger applications
- Foundation · free · complaints: Less popular than Bootstrap, leading to fewer resources, Can be complex for beginners, Accessibility features not always prioritized
- Material-UI · Pro $299 / year / dev · Premium $599 / year / dev · complaints: Steep learning curve for beginners, Performance issues with large applications, Accessibility features can be overlooked
There is a notable gap in the availability of built-in UI controls that prioritize both user experience and accessibility for developers. While competitors like Material-UI, Ant Design, and Bootstrap offer a range of components, they often struggle with accessibility issues and steep learning curves, indicating a need for a solution that combines ease of use with robust accessibility features.
See the full evidence, competitor gap matrix and opportunity report.
Free account. No credit card.