Agenda

Meeting Log

Matthias sent a message to the GNOME Accessibility Devel list about themes in GNOME 3.
Piñeiro identified these areas which need to be tested:
1. Are the a11y themes working well?
2. Can we improve the a11y themes?
"Good enough"?
- Related to the second area, Piñeiro pointed out that Joanie (not yet present) had told him that she thought some of the existing (GNOME 2) a11y themes "are not good enough."
- Piñeiro added that in theory, one of the reasons for the new themes is to provide a more flexible and easier way to create and modify themes.
- Li asked if we had open bugs for the "not good enough" themes. Piñeiro responded that Joanie had made this claim in an informal chat.
Automated testing of themes
- Brian pointed out that automated testing of "good enough" will prove difficult.
- Piñeiro agreed, observing that one thing we need to test is that people requiring the themes can properly identify/distinguish the elements on the screen.
- Brian suggested that it might be possible to determine whether a component is honoring the themes, which was a problem in the past. But he added that this might still prove to be a lot of work.
- Peter responded that it would be useful to see if icons changed when the theme changed.

Gtk2 theme creation was complex and not well documented; hopefully this has been improved.
We need to test specifically:
1. Are the a11y themes working well?
2. Can we improve the a11y themes?

Brian asked if anyone had been able to look at the accessibility tests he has in launchpad.
Piñeiro asked if he had announced it on the gnome-accessibility-devel list.
Brian responded that he had mentioned it a while back during a team meeting, but would make a list announcement.
In reply to Piñeiro's questions about the coverage, environment, and documentation, Brian stated:
- The tests are not used within Accerciser, but are compatible with Accerciser validator plugins.
- They include all of the tests the plugins run, plus test a few other areas including focus traversal.
- They are meant to add accessibility test functionality to existing Mago-based application tests, as well as allow accessibility-specific tests of the entire desktop.
- How to install and run the tests is not yet documented. He plans to improve the documentation.
- He plans to move his build and test environment to GNOME 3.0 soon.

Piñeiro stated that:
- He has officially announced the event.
- The place and date are set.
- A reasonably-priced and close-to-the-venue hotel has been recommended.
- More info can be found at: http://live.gnome.org/Hackfests/ATK2011
Joanie suggested that the hackfest page should include a link to the hotel.
Piñeiro responded that it was present via the google maps link which links to the official hotel page.
Li asked if attendees should book their own reservations or if GNOME would do it for us.
Piñeiro stated he would look into this and see what was done for the Gtk hackfest.

People who require Foundation funding to attend should apply with the Travel Committee.

Li stated that he has been working on the move of Gail to Gtk.
Piñeiro asked if there was a deadline and if this was planned for inclusion in GNOME 3 or not.
Li replied that there was currently not a deadline set, but that it might be finished before GNOME 3.
Li has moved 14 widgets so far, but added that several complex widgets remain.

Due to the complexity and the time remaining before GNOME 3, merging the branch to master might not be feasible.

Regarding new themes, the team should test specifically:
1. Are the a11y themes working well?
2. Are there areas in which we can we improve the a11y themes?
Regarding Brian's Mago testing framework:
- Brian will announce his tests on the gnome-accessibility-devel list.
- Brian will create a README and an INSTALL for his tests.
Regarding the Atk Hackfest:
- People who require Foundation funding to attend the should apply with the Travel Committee.
- Piñeiro will investigate if Atk Hackfest attendees should book their own hotel reservations, or if GNOME will do it for us.