On Thu, Feb 10, 2011 at 4:39 AM, Ted Gould t...@ubuntu.com wrote:
1. Expert screenreader users will, if they can, save time by listening
to only the first part of an item's label before navigating
elsewhere. So an accessible label may put variable information
first (for example, 22
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aaron J. Seigo wrote on 03/03/11 19:53:
On Thursday, March 3, 2011, Matthew Paul Thomas wrote:
Aaron J. Seigo wrote on 03/03/11 06:15:
On Tuesday, March 1, 2011, Matthew Paul Thomas wrote:
...
But in general, while all interactive graphic-only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aaron J. Seigo wrote on 03/03/11 06:15:
On Tuesday, March 1, 2011, Matthew Paul Thomas wrote:
...
But in general, while all interactive graphic-only
elements should have accessible labels, not all of them need tooltips.
example?
Icon-only
On Thursday, March 3, 2011, Matthew Paul Thomas wrote:
Aaron J. Seigo wrote on 03/03/11 06:15:
On Tuesday, March 1, 2011, Matthew Paul Thomas wrote:
...
But in general, while all interactive graphic-only
elements should have accessible labels, not all of them need tooltips.
example?
On Tuesday, March 1, 2011, Matthew Paul Thomas wrote:
I understand that it's suboptimal (though thanks, Matthew for laying it
out in greater detail), my reservation was that many developers simply
don't care about accessibility enough to add another string, so it
probable makes sense if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sebastian Kügler wrote on 10/02/11 17:22:
On Thursday, February 10, 2011 05:39:08 Ted Gould wrote:
...
I forwarded the discussion that was had about using the title in the
tooltip for the accessible label. While I felt that it was not
adequate I
On Thursday, February 10, 2011 05:39:08 Ted Gould wrote:
Plasma folks,
I forwarded the discussion that was had about using the title in the
tooltip for the accessible label. While I felt that it was not adequate
I couldn't express why. As per usual, mpt says it better than I, here
is
On Thursday 10 February 2011, Sebastian Kügler wrote:
On Thursday, February 10, 2011 05:39:08 Ted Gould wrote:
Plasma folks,
I forwarded the discussion that was had about using the title in the
tooltip for the accessible label. While I felt that it was not adequate
I couldn't
Plasma folks,
I forwarded the discussion that was had about using the title in the
tooltip for the accessible label. While I felt that it was not adequate
I couldn't express why. As per usual, mpt says it better than I, here
is his response:
Forwarded Message
From: Matthew
(resending, cc'ing Ted)
What would help is if the tooltip was using semantic markup, instead of a
subset of html. Think about something like this:
tooltip
titleAmarok/title
icon src=amarok.png alt=Amarok/
bodyCurrently playing: Qt 4 dance by Trolltech/body
/tooltip
On Thursday, February 3, 2011, Aurélien Gâteau wrote:
There are ways to strongly suggest application developers to define such
strings: for example outputing warnings on stderr when a KSNI goes live
without having proper a11y properties set.
catching and punishing sins (though a warning
Yeah, in talking to the a11y folks they like tooltips, but they really
wanted another label as sometimes the tooltips don't describe the icon
enough for a blind user to know what it means.
this is true for traditional tooltips, but the ones in a SNI are not like
those tooltips at all:
On Monday 07 February 2011, Aurélien Gâteau wrote:
Yeah, in talking to the a11y folks they like tooltips, but they really
wanted another label as sometimes the tooltips don't describe the icon
enough for a blind user to know what it means.
this is true for traditional tooltips, but
On Monday 07 February 2011, Aurélien Gâteau wrote:
On Thursday, February 3, 2011, Aurélien Gâteau wrote:
There are ways to strongly suggest application developers to define
such strings: for example outputing warnings on stderr when a KSNI
goes live without having proper a11y properties
What would help is if the tooltip was using semantic markup, instead of a
subset of html. Think about something like this:
tooltip
titleAmarok/title
icon src=amarok.png alt=Amarok/
bodyCurrently playing: Qt 4 dance by Trolltech/body
/tooltip
With such a format, it
On Monday, February 7, 2011, Aurélien Gâteau wrote:
On Thursday, February 3, 2011, Aurélien Gâteau wrote:
There are ways to strongly suggest application developers to define
such strings: for example outputing warnings on stderr when a KSNI
goes live without having proper a11y
On Monday, February 7, 2011, Aurélien Gâteau wrote:
What would help is if the tooltip was using semantic markup, instead of
a subset of html. Think about something like this:
tooltip
titleAmarok/title
icon src=amarok.png alt=Amarok/
bodyCurrently playing: Qt 4 dance
On Thursday 03 February 2011, Ted Gould wrote:
Hello,
For an intro see the mail with the (0/3) in the subject line.
One of the projects we're doing is to try and make Unity more
accessible. To that end we'd like to add properties to add accessible
labels for the icons that could be given
On Thu, 2011-02-03 at 14:37 +0100, Marco Martin wrote:
On Thursday 03 February 2011, Ted Gould wrote:
One of the projects we're doing is to try and make Unity more
accessible. To that end we'd like to add properties to add accessible
labels for the icons that could be given to screen
Hey,
On Thursday, February 03, 2011 15:29:38 Ted Gould wrote:
On Thu, 2011-02-03 at 14:37 +0100, Marco Martin wrote:
On Thursday 03 February 2011, Ted Gould wrote:
One of the projects we're doing is to try and make Unity more
accessible. To that end we'd like to add properties to add
On the other hand, it requires application developers to add another string
in their code to all UI elements -- something which might be easily forgotten
by those that don't care a lot about a11y (I fear that this applies to a lot
of developers). Falling back to the tooltip sounds like
first, thanks for working with us on this Ted. it really helps keep things
moving forward in a coordinate fashion, and makes our lives (and hopefully
yours) a lot brighter. :)
oh, and you don't need to CC Marco and I, we're on the plasma-devel list :)
On Wednesday, February 2, 2011, Ted Gould
On Thursday, February 3, 2011, Aurélien Gâteau wrote:
There are ways to strongly suggest application developers to define such
strings: for example outputing warnings on stderr when a KSNI goes live
without having proper a11y properties set.
catching and punishing sins (though a warning is
On Thursday, February 3, 2011, Sebastian Kügler wrote:
On the other hand, it requires application developers to add another string
in their code to all UI elements -- something which might be easily
forgotten by those that don't care a lot about a11y (I fear that this
applies to a lot of
On Thursday, February 3, 2011, Ted Gould wrote:
On Thu, 2011-02-03 at 14:37 +0100, Marco Martin wrote:
On Thursday 03 February 2011, Ted Gould wrote:
One of the projects we're doing is to try and make Unity more
accessible. To that end we'd like to add properties to add accessible
On Thu, 2011-02-03 at 16:24 +0100, Sebastian Kügler wrote:
On the other hand, it requires application developers to add another
string in their code to all UI elements -- something which might be
easily forgotten by those that don't care a lot about a11y (I fear
that this applies to a lot of
26 matches
Mail list logo
