Opened 15 years ago
Closed 12 years ago
#5004 closed New Feature (wontfix)
Create accessibility plugin
| Reported by: | Garry Yao | Owned by: | Garry Yao |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | Accessibility | Version: | |
| Keywords: | Confirmed | Cc: |
Description (last modified by )
ARIA is still not fully supported in browsers and screen readers. We still want to have the editor accessible with some old technologies, these should have a dedicated plugin for all the backwards (hacks) compatibility. It would make the necessary changes to the editor structure to make it accessible on some situations. It should be optional, loaded only when needed.
Change History (6)
comment:1 Changed 15 years ago by
| Description: | modified (diff) |
|---|---|
| Owner: | set to Garry Yao |
| Status: | new → assigned |
comment:2 Changed 15 years ago by
comment:3 Changed 15 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Fixed with [5092] in 3.2.x branch.
comment:4 Changed 15 years ago by
| Milestone: | CKEditor 3.2 → CKEditor 3.x |
|---|---|
| Resolution: | fixed |
| Status: | closed → reopened |
The last test results with ARIA support on core showed that we actually have quite few issues with non ARIA browsers. Actually, ARIA is bringing better support even on those browsers. Because of this we still need to understand the effective benefit of the compatibility plugin.
For now, I've removed the plugin with [5174]. We need to make more testing and research before considering proposing it again.
comment:6 Changed 12 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | reopened → closed |
I think that this issue expired.
Changes are checked in with [4925] on aria branch.