Opened 15 years ago
Closed 15 years ago
#3383 closed Bug (invalid)
Unable to use screenreader in FF Ajax Example
| Reported by: | Damian | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | CKEditor 3.0 |
| Component: | General | Version: | |
| Keywords: | IBM | Cc: |
Description
There is a problem using the JAWS screen reader with the Ajax example.
Steps to reproduce:
- Open JAWS
- Open the Ajax sample from the nightly build
- Tab until reaching the editing area of the editor, ensuring that the cursor is within the editing area.
- Attempt to type text into the editing area.
Actual result:
Typed text is not entered into the text area. When the letter 'A' is typed, the screen reader reads "No Anchor Tags Found".
FF2 only.
Change History (2)
comment:1 Changed 15 years ago by
| Summary: | Unable to use screenreader in FF2 Ajax Example → Unable to use screenreader in FF Ajax Example |
|---|
comment:2 Changed 15 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
This is an issue when the JAWS Virtual PC Cursor is turned on.
Turning it off using INSERT + Z will return to normal keyboard navigation and input.
Note: See
TracTickets for help on using
tickets.
This is both FF2 and FF3