Reported by gandalf on 2015-04-22 09:48
This problem is valid for all form fields and aria widgets that need focus mode in browsers.
In the last time there is more and more English words and concepts that are used, especially in Web pages and Web apps. Please prioritize this issue high despite you as English speaker do not have this problem so urgent.
The bug is easy to explain: NVDA recognizes and reads properly all language switches made by lang="SomeLanguageCode", but only if currently in browse mode. If you tab through your form fields / aria widgets in a web page, NVDA s witches automatically in the focus mode. In this mode all widget names and form field labels are read exclusively in the main document language ignoring all swithes through the lang attribute. This is actually a large bug - also in JAWS. Be so good and make NVDA better than JAWS also in this regard :)
Blocked by #3188
Reported by gandalf on 2015-04-22 09:48
This problem is valid for all form fields and aria widgets that need focus mode in browsers.
In the last time there is more and more English words and concepts that are used, especially in Web pages and Web apps. Please prioritize this issue high despite you as English speaker do not have this problem so urgent.
The bug is easy to explain: NVDA recognizes and reads properly all language switches made by lang="SomeLanguageCode", but only if currently in browse mode. If you tab through your form fields / aria widgets in a web page, NVDA s witches automatically in the focus mode. In this mode all widget names and form field labels are read exclusively in the main document language ignoring all swithes through the lang attribute. This is actually a large bug - also in JAWS. Be so good and make NVDA better than JAWS also in this regard :)
Blocked by #3188