Accessibility/Meetings/2013-03-20: Difference between revisions

m
no edit summary
m (fixed links to goals)
mNo edit summary
Line 1: Line 1:
==Agenda==
* [https://wiki.mozilla.org/Platform/2013-Q1-Goals#Accessibility Q1 goal status]
* [https://wiki.mozilla.org/Platform/2013-Q1-Goals#Accessibility Q1 goal status]
* [https://wiki.mozilla.org/Platform/2013-Q2-Goals#Accessibility Q2 goals draft]
* [https://wiki.mozilla.org/Platform/2013-Q2-Goals#Accessibility Q2 goals draft]
* Round table
* Round table
==Meeting notes==
attending: dbolter, hub (hubert), trevor (tbsaunde), marcoz, lizzard, yzen, eeejay (eitan)
* Chat about an Android regression.  Top 3rd of screen breaks with AccessFu, it drops down menu or opens the awesomebar.
** What tests can be set up for the team so it doesn't break?
** The fix had something like 8 or 9 patches. The bug is probably in one of those fixes.
* Q1 goals
* getting better and better on performance,
* minor problems on mac with voiceover
** loads marco's main blog page, it still freezes when voiceover tries to read it
** most important thing now is to provide text editing.  that is not working across the board now.
** voiceover  needs to update and read the braille.
** filling out forms with firefox - people are unhappy if they can't control what they've typed.
** maybe firing too many events is the voiceover problem
** trevor - actually we queue up a lot of events but don't fire them.  (or was he talking about safari?)
* Someone might go through [http://asurkov.blogspot.com/ blog posts that alex wrote] - changes from/for vendors.
Q2 goals draft - on Platform/2013 (Platform engineering)
- fixes to gaia, make sure it is accessible
- get AccessFu up to speed
- blake - re-writing xpl, in conversation with them about making sure it is safe
- Thoughts about android and gaia, a lot of stuff gets rewritten every other week. Tabs handling has been rewritten three times recently. Mobile is very much in flux. Need to get into people's heads how to properly code this stuff. Proper visibility hidden and visibility visible, rather than pushing into the z-axis. Use proper techniques.
- Reactivity goal around stuff we do that isn't in features. assist to resolve any access work within X weeks.
-- Review iterations, try and iterate fast enough so he can land his feature within 2 weeks.
-- This is not completely under our control
- Security goal. sharing the goal with security teams.
- Ian Barlow  https://wiki.mozilla.org/Firefox/Goals/2013Q2#Profile_Related_Work
-- Boriss may be working on something for desktop, Jennifer Morrow also mentioned.
- Checkboxes that could kill us  post by alex limi
-- http://limi.net/checkboxes-that-kill
-- Tools, options, advanced accessibility. What effect does smooth scrolling have when it toggles,
- April firefox work week?
- Workweek in toronto? no update. don't know yet
- Bug day from last week, about 20 bugs triaged, some closed, some activity/response
-- community interest in future accessibility bug days
-- Liz will talk with dbolter about scope and focus for next event
Confirmed users
2,816

edits