ubuntu-phone team mailing list archive

[Bruno Girin <brunogirin@xxxxxxxxx>]

On 23/02/13 23:28, Mike Sandman wrote:
> Color not with standing, there are many ways to indicate the "bad
> part": italic, underlines...perhaps the squiggly underlines, used in
> most spell-check-as-you-type scenarios. At any rate, my idea was not
> to use color so much as to call attention to part of the input that
> caused the problem.  For example, image if your word processor just
> said "spelling error" at the bottom of the page--not too useful.
>
> However, you do bring up a great point about accessibility.  Using
> your example, let's say a color-blind user has set his theme to
> high-contrast.  How, in QML are we to account for this, other than
> just hope it still looks good.  It would be nice if my widgets would
> behave based on accessibility settings, especially if the framework
> helped me in a way similar to i18n facilities.  How nice would it be
> to be able to provide a set of strategies where the framework chose
> based on accessibility need.  I could build a default indicateError()
> function that changed the text red and beeped, and others that would
> cater to various impairments: 
>
> * no beep for the hearing impaired
> * switch to underline for the color-blind
>
> Anyway, I'm getting off topic.  Again, great work guys on the calc.
> Will be watching the progress!

There are two things you can do:
- use the QML SystemPalette so ensure that you don't hardcode any colour
[1],
- QML can be styled using CSS and a class can be applied using the
ItemStyle object [2]; going forward, the SDK could handle a number of
standard classes to ensure consistent look and feel across apps for
standard use cases like highlighting an error.

[1] http://doc.qt.digia.com/stable/qml-systempalette.html
[2]
http://developer.ubuntu.com/api/ubuntu-12.10/qml/mobile/qml-ubuntu-components0-itemstyle.html

Bruno