NVDA not reading first letters in the edit field when searching for contacts in skype 6.2. #3036

Closed
nvaccessAuto opened this Issue Mar 2, 2013 · 4 comments

1 participant

@nvaccessAuto

Reported by ateu on 2013-03-02 12:07
Steps to reproduce.

  1. Open skype 6.2;
  2. Tab to the edit field below the add contact;
  3. Edit a name.

Expected result: NVDA should announce/show the intire name.
Actual result: NVDA announce/shows the name missing one or two letters.
Also, if you move with arrow keys incide the edit field, you will read the name missing the first letters, as well it's announced.

Tested with other screen readers and works OK.

@nvaccessAuto

Comment 1 by Palacee_hun on 2013-03-28 18:24
This is reproducible and also occurs with Skype 6.0 (and maybe the 5.x series?). Inspired by the change to map TChatRichEdit to RichEdit20, I did a little investigation. I quickly found out that if I mapped "TAccessibleEdit" (the class name of the control in question) to "Edit", the problem went away completely. The cause of this is that since NVDA doesn't recognise this control as a real edit control by its name, it falls back to using the display model to emulate editing functionality and the display model of Skype has some issues (quite mysterious ones indeed). That's why I suggest reviewing the Skype control classes and find out which have issues just because they have a non-standard name. Remapping those may cure their problems and improve Skype accessibility.

@nvaccessAuto

Comment 2 by jteh on 2013-03-28 23:59
We didn't realise these supported standard Edit APIs; this isn't documented anywhere I know of. This should be at least investigated for 2013.2.
Changes:
Milestone changed from None to 2013.2

@nvaccessAuto

Comment 3 by ateu on 2013-04-02 09:43
I think it has been fixed as of a5eec6e.
Here, the problem stoped.

@nvaccessAuto

Comment 4 by jteh on 2013-04-03 17:59
Closing as per comment:3.
Changes:
State: closed

@nvaccessAuto nvaccessAuto added the bug label Nov 10, 2015
@nvaccessAuto nvaccessAuto added this to the 2013.2 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment