[wp-trac] [WordPress Trac] #12423: Include Ace (or similar) as default code editor

[WordPress Trac]

#12423: Include Ace (or similar) as default code editor
-----------------------------+----------------------------
 Reporter:  scribu           |       Owner:  afercia
     Type:  feature request  |      Status:  assigned
 Priority:  normal           |   Milestone:  4.8
Component:  Editor           |     Version:  3.0
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:  accessibility
-----------------------------+----------------------------

Comment (by FolioVision):

 Thanks for the link, Aaron.

 Aaron and Andrea, I'm a bit surprised to hear again about the guidelines
 when I'm asking about a gold standard implementation. **What is the best
 existing implementation of accessibility for screen readers in a code
 editor?** If we are to aspire to a better accessibility for screen
 readers, starting with the most successful screen reader code editor to
 date as a model would make the most sense.

 If there are no good of implementations of code editors for screen
 readers, then we should say so and decide what is realistic to do within
 this round.

 PS. On the other hand, if the best implementation is in CKeditor for
 example and we are determined to prioritise accessibility, perhaps it
 would make sense to move to the modular and fast iterating CKeditor from
 TinyMCE. CKeditor would give us perfect code support within the WordPress
 editor (hurray, no more mangled markup: even our venerable
 [https://wordpress.org/plugins/foliopress-wysiwyg/ Foliopress WYSIWYG]
 based on FCKeditor doesn't mangle markup) with even Markdown close at
 hand.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/12423#comment:56>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform