and how to approach mapping a bug to the responsible
component, and how to debug each component.
That would probably be a useful topic too, if we can find time somewhere.
The mapping would be very useful - I know it took me a while and I still
get confused.
Bill - as part of your talk,
Hi Brian:
+ I think a *lot* of a11y bugs are really the same sort of problems
that you see over and over again. Programs that do not have
accessible labels for widgets, for example. Perhaps it would be
useful to pick a few bugs that are examples of the common a11y bugs
that
Hey All:
I haven't heard from anyone regarding this straw man agenda. I'd really
like some feedback on it. For example, if your feedback is well...I'd
like to attend, but the content is not really what I was hoping...
please let me know more about what your hoping for! This meeting
the suggestions from the community (THANKS!),
I've put together a straw man agenda for the Accessibility Summit for
October 8, 2006, as part of the GNOME Boston 2006 Summit:
http://live.gnome.org/Boston2006/AccessibilitySummit
The agenda is still up for discussion, so please send your
After consideration of all the suggestions from the community (THANKS!),
I've put together a straw man agenda for the Accessibility Summit for
October 8, 2006, as part of the GNOME Boston 2006 Summit:
http://live.gnome.org/Boston2006/AccessibilitySummit
The agenda is still up
be a great thing to have at GUADEC 2007
however...
regards
Bill
* What do we have?
* What do we need?
* How do we get there?
Brian
After consideration of all the suggestions from the community (THANKS!),
I've put together a straw man agenda for the Accessibility Summit
Hi All:
After consideration of all the suggestions from the community (THANKS!),
I've put together a straw man agenda for the Accessibility Summit for
October 8, 2006, as part of the GNOME Boston 2006 Summit:
http://live.gnome.org/Boston2006/AccessibilitySummit
It's a full day, with the day
