-
-
Notifications
You must be signed in to change notification settings - Fork 630
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with editable text fields which update their value when the focus changes #220
Comments
Attachment test_label_as_edit_field_value.html added by jteh on 2008-11-05 15:00 |
Comment 1 by Iris on 2008-11-06 05:50 Attached is the log that I got for that particular occurence on Wordpress.com INFO - nvda (22:29:32): |
Comment 2 by jteh (in reply to comment 1) on 2008-11-06 07:00
It doesn't. :) I think this is a different bug, so please open another ticket and provide exact steps to reproduce. Btw, when including preformatted text like log files, either attach a file or enclose them in ! |
Comment 3 by jteh on 2008-11-06 07:03 |
Comment 4 by jteh on 2009-05-18 07:27 Better solution: Only update caret offset if it is outside the updated zone, otherwise leave it alone. |
Comment 5 by jteh on 2009-06-17 07:20 |
Comment 6 by jteh on 2009-06-25 00:39 |
Comment 7 by jteh on 2009-06-25 02:36 |
Reported by jteh on 2008-11-05 14:58
Some web sites use a technique whereby they present the label of an editable text field in its value:
The practical upshot is that the field will contain its label if it is empty, but otherwise, it will show the value entered by the user. This is problematic for accessibility anyway, but nevertheless, several sites do this.
Unfortunately, this is particularly problematic for NVDA. NVDA sets the focus to fields as the user moves to them with the cursor keys or quick navigation. The resulting focus event is normally ignored because the virtual caret is already in the field, so NVDA knows that the focus change was caused by the caret movement. However, if a prior element on the page updates during the focus change (as is the case with this technique), the virtual caret will not be in the field because the field wil move in the buffer as a result of the focus change. Thus, NVDA will not ignore the focus event.
This is particularly bad if "Automatic focus mode for focus changes" is enabled because, upon receiving the focus event, NVDA will then activate focus mode, even though the user might have actually moved there using cursor keys or quick navigation.
Steps to Reproduce
Actual Results
Focus mode will be automatically enabled upon landing in the second edit field.
Expected Results
Focus mode should not be automatically enabled.
Additional Information
The text was updated successfully, but these errors were encountered: