Hi all,
Here are some points that I need to clarify with you guys.
2) Enable the use of keyboard to navigate to a text element or an
articulation or a crescendo marking.
Use the existing “next element” code to traverse the "annotations" for each
ChordRest segment, the Articulations for each ChordRest, etc. Here what is
remaining, according to my opinion, is to implement a method to dynamically
alter the string which is displayed in the status bar to include attached
elements. Andrei, please do share your original plan to implement this. I
think it will be helpful here.
5) Support for other screen-readers- VoiceOver on OS X and also Orca
on Linux.
When implementing support for VoiceOver on OS X , I will face a problem
since I do not own a Macintosh <https://en.wikipedia.org/wiki/Macintosh>
computer. Any word of advice on this issue will be helpful.
In addition, I add the following point to my list.
6) Make the palettes accessible to the screen reader.
If we have the implementation for QAccessibleWidget for the Palette object
already, I think it remains only to implement the part which gathers the
information from the selected element and creates the string which is
displayed in the status bar and exposed to the Screen Reader.
Best Regards,
Samadhi.
On 20 March 2016 at 20:30, Lasconic <lasco...@gmail.com> wrote:
> Just want to add that Braille output is a huge project by itself if we
> want to do it from scratch... So I wouldn't focus on this during a GSoC
> project. Your point 1, 2, 4 and 5 are more focused on MuseScore's
> accessibility.
>
> Regarding braille though...
> We could of course integrate with freedots, but the project is currently
> inactive. However it's the shortest road.
> I currently operate http://musicxml2braille.appspot.com/. Doing a REST
> API call from a plugin to get Braille out is probably doable. But, of
> course, the plugin needs to be accessible... Not sure it's the case for any
> plugin right now.
>
> lasconic
>
> 2016-03-20 7:48 GMT+04:00 Marc Sabatella <m...@outsideshore.com>:
>
>> On Sat, Mar 19, 2016 at 1:51 AM Samadhi Poornima <
>> samadhipoornima...@cse.mrt.ac.lk> wrote:
>>
>>
>>> 2). Enable the use of keyboard to navigate to a text element or an
>>> articulation or a crescendo marking.
>>>
>>
>> I think there is probably a pretty straightforward model for how this
>> could work, based on the existing "next element" code Andrei added (which
>> navigates clefs and barlines and some other elements, but not
>> articulations, text, or crescendos) but making sure to also traverse the
>> "annotations" for each ChordRest segment, the Articulations for each
>> ChordRest, etc. Here as elsewhere, feedback from actusal blind users would
>> be useful.
>>
>>> 3). Braille output- I plan on doing this by calling the FreeDots
>>> executable once the user enters the command to import the file to braille.
>>> However, this would not be the optimum solution to this since FreeDots is
>>> written in java.
>>>
>>
>> There are other concerns here too. FreeDots is a good thing, but it is
>> pretty limited in what it can do. There are other automatic or
>> semi-automatic MusicXML->Braille converter, each of which also has
>> limitations but different progrsams have different strengths and
>> weaknesses. There are a few people out there in the world who have done
>> fairly extensive study of these issues that you might want to consult, also
>> it might be good to contact the develoeprs of these tools to get a sense of
>> their plans for the future to see which tool might make the most sense for
>> us to focus our integration efforts on. Frankly, I'm not 100% convinced it
>> wouldn't someday be worth implementing out own Braille export, working
>> directly from our own score representation (although I recognize that this
>> becomes one more thing to maintain over time, so I don't make this
>> statement lightly).
>>
>> Marc
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Transform Data into Opportunity.
>> Accelerate data analysis in your applications with
>> Intel Data Analytics Acceleration Library.
>> Click to learn more.
>> http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
>> _______________________________________________
>> Mscore-developer mailing list
>> Mscore-developer@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>>
>>
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
> _______________________________________________
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
>
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
Mscore-developer mailing list
Mscore-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mscore-developer
