I know that SWT has an accessibility API which you can use for your own widgets, and there are SWT snippets showing how to handle assistive technology querying a text type control.
http://git.eclipse.org/c/platform/eclipse.platform.swt.git/tree/examples/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet334.javaWhile I agree that StyledText should be accessible by default and so probably something for the Eclipse developers to solve, there might be a point when BrailleBlaster is doing sufficient custom stuff in the edit areas that additional accessibility information needs to be given.
I can have a look at what NVDA is recieving in its log, but I probably cannot deal with it until the weekend.
Michael Whapples On 16/05/2013 17:37, Keith Creasy wrote:
Vic.Since WE works I'm guessing that they have just done something to support SWT's methods that the others haven't. I feel certain we can do something to fix it. Actually if we can just get WE, and NVDA to work on Windows I'll be pretty satisfied. Then we can complain to FS that both those screen readers work and maybe they'll fix it too.If we have someone on here who is involved with NVDA they could probably catch the output from the read-line method and see what actually is coming from the widget.I'm not sure what the styled text view does internally. There is a Unicode value for a soft return but it's not that easy to figure out if it is used.Keith Creasy Software Developer American Printing House for the Blind KCreasy@xxxxxxx Phone: 502.895.2405 Skype: keith537*From:*brailleblaster-bounce@xxxxxxxxxxxxx [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] *On Behalf Of *Vic Beckley*Sent:* Thursday, May 16, 2013 12:03 PM *To:* brailleblaster@xxxxxxxxxxxxx *Subject:* [brailleblaster] Re: Screen readers broken with latest build Keith and Brandon, I guess we'll just have to get everyone to switch to W-E! LOL!!!Seriously, I agree that you shouldn't need to have sophisticated configuration files for the different screen readers. I also agree that you shouldn't have to add hard returns. That isn't done in any other text editor like Word. Aren't the line endings in Word just marked with soft returns and paragraphs with hard returns? Could the problem lie in what character the accessibility interface is using for a soft return? I don't understand if that is the problem then why does W-E interpret it correctly? It actually is doing better now than when you were putting in the hard returns.Brandon, FYI: All other navigation commands seem to speak correctly. It is just the up and down arrow keys that don't.Best regards from Ohio, Vic*From:*brailleblaster-bounce@xxxxxxxxxxxxx <mailto:brailleblaster-bounce@xxxxxxxxxxxxx> [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] *On Behalf Of *Keith Creasy*Sent:* Thursday, May 16, 2013 10:19 AM *To:* brailleblaster@xxxxxxxxxxxxx <mailto:brailleblaster@xxxxxxxxxxxxx> *Subject:* [brailleblaster] Re: Screen readers broken with latest buildScripts might be possible but it shouldn't be necessary and it's bad because each one has a different scripting vocabulary.I think that what is happening is that the SWT text widget is giving the screen reader the entire paragraph when it asks for a line. Basically the "soft" returns are invisible to the accessibility interface in the SWT widget. I think Ken might have a contact with someone who works on the SWT widgets so maybe we can do something there.Keith Keith Creasy Software Developer American Printing House for the Blind KCreasy@xxxxxxx <mailto:KCreasy@xxxxxxx> Phone: 502.895.2405 Skype: keith537*From:*brailleblaster-bounce@xxxxxxxxxxxxx <mailto:brailleblaster-bounce@xxxxxxxxxxxxx> [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] *On Behalf Of *Brandon Roller*Sent:* Thursday, May 16, 2013 10:13 AM *To:* brailleblaster@xxxxxxxxxxxxx <mailto:brailleblaster@xxxxxxxxxxxxx> *Subject:* [brailleblaster] Re: Screen readers broken with latest buildI am not very familiar with screen readers, so these suggestions may not work at all.Are there configuration settings that could be changed to make them read by word or by sentence?Or would it be possible to write scripts so that a screenreader behaves a certain way when BB is run?On Thu, May 16, 2013 at 10:10 AM, Keith Creasy <kcreasy@xxxxxxx <mailto:kcreasy@xxxxxxx>> wrote:Hi Vic.I'm not sure what we can do about the screen reader issues. WE understand the problem but it really is between SWT's accessibility interface and the screen readers. We can at some point go back to putting in hard new-line characters, which is what made it work for a while, but that really isn't a good solution in my opinion.Keith Keith Creasy Software Developer American Printing House for the Blind KCreasy@xxxxxxx <mailto:KCreasy@xxxxxxx> Phone: 502.895.2405 <tel:502.895.2405> Skype: keith537*From:*brailleblaster-bounce@xxxxxxxxxxxxx <mailto:brailleblaster-bounce@xxxxxxxxxxxxx> [mailto:brailleblaster-bounce@xxxxxxxxxxxxx <mailto:brailleblaster-bounce@xxxxxxxxxxxxx>] *On Behalf Of *Brandon Roller*Sent:* Thursday, May 16, 2013 9:59 AM *To:* brailleblaster@xxxxxxxxxxxxx <mailto:brailleblaster@xxxxxxxxxxxxx> *Subject:* [brailleblaster] Re: Screen readers broken with latest build Vic,I made changes to the layout so that more document, such as your Acts file would open.BB should now open more varieties of document consistently.A trade-off at the moment is that there are screenreader issues with occur.On Thu, May 16, 2013 at 9:45 AM, Vic Beckley <vic.beckley3@xxxxxxxxx <mailto:vic.beckley3@xxxxxxxxx>> wrote:Brandon and Keith,NVDA and Orca are broken with the latest changes to BB. Now 100% of the timethey read the entire paragraph when moving up or down with the arrow keys. NVDA was reading practically flawlessly before these latest updates.Ironically, W-E is working better now. The only problem it is having now isthat it doesn't track the cursor when switching between views until it moves. Best regards from Ohio, Vic
