#11260 closed Bug (fixed)
AVT: JAWS not reading disabled buttons as unavailable
Reported by: | Satya Minnekanti | Owned by: | Frederico Caldeira Knabben |
---|---|---|---|
Priority: | Normal | Milestone: | CKEditor 4.3.1 |
Component: | Accessibility | Version: | 4.3 |
Keywords: | IBM | Cc: | Teresa Monahan, Irina |
Description
To reproduce the defect:
- Open AJAX Sample and click on Create Editor button.
- Press Alt + F10 to navigate to toolbar.
- Navigate to Undo or Redo button.
Expected Result: JAWS should read Undo or Redo button unavailable
Actual Result: JAWS reads Undo or Redo button but it did not read unavailable. This is because aria-disabled=true missing on all the disabled buttons
This issue is only happening from 4.3
This is a failure of Accessibility checkpoint 1.3a & 4.1b
Change History (9)
comment:1 follow-up: 2 Changed 11 years ago by
Milestone: | → CKEditor 4.3.2 |
---|
comment:2 follow-up: 3 Changed 11 years ago by
comment:3 Changed 11 years ago by
Replying to tmonahan:
I'll check this, but we already froze the code and it's on testing phase for release on Tuesday. I'm afraid it may be already too late for it.
comment:4 Changed 11 years ago by
Owner: | set to Frederico Caldeira Knabben |
---|---|
Status: | new → assigned |
Introduced with git:a195b2a.
Basically, we're not any move initializing disabled buttons, so the aria-disabled attribute is not set on startup.
comment:6 Changed 11 years ago by
Milestone: | CKEditor 4.3.2 → CKEditor 4.3.1 |
---|---|
Status: | review → review_passed |
I pushed additional commit which fixes a bug in a button template.
comment:7 Changed 11 years ago by
Resolution: | → fixed |
---|---|
Status: | review_passed → closed |
Fixed on master with git:93a07a4.
comment:8 Changed 11 years ago by
Thanks to you all for the speedy turn around on this! We really appreciate it!!
comment:9 Changed 11 years ago by
Summary: | AVT: JAWS not reading disbaled buttons as unavailable → AVT: JAWS not reading disabled buttons as unavailable |
---|
issue summary typo fixed
Replying to fredck:
Hi Fred, Can this be targeted for 4.3.1? This is an accessibility failure and the 4.3.2 release will be too late for some of our products.