*** Original post on bio 1897 by Kiran Kaja <kkaja AT adobe.com> at 2013-03-13 11:30:00 UTC *** Using InstantBird 1.3 on Windows 7. Also using Jaws for Windows screen reader (www.freedomscientific.com) and/or NVDA (www.nvda-project.org). NVDA is free & open source and so can be used for testing. The issue is that I am unable to set focus to the chat log in the conversation window in order to be able to review the incoming chat messages with my screen reading software. When using the Tab key to navigate through the conversation UI, the chat log is skipped. Steps to reproduce: 1. install and run either Jaws or NVDA from the links mentioned above. NVDA is free & OpenSource. 2. when either Jaws or NVDA is running, open InstantBird. 3. Use the keyboard to navigate through the contacts and press enter on a contact to launch the conversation window with that contact. 4. The focus will be placed in the edit box to type in the message. 5. Navigate the Conversation window using the Tab key. The screen reader will anounce something on the lines of "edit, type in text". 6. Pressing Tab once from the edit field takes focus to the tab control with the name of the contact you are chatting with. Screen reader will announce "<name> tab". 7. Next tab key press puts focus in the chat log. You can use up and down arrow keys to move through the chat messages. There may now be any chat messages and so the screen reader may just read out the name of the contact when the arrow keys are pressed. 8. pressing tab again takes you back to the edit field for typing a message. 9. send a couple of messages to your contact. 10. Now try pressing the Tab key twice or just press Shift+Tab to go to the chat log. You may notice that you can't set focus to the chat log after you have sent a message or two. If you are still able to set focus to the chat log using the Tab key, please wait for your contact to reply to your message and send a message yourself in reply to that. It is a bit inconsistent to reproduce but after a 2 or 3 exchanges of messages, it shouldn't be too difficult to reproduce. the tab key completely skips the chat log and only moves between the edit field and the Tab control. This means that screen reader users cannot review incoming messages at all. This is really critical. We use Jabber internally to communicate at work and InstantBird is the only real solution that is an accessible client for blind people who use a screen reader. Pressing the
*** Original post on bio 1897 at 2013-03-13 11:41:02 UTC *** The tab key is used both for focus, and to complete nicknames in chat rooms. When the input box is focused, we use the tab key as the completion key if the input box already contains some text; if it's empty, we switch the focus to the next focusable element. Could it be that during your testing the input box wasn't empty? Also, did you test with a private conversation or in a chat room? I think for private conversations we could make the tab key work as a way to switch the focus even when the input box isn't empty, as there's no possible nick completion there.
*** Original post on bio 1897 by Kiran Kaja <kkaja AT adobe.com> at 2013-03-13 11:54:16 UTC *** I only tested with private conversations. There is no text in the input box when I am pressing the tab key. The focus does move to the next focussable element with the tab control but then it should go to the chat log which it doesn't. It used to happen earlier. I don't know if I updated to the latest version 1.3 recently but this problem started occuring about a couple of months ago. I have auto update turned on and so don't really remember when it was updated.
*** Original post on bio 1897 at 2013-03-14 12:15:36 UTC *** I can't reproduce this so far on Linux with the latest nightly build.
*** Original post on bio 1897 by gringochapin <cannona AT gmail.com> at 2013-05-25 14:42:47 UTC *** I'm using Windows XP and Jaws, and I may have encountered this issue as well, though not sure if it's the same issue or not, as it doesn't happen all that often. In my case, I never lose the ability to tab to the chat log, however, sometimes when I do so, Jaws doesn't seem to recognize that it is a browsable window, and so fails to enable the virtual buffer. This only seems to happen when I have multiple tabs open, so switching to another tab, and then back resolves it. (I have multiple tabs open often, so not sure if there's any correlation.) You might try opening a second conversation tab, and then switching back and forth once to see if that resolves it, at least temporarily.
*** Original post on bio 1897 by Hadi Remonion <hadirezaei AT gmx.com> at 2013-12-05 18:26:43 UTC *** using instantbird v1.4 and jaws. I cannot reproduce this problem. so it could be a local problem or a specific bug for 1.3 which is fixed now; in either way, I don't think this bug exist in instantbird 1.4 as everything seems to be working correctly.