GSoC 2017: Accessibility - Week 1
I have been working on navigation commands to get to the next element and previous element of the score.
Below, I have written the key tasks I have completed, some tasks that stalled and the plan for next week.
Key accomplishments so far
I have been working on two navigation commands, next element and previous element. These commands select the next or previous element of the score. Elements like fingering and other note attached elements, articulation, lyrics, annotations and spanners are selected as well as major elements like notes, rests and clefs.
I am currently testing the commands and fixing some bugs. Most of the work is done.
Key tasks that stalled
Selection of spanners: This took some time, as spanners cannot be accessed from a score element. They need to be accessed from a global list.
Multiple staves: I had to make modifications so that the commands would work when the score has multiple staves. I fixed this by taking into account the active staff while finding the next element.
Tasks in the upcoming week
I plan to remove any remaining bugs from the next element and previous element commands. I would also like to start working on making all palette symbols keyboard accessible. There are a few approaches that have been considered so far.
One approach is to add shortcut commands for all palette symbols.
Another approach is to use the palette search feature and make the palettes navigable by keyboard, using the arrow keys. A shortcut command for palette search could be added, and the the search could be extended to search for palette names, apart from palette symbols.
I would like some feedback on which approach would be better, so that I can start working on the navigation of palettes. Please feel free to comment below.