[wp-trac] [WordPress Trac] #38342: Quick Draft: Leverage REST API endpoints

[WordPress Trac]

#38342: Quick Draft: Leverage REST API endpoints
-------------------------------------+-------------------------------------
 Reporter:  adamsilverstein          |       Owner:  joehoyle
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  Future Release
Component:  Administration           |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch 4.8-early      |     Focuses:  accessibility,
  needs-refresh has-unit-tests       |  javascript, rest-api
-------------------------------------+-------------------------------------

Comment (by afercia):

 Re: date formatting, see also #39222.

 @adamsilverstein sorry for the late reply and thanks for all your work
 here! Tested [attachment:38342.22.diff] so not looking into the Date
 issues and it looks good to me, except one thing I haven't considered
 before.

 The thing is, even if the `speak` messages are now assertive, after 250ms
 focus is moved to the Title input field so screen readers will stop
 announcing the message and will start announcing the input field. Tested
 with Safari+VoiceOver and Firefox+NVDA what they announce is something
 like:
 `An err... Title edit text`
 or:
 `Suc... Title edit text`
 which defeats the purpose of sending audible messages altogether. I've
 tried to delay the messages too but it doesn't work well. I'd consider to
 don't move focus at all (note: it doesn't happen when `! hasValuesToSave`)
 and keep it on the button. I understand moving focus has some benefit for
 users who are going to post multiple drafts but in this case it breaks
 accessibility and haven't found other ways to make it work.

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