Re: [sage-cell] Web accessibility of Sage cells

2016-12-01 Thread Rob Beezer
In the past, Alex has been able to have a student actually test this sort of thing, while being videorecorded for analysis. Maybe that would be an option once something is in place (or Alex's accessibility expersts could be consulted about various options). Rob On 12/01/2016 08:16 AM, Jason

Re: [sage-cell] Web accessibility of Sage cells

2016-12-01 Thread Alex Jordan
I'm arranging for some user testing by at least one screen reader user, possibly two, likely to take place on Friday December 16. I will be present with the end user, and possibly another staff member will be present to manage recording the session. I'm planning to do testing with some

Re: [sage-cell] Web accessibility of Sage cells

2016-12-01 Thread Alex Jordan
The staff here confirm that with conventional user expectations, ESC is the right way to exit the cell for a keyboard navigator. Where that should take you is going to be something to probe with the user testing. On Thursday, December 1, 2016 at 8:16:47 AM UTC-8, Jason Grout wrote: > > Perhaps

Re: [sage-cell] Web accessibility of Sage cells

2016-12-01 Thread Andrey Novoseltsev
I am happy to do and roll out any changes necessary, but I need some pointers on where and how they should be done technically. A probably related request from a long time ago about voice over: https://groups.google.com/d/topic/sage-devel/Q952nMqGHjs/discussion Thank you! Andrey On Thursday,

Re: [sage-cell] Web accessibility of Sage cells

2016-12-01 Thread Jason Grout
How about escape to leave the editor and focus the div around the editor, like in the Jupyter notebook? On Thu, Dec 1, 2016, 00:26 Alex Jordan wrote: > I work on MathBook XML and WeBWorK, both of which make use of Sage cells. > So first I want to thank this community