4 ms·
Esc is handled automatically by the suggested replacement <dialog>, although only Chrome has implemented <dialog> so far. With respect to Tab, doesn't that pro
by comex 10y ago
Esc is handled automatically by the suggested replacement <dialog>, although only Chrome has implemented <dialog> so far.
With respect to Tab, doesn't that problem already exist in all other (non-dialog) web content? If a webpage's dialogs are accessible but everything else is broken, I feel like you're going to have a bad time regardless… Though I suppose that if you're not impaired and typically use the mouse to click buttons, but are used to using the keyboard for dialogs, this could be an annoyance.
- mschuster91 10y agoThe problem is most people will skip over the "make it feel really native" part, except when they're forced by law (ADA comes to my mind). It costs a lot to implement right across browsers and even more to properly test. To make it worse: Windoes has different native UI than OS X, and on linux it entirely depends on the desktop environment and window manager - there is no way to "get it native" there, so it is a loss of consistency. Oh, and JS cr.p also does not know about stuff like OS color schemes, DPI settings, OS-level-set hotkeys etc., so all this will be lost.