Accessibility is a very real advantage of Qt solutions.<div><br></div><div><a href="http://doc.qt.io/qt-5/accessible.html">http://doc.qt.io/qt-5/accessible.html</a></div><div><br></div><div>"""</div><div>[...]</div><div><div>applications usable for people with different abilities. It is important to take different people's needs into account, for example, in case of low vision, hearing, dexterity, or cognitive problems. Some examples of accessibility measures are keyboard shortcuts, a high-contrast user interface that uses specially selected colors and fonts, or support for assistive tools such as screen readers and braille displays.</div><div><br></div><div>A basic checklist that any application should aim for:</div><div><br></div><div>- Usability - Usability and user centric design generally lead to more usable applications, including improvements for people with various abilities.</div><div>- Fonts - Font settings should follow the system/platform. This allows users to select fonts for readability and increasing the font size.</div><div>- Colors - Provide enough contrast and consider the most common cases of low vision and color blindness. Make sure that the application is usable, for example, for people with red/green blindness, and don't depend on colors only.</div><div>- Scalable UI - A user interface that works in various sizes and properly supports different fonts and accommodates size changes.</div><div>- Sounds - Do not exclusively rely on sound notifications, provide a visual alternative when a sound signal is imperative to using the application.</div><div>- Spelling - Offer spell checking wherever it makes sense, even when only a single word is expected.</div><div>- Assistive Technology - Support the use of assistive tools (AT). Either use standard widgets/controls which support ATs out of the box, or make sure that your custom widgets and controls support accessibility properly. </div><div>"""</div><div><br></div><div>Does anyone have any experience with building accessible native GUI apps with something other than Qt?</div><div><br></div><div><br></div><div>Most of this a11y (accessibility) information is focused on web apps (that don't need an installer/updater to quickly respond to security issues): <a href="https://github.com/brunopulis/awesome-a11y">https://github.com/brunopulis/awesome-a11y</a></div><br>On Friday, August 24, 2018, Chris Barker via Python-ideas <<a href="mailto:python-ideas@python.org">python-ideas@python.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Aug 24, 2018 at 8:17 AM, Barry Scott <span dir="ltr"><<a href="mailto:barry@barrys-emacs.org" target="_blank">barry@barrys-emacs.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>> A graphical "hello world" in QT is only half a dozen or less lines of<br>
> code in total, so<br>
> meets the simplicity requirement.<br>
<br>
</span>I think 2 lines is simple, 12 is not really simple, is it?<br></blockquote><div><br></div><div>well, if all you need is a single dialog box with one or two entry fields, then yes, 2-4 lines is better than 12-14 lines -- but a lot.</div><div><br></div><div>But if you are building an actual application, I'm not sure that the extra ten lines of startup code matters at all. And if those ten lines are essentially boilerplate that you can copy and paste from somewhere (Or have a gui-builder write for you), then even less so.</div><div><br></div><div>That's not to say that the GUI toolkit slike wxPython, PySide, pyGTK aren't a bit more complex than they need to be, but much of that complex is there to support complex needs.</div><div><br></div><div>I do think there is a place for tools that make "the easy stuff easy", but make sure that the complex stuff is still possible.</div><div><br></div><div>-CHB</div><div><br></div></div>-- <br><div data-smartmail="gmail_signature"><br>Christopher Barker, Ph.D.<br>Oceanographer<br><br>Emergency Response Division<br>NOAA/NOS/OR&R (206) 526-6959 voice<br>7600 Sand Point Way NE (206) 526-6329 fax<br>Seattle, WA 98115 (206) 526-6317 main reception<br><br><a href="mailto:Chris.Barker@noaa.gov" target="_blank">Chris.Barker@noaa.gov</a></div>
</div></div>
</blockquote></div>