Metadata
- Source
- FLUID-3845
- Type
- Bug
- Priority
- Critical
- Status
- Open
- Resolution
- N/A
- Assignee
- Jonathan Hung
- Reporter
- Jonathan Hung
- Created
2010-11-18T11:58:27.844-0500 - Updated
2017-09-27T10:33:56.793-0400 - Versions
-
- 1.3
- 1.4
- 1.5
- Fixed Versions
- N/A
- Component
-
- Inline Edit
Description
When entering edit mode, NVDA reads out "Edit Autocomplete" for editable fields. This should be removed to reduce confusion.
Environments
FF3.6 NVDA 2010.1
Attachments
Comments
-
Jonathan Hung commented
2010-11-18T15:17:34.892-0500 Some more details:
- issue seems to be present in NVDA 2010.1 and with v3939 dev snapshot in FF3.6.
- JAWS does not read out "Auto complete".
- NVDA and IE8 was tested, but inconclusive because of outstanding functionality issues with the inline edit demo and IE8.
-
Jonathan Hung commented
2010-11-18T15:30:15.175-0500 Also seems to be the same issue reported at NVDA: http://www.nvda-project.org/ticket/783#comment:2
The issue was determined to be a Firefox issue.
-
Jonathan Hung commented
2010-11-18T15:46:03.898-0500 Updated patch with comment and JSLinted.
-
Michelle D'Souza commented
2010-11-18T17:05:17.705-0500 We need to do some more design thinking and exploration before we put this fix into trunk. We are doing more then just controlling what the screen reader says, we are actually changing the default behaviour of the input and removing the browser's inbuilt autocomplete behaviour. We need to determine whether we are correct in assuming that having the browser read 'edit autocomplete' is in fact confusing and we also need to determine that we truly want to remove the default autocompleting behaviour. If we do decide that we want this behaviour we should consider exposing it in the public API so that people using the component can override this.
-
Justin Obara commented
2017-09-27T10:33:21.471-0400 In FF 55 and NVDA 2017.3 it now says "edit has autocomplete" at the beginning.
-
Justin Obara commented
2017-09-27T10:33:56.793-0400 @@Jonathan Hung do you think we can close this issues as won't fix? I think the behaviour is acceptable as is.