[wp-trac] [WordPress Trac] #12423: Include default code editor

WordPress Trac noreply at wordpress.org
Mon Mar 20 22:08:31 UTC 2017


#12423: Include 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 afercia):

 I'd strongly recommend everyone taking part in this discussion to spend a
 few minutes of their time and watch the following videos (or, better,
 actually test with assistive technologies) to get an idea on how non-
 standard solutions fail with software that expect, correct HTML, proper
 semantics, and predictable interaction models.

 Admittedly, these are just partial tests with just one screen reader and a
 speech recognition tool. However, they both result in a strongly increased
 difficulty when using the editor or even in the complete inability to
 enter text.

 Tests run on the Theme editor with the patch from this ticket applied and
 on this codepen: http://codepen.io/afercia/full/pRBxwd/ where the only
 difference is that it uses an ARIA `role: "textbox"`, an `"aria-
 multiline": "true"`, and an `aria-label` attributes.

 '''Dragon NaturallySpeaking'''
 Tests recorded by Graham Armfield at WordCamp London 2017

 Theme editor with CodeMirror, compared to the Post editor simple textarea:
 the most basic operations fail, while they perfectly work on the standard
 textarea.
 https://youtu.be/AfWyqMCXI9I

 Codepen: basically the same results, also highlighting how the focus
 indicator (caret) and the actual insertion point are often disjointed
 https://youtu.be/b03tGluQiCo

 '''Testing Safari 10 + VoiceOver on the Codepen'''
 Apart from sometimes losing the insertion point, it's pretty evident that,
 when navigating by word or by character, VoiceOver gets stuck when it
 encounters a line number:
 https://www.youtube.com/watch?v=QSW2CZkOaSI

 When removing the line numbers, things work a bit better:
 https://www.youtube.com/watch?v=Rz6X1JMBlBk

 Will try to follow up with some more generic considerations soon.

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


More information about the wp-trac mailing list