Welcome, good to have you aboard! I think one of the first things we should probably do logistically is sort out what might be worth working on sooner rather than later so it can possibly be incorporated into the 2.0 release.
To my mind, the things that are most "2.0-worthy" are the basic things needed just to get existing the existing functionality more screenreader and keyboard friendly. Menus and dialogs most obviously. Also the major main window elements, at least to the extent that tabbing around the main window does something reasonable and takes you back where you started. My understanding is that the first thing a blind user does, aside from look at the menus, is tab around the main window to get a sense of what is there. This doesn't have to expose features that won't work anyhow (eg, the palette), but nor should it get the user into a state where the focus is somewhere they can't get out of easily. I think the goal should be that a blind use can at least open the program, open files, listen to playback, do "save as" to convert formats. I suspect we're close to this if not there already already for 2.0. Marc ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Mscore-developer mailing list Mscore-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mscore-developer
