WordPress.org

Make WordPress Core

Opened 6 years ago

Last modified 2 months ago

#23562 reopened defect (bug)

Using Speech Recognition Software with the Add Media Panel

Reported by: grahamarmfield Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 3.5.1
Component: Media Keywords:
Focuses: accessibility Cc:

Description

Linked to #23560 this ticket specifically concerns the speech recognition user's accessibility experience of the Add Media functionality.

I'm using Dragon Naturally Speaking with IE9 on Windows 7 - a typical setup as Dragon works best with IE.

Within the Edit Post screen I can use Dragon to action the Add Media link successfully. The command in Dragon for such an action is "Click Add Media". This works, but then I run into the following problem:

  • With the exception of Set Featured Image, none of the other links on the panel appear to be directly accessible with Dragon.
  • If I select Set Featured Image I can't action any of the other links.

Dragon users can use voice commands to replicate pressing the tab key. The experience then mirrors that outlined in #23560 - but of course this cannot be used to select the images or other files.

It is possible for Dragon users to interact with screens using mouse commands but it is an incredibly laborious and time consuming process - used only as a last resort.

If one of the images is selected, the information panel for that images opens to the right. Unfortunately none of the input fields (for title, alt, etc) are directly available to Dragon. Ironically, the Insert Into Post button can be accessed directly with a voice command.

Some investigation needs to be done as to why most of the links and input fields cannot be directly accessed by Dragon when the panel is opened. This is a parallel with the situation on the Theme Customizer panel.

It is interesting that the Set Featured Image link and the Insert Into Post button can be directly accessed. What is different about them?

Change History (20)

#1 @toscho
6 years ago

  • Cc info@… added

#2 @sharonaustin
5 years ago

  • Cc sharonaustin added

#3 @nacin
5 years ago

  • Component changed from Accessibility to Media
  • Focuses accessibility added

#4 @tomauger
5 years ago

Graham, the Media Modal has significantly changed in 3.9 can you re-run your tests and update this ticket?

This ticket was mentioned in Slack in #accessibility by rianrietveld. View the logs.


5 years ago

#6 @joedolson
4 years ago

  • Keywords needs-testing added

Graham - if you could re-test this, that would be great.

#7 @swissspidy
3 years ago

  • Keywords close added

This ticket was mentioned in Slack in #accessibility by rianrietveld. View the logs.


3 years ago

#9 @joedolson
3 years ago

  • Keywords close removed

We're going to have this checked over by the accessibility testing team to see where we stand on this question.

This ticket was mentioned in Slack in #accessibility by rianrietveld. View the logs.


3 years ago

#11 @afercia
3 years ago

Definitely needs to be re-tested after all the relevant changes in the last months and before we can make a decision and a schedule for a future release.

This ticket was mentioned in Slack in #accessibility by rianrietveld. View the logs.


3 years ago

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


3 years ago

#15 follow-up: @afercia
3 years ago

  • Keywords needs-testing removed
  • Milestone changed from Awaiting Review to Future Release

Either we should make an action plan or close this ticket :) Moving it to Future release, as it is something that at the very least needs a decision.

#16 in reply to: ↑ 15 @GrahamArmfield
3 years ago

Replying to afercia:

Either we should make an action plan or close this ticket :) Moving it to Future release, as it is something that at the very least needs a decision.

I think there is a piece of work being done to improve media - I read about it on the core blog or WP Tavern (can't remember which).

Maybe efforts should be made to influence that in an accessible way rather than making specific changes to existing functionality which may get trashed in the next major release or one after.

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


3 years ago

#18 @iseulde
5 months ago

  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

This ticket has not seen any activity in over *two* years, so I'm closing it as "wontfix".

The ticket may lack decisiveness, may have become irrelevant, or may not have gathered enough interest.

If you think this ticket does deserve some attention again, feel free to reopen.

For bugs, it would be great if you could provide updated steps to reproduce against the latest version of WordPress (5.0.2 at the time of writing). Remember images or a video can be superior to explain a problem. At the very least, quickly test again to make sure the bug still exists.

If it’s an enhancement or feature, some extra motivation may help.

Thank you for your contributions to WordPress! <3

#19 @JeffPaul
3 months ago

  • Keywords bulk-reopened added
  • Milestone set to Awaiting Review
  • Resolution wontfix deleted
  • Status changed from closed to reopened

A decision was made to reopen tickets that were closed in the bulk edit that this ticket was affected by. This ticket is being placed back into the Awaiting Review milestone so it can be individually evaluated and verified to determine if it is still relevant/valid or reproducible.

#20 @afercia
2 months ago

  • Keywords bulk-reopened removed
  • Milestone changed from Awaiting Review to Future Release
Note: See TracTickets for help on using tickets.