Christian:
As you say, it would be better to make stronger release team a11y
requirements. I think it would be easier to define such requirements
once accessibility is working reasonably in GNOME 3. We have made a
lot of progress already, so hopefully this will not be so far in the
future.
cd
Bill:
On 01/ 6/12 07:24 PM, Bill Cox wrote:
I agree that the Gnome Foundation gives a11y high priority. My main
issues in the past have been that the GTK+ team gives it zero
priority, at least when a bug is reported by the community.
Padraig O'Briain was the fellow at Sun
who did a great de
Hi, Alejnandro. GdkPixbuf is used in cell renderers, which draw cells
in tables, lists, and trees. They are used as GUI objects, even if
they were not originally intended to be. They are displayed by many
programs, usually as status indicators in lists, such as stars for
popularity, green check
On 01/07/2012 03:26 PM, Christian Hofstader wrote:
>> cox: In my opinion, the separation of responsibilities is the main reason
>> for lack of a11y progress in GTK. If any of the wonderful people
>> working on a11y that we are both fans of were able to commit patches
>> to GTK, the issues would h
On 01/06/2012 04:55 PM, Christian Hofstader wrote:
> "Sometimes accessibility lags behind…" is an accurate statement. My question
> is why Gnome Foundation would consider a11y issues to have a priority lower
> than any other feature of the software. By permitting a11y to "lag behind"
> other fe
Sorry, Benjamin. I'll try to keep it straight. Here's the problem
with pixbuf that makes solving this issue hard without adding an
accessible description directly to pixbuf. GTK does not build widgets
for cells in lists, tables, and trees. Instead, you register a
callback function that is respo
- Mensaje original -
> De: Jason White
>
> I think the Gnome accessibility community has a good grasp of the technical
> issues that have to be addressed, including the lack of appropriate
> documentation for desktop and application developers as to how to implement
> accessibility int
On Sun, Jan 8, 2012 at 3:45 AM, Bill Cox wrote:
> I've read that you are doing a lot of code enhancements for a11y
You're thinking of a different Benjamin - Benjamin Otte.
--
Benjamin Hawkes-Lewis
___
gnome-accessibility-list mailing list
gnome-accessi
I just read what I wrote, and I sound like an ass hole. Well,
sometimes I am. I've read that you are doing a lot of code
enhancements for a11y, and that makes want to be your friend. I spend
less than 1 percent of my time on how to get GTK objects to talk.
When I say please prove me wrong, what
If the GtkCellRendererPixBuf class werer allowed to have an accessible
text description, that would be great. However, most of the code I've
looked at builds pixbuf objects and later on the calls to
GtkCellRendererPixBuf are non-aware of exactly which pixmap is being
drawn. If you feel that addin
On 1/7/12, Mats Lundälv wrote:
> The main show-stopper for suggesting free systems
> in general, including Gnome based systems, is the lack of easily available
> and well functioning TTS reading support for seing users with a reading
> imparment - the by far largest area of a11y needs.
I happen t
Christian Hofstader wrote:
> cdh: The Gnome a11y issues for people with vision impairment in the 2.xx
> releases are many, especially when compared to what users enjoy with JAWS or
> VoiceOver. These issues, though, are not all based in Gnome itself, rather,
> across the ecosystem of OS, UI, app,
On Sat, Jan 7, 2012 at 1:24 AM, Bill Cox wrote:
> Because several e-mails on this topic have attacked my emotional
> response to my patch to pixmap objects being rejected, I want to
> explain my philosophy about GUI objects and a11y. If an object is
> going to be displayed on the screen, I feel e
Hi, I'd just want to express my opinion about this being a very important discussion, and to reinforce what Christian says about the problem with promoting free systems with major a11y shortcomings for public use. Here we hear about the remaining difficulties for VI screenreader users, though this
>
> cox: In my opinion, the separation of responsibilities is the main reason
> for lack of a11y progress in GTK. If any of the wonderful people
> working on a11y that we are both fans of were able to commit patches
> to GTK, the issues would have been resolved years ago.
>
cdh: Can Brian or so
>
> As you say, it would be better to make stronger release team a11y
> requirements. I think it would be easier to define such requirements
> once accessibility is working reasonably in GNOME 3. We have made a
> lot of progress already, so hopefully this will not be so far in the
> future.
>
c
Hi, Chris. One of the reasons I often make an ass of myself, other
than having no clue about human emotions, is I write emails like this
after drinking on Friday night. So...
I agree that the Gnome Foundation gives a11y high priority. My main
issues in the past have been that the GTK+ team give
Christian:
On 01/ 6/12 09:55 AM, Christian Hofstader wrote:
"Sometimes accessibility lags behind…" is an accurate statement. My
question is why Gnome Foundation would consider a11y issues to have a
priority lower than any other feature of the software. By permitting
a11y to "lag behind" other
"Sometimes accessibility lags behind…" is an accurate statement. My question
is why Gnome Foundation would consider a11y issues to have a priority lower
than any other feature of the software. By permitting a11y to "lag behind"
other features, it is effectively put on the back burner and will r
Bill:
On 12/25/11 12:11 AM, Bill Cox wrote:
Since you bring it up, let's talk about it. There has not been a
single accessibility bug reported by the community that was closed by
the GTK+ team in two years. The calender doesn't talk, and neither do
most images, regardless of the dedication of
Bill:
It is important to raise visibility for certain accessibility issues
that are causing real users problems. I really do understand how
frustrating it can be when software just does not work properly. This
clearly creates very serious issues for users who depend on features
like accessibil
On Sun, Dec 25, 2011 at 6:11 AM, Bill Cox wrote:
> Since you bring it up, let's talk about it. There has not been a
> single accessibility bug reported by the community that was closed by
> the GTK+ team in two years. The calender doesn't talk, and neither do
> most images, regardless of the ded
Bill, the money will be spend in accessibility works, so
What's the problem ? Don't you trust in the accessibility
team ?
And yes, there are lot of bugs opened. The resources
are also limited and GTK has being involved in big changes
from version 2 to version 3 with big time constraints.
And, as
Bill Cox wrote:
> Since you bring it up, let's talk about it. There has not been a
> single accessibility bug reported by the community that was closed by
> the GTK+ team in two years. The calender doesn't talk, and neither do
> most images, regardless of the dedication of the original programme
Since you bring it up, let's talk about it. There has not been a
single accessibility bug reported by the community that was closed by
the GTK+ team in two years. The calender doesn't talk, and neither do
most images, regardless of the dedication of the original programmer.
I submit but reports w
Bill Cox wrote:
> So, how do we separate the groups that deserve accessibility funding
> under Gnome from those who seem hell bent on making life painful for
> the blind?
I don't think this is either a helpful or productive question to ask, and I
doubt very much that there are people associated
First of all, I'm a huge fan of people like Mike Gorse and Joanmarie.
These people have undertaken the task of helping people like me
without the motivation of losing their own vision. These are the
people who I will go to bat for to help fund, to the extent that my
limited abilities allow. On th
Awesome news!
2011/12/16 Juanjo Marín
>
> Friday 16th dec, the GNOME Foundation announces a fundraising campaign [1]
> to kick off 2012 as the Year of Accessibility for GNOME.
>
> GNOME has held accessibility amongst its core values from the project’s
> inception. Because of this commitment, alo
On Sat, 17 Dec 2011, Joanmarie Diggs wrote:
Pixmaps should have accessible descriptions. The calendar should talk.
Bugs should be filed. Developers should be pinged.
Bill did file a bug for the first issue at least, if I'm remembering
correctly. I suspect that part of the issue is that, i
Hey Bill.
On 12/16/2011 09:56 PM, Bill Cox wrote:
I'd feel a lot better pushing gnome accessibility if GTK+ wasn't such
a complete lost cause in terms of accessibility improvement.
I don't think this is a fair assessment. There has been a lot of
investment in improving Gtk+ Accessibility, inc
I'd feel a lot better pushing gnome accessibility if GTK+ wasn't such
a complete lost cause in terms of accessibility improvement. Pixmaps
should have accessible descriptions. The calendar should talk.
Someone somewhere in GTK+ land should care, and I just don't see it.
I recommend channeling the
Friday 16th dec, the GNOME Foundation announces a fundraising campaign [1] to
kick off 2012 as the Year of Accessibility for GNOME.
GNOME has held accessibility amongst its core values from the project’s
inception. Because of this commitment, along with the efforts of many dedicated
developers
32 matches
Mail list logo
