2014-08-27 20:42 GMT+03:00 Marc Sabatella <[email protected]>:
> Andrei, this is mostly for you, but also so others can comment.
>
> Really great work on getting the first level of accessibility into
> MuseScore
> 2.0 Beta 1! If you haven't already created a forum account on
> musescore.org, please do so and check out the discussion at
> http://musescore.org/en/node/30896, then maybe start a new thread in the
> Technology Preview forum to share your thoughts, begin new discussion, etc.
>
I do have an account on musescore.org, but I didn't spend much time on the
forum.
I know you've begun work on palettes, and I'm curious to know what approach
> you have in mind. "Most" palette items can be added by clicking the score
> then double clicking the palette icon, so those should be relatively
> straightforward to model with keyboard. More problematic would be the
> elements - such as those in the "Lines" and "Repeats" palettes, also key
> and
> time signatures when adding new ones as oppsoed to replacing existing ones
> -
> that currently require drag and drop. But a solution that simplified this
> for sighted users as well would of course be very welcome!
At the moment I only made possible tabbing through the buttons that open
and close the
palettes. Now, I'm trying to make tabbing work in the palette itself. At
the moment I'm going
through the code to see how can I do that. And the first thing alfter is to
make Space/Return
behave like double click for the selected item.
>
> Remember we still need to make the Create New Score wizard accessible or
> else all the keyboard shortcuts in the world for palette items won't help
> :-)
>
Create New Score dialog is already mostly accessible. The instrument adding
will need a bit
of improvement, but if I remember correctly the most problematic is the key
signature adding
which is done through the key signature palette, that's one of the reasons
why I chose to start
working in the palettes.
>
> In another random bit of news, a month or so ago I had been approach by a
> blind musician / programmer interested in pursuing work I had begun last
> summer - I had prototyped an accessible score reader using Python & the
> music21 library. He just wrote me back this morning to tell me he was
> almost done. I shared the news of the beta with him and the fact that we
> basically have score reading functionality in there (subject of course to
> further tweaking). Hopefully he'll be in touch with us and interested in
> discussing further ideas.
>
Sounds great! I would like to try his work when it's done. I would like to
see how a score reader
sounds from his perspective.
> I will be posting news of the Beta and its accessibility features to the
> MENVI mailing list and my own Accessible Music Notation Project blog. So
> hopefully we'll soon have eager users checking things out!
>
I'm eager to hear some feedback! :)
> Marc
>
Andrei
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
