[kde-guidelines] [Kde-accessibility] Custom controls (was Discouraging use of custom widget replacements)

[Frederik Gladhorn]

Hello,

On Wednesday 10. July 2013 10.50.25 Thomas Pfeiffer wrote:
> On 10.07.2013 10:19, Olaf Schmidt-Wischhöfer wrote:
> > Hi,
> > 
> > I am cc'ing the accessibility list, because custom controls are a huge
> > accessibility problem unless proper support for the accessibility classes
> > is implemented.
> > 
> > It would be necessary to include both a big warning and contact points for
> > providing accessibility information.
> 
> I'd suggest to ask people to not only consult the usability team but
> also the the accessibility team when defining a new widget. That would
> probably work better than trying to include all a11y stuff into the
> guidelines themselves.
> Do you think that would work?

I think we need more documentation how to make accessibility work for custom 
widgets. I do think that the topic is big enough to have it's own pages - either on 
KDE wikis or preferably right in the Qt documentation.
Then link to it in the usability guides.

Adding a11y to Dolphin's ItemViewsNG took quite some time and effort, but is also 
a really complex task. I hope that for most widgets the authors will get away with a 
couple of lines of code. It would be good to get feedback on where docs are missing.

Frederik

> _______________________________________________
> kde-accessibility mailing list
> kde-accessibility at kde.org
> https://mail.kde.org/mailman/listinfo/kde-accessibility
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-guidelines/attachments/20130715/6f5182e2/attachment.html>