Products · Broad category
Immediate mode GUI
Raised as a usability problem by 7 people on Hacker News over 8 years (2019–2026), in 5 threads.
This is a broad category rather than one product, so its issues aren't ranked on the home page.
No issue was raised by at least 3 people in 3 threads this year.
No issue was raised by at least 3 people in 3 threads in the last 5 years.
Every issue, all time, most people first
Text drawn to canvas is inaccessible to screen readersUnreviewed
20192026- Screen readers and input methods can't interact with text in immediate-mode GUIs2026-02-13
- Screen readers cannot read canvas-drawn interfaces, only a bitmap2021-02-14
- Immediate mode GUIs draw text to canvas, so screen readers cannot access it2019-04-25
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 7 complaints
- Screen readers and input methods can't interact with text in immediate-mode GUIs2026-02-13
- Huge event loop is hard to split and organize, making code hard to follow2024-01-16
- Apps built on non-native toolkits behave weirdly and perform worse for users2024-01-16
- Text looks poorly rendered on high-DPI screens, making the interface uncomfortable to use2022-12-23
- Screen readers cannot read canvas-drawn interfaces, only a bitmap2021-02-14
- Developers must manually store and retrieve state per component, which is hard to reuse2019-04-25
- Immediate mode GUIs draw text to canvas, so screen readers cannot access it2019-04-25