Opened 13 years ago
Closed 13 years ago
#8864 closed Bug (fixed)
[IE] Rich combo listbox improperly presented
Reported by: | Garry Yao | Owned by: | Garry Yao |
---|---|---|---|
Priority: | Normal | Milestone: | CKEditor 3.6.3 |
Component: | Accessibility | Version: | |
Keywords: | IE | Cc: |
Description
- Load any sample page, focus the toolbar and navigate to the "Format" button menu;
- Expected: AT announce the button as "menu button", with the keystroke hint prompted (press space to activate).
- Actual: AT announce the button as "menu button", but no keystroke prompt presented, instead AT reads the title of the button link element.
- Press Space key to open the dropdown.
- Expected: AT switches to form mode, announces the dropdown as "List Box";
- Actual: No role announced, AT start with the list box item's content text, followed by the presentation to the toolbar button which is missed at the previous step.
JAWS 13 is used in the testing on IE9/Window7, Firefox works well matches the expected behavior with the same testing environment.
Attachments (2)
Change History (9)
comment:1 Changed 13 years ago by
Milestone: | → CKEditor 3.6.3 |
---|
comment:2 Changed 13 years ago by
The history pointed me to [5085], even though I dont memorize clearly what would be the rational of the change, but at least it doesn't work for now, and some best practice out there has pointed us the correct way of having it is onto the iframe's body element.
Changed 13 years ago by
Attachment: | 8864.patch added |
---|
comment:3 Changed 13 years ago by
Owner: | set to Garry Yao |
---|---|
Status: | new → review |
The patch is enough to make it works in both IE and FF.
comment:4 Changed 13 years ago by
Status: | review → review_failed |
---|
Considering the way the panel plugin is coded, the patch can potentially break if !forceIFrame
, because the <iframe>
will not exist at that point. Because of this, the condition to be checked should be ( CKEDITOR.env.ie || !this.forceIFrame )
.
Other than that, the patch should be ok. It makes accessibility work a bit better with IE. Let's just keep in mind that IE is not our accessibility compatibility target.
Changed 13 years ago by
Attachment: | 8864_2.patch added |
---|
comment:5 Changed 13 years ago by
Status: | review_failed → review |
---|
comment:6 Changed 13 years ago by
Status: | review → review_passed |
---|
comment:7 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | review_passed → closed |
Fixed with [7451].
Priorities this one due to the severity, even not being a regression.