[wp-trac] [WordPress Trac] #12423: Include default code editor
WordPress Trac
noreply at wordpress.org
Wed Mar 8 00:20:59 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 zersiax):
You make some good points. Overall, I am a proponent of trying to make
mainstream tools work for screenreaders, there's a huge amount of reasons
I could list for that. I'm not sure if I agree with the fact that it's not
an accident a combo editor was never created; that seems more like a
supply & demand problem to me.
I know loads of code editors that either don't build in access features
because they don't have the bandwidth, or the knowledge, or the money, or
the time , or the incentive, or the myriad of other excuses I see over and
over and over again when I ask.
In this day and age, where most phones have a screenreader built in, most
pc's do as well and more and more "mainstream" tech is introduced that
actually is usable by the blind, what are called 'blind ghetto' products
are becoming less and less popular. Creating a specialized editor for the
blind seems to make sense, but do keep in mind that this introduces quite
a bit of overhead for maintaining the two editors in sync. E.G., the
specialized editors will likely require a lot of accessibility markup that
not everyone is familiar with, so if the folks who built it decide to
leave for the nearest space dock, we do have a problem.
I wouldn't say it's impossible to create an editor that caters to both
groups; if you look at my wishlist above, you'll find that a lot of the
things I put down aren't specific to accessibility. They are just features
you guys have had forever that I would like to see made accessible, or at
least unobtrusive enough to stay the heck out of my way if I can't use
them anyway ;)
There is a case for creating a low-fi text editor for the folks who don't
want extra complexity in their lives', the lowest common denominator as
you mentioned, but I think that would impede progress quite a bit. I would
like to add to that however that we should only replace that "dumb" editor
if we have a better alternative, better in this case being better for
everyone. If you want to go for progressive enhancement, perhaps in the
next few minor version upgrades the installer should allow for an editor
to be selected until we are certain we can deliver a good editing
experience for everyone.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/12423#comment:76>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list