text files) we can do better than that if there's an editor lexer I can use to classify characters by sentence as opposed to line, that would be good. For now, I've implemented line semantics for both types of request. The text reader interface makes a distinction between a "sentence" and a "line".I'm not sure how to make the screen reader invoke those, to see whether they need to be wrapped in command actions or if these will function the same way a Swing event originating a text change does. I've marked some TODOs in the code: I'm not sure whether we need to hold a write lock for the AccessibleText callbacks for updating the text.Given than MacOS support is broken in other ways, we will revert to returning a supported role (e.g. although the reader can "read" the text line when moving the mouse. By "not working", we mean that the screen reader does not read line text when the caret moves in the editor. Note (October 2015): It turns out the things are not working under Windows + NVDA, because the "textarea" role is non standard, and NVDA does not understand it.But until we test it, I'm going to assume it's broken. I'm optimistic that things will work better on Windows (since back when Swing was adding accessibility, Windows was the main platform they targeted with the Accessibility Bridge etc), so hopefully simply implementing the AccessibleContext interfaces and firing property events will be adequate. Next I need to see what happens on Windows and Linux, and whether additional changes are required.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |