[wp-trac] [WordPress Trac] #47456: Improve the user interface to ensure correct usage of the image alt text

[WordPress Trac]

#47456: Improve the user interface to ensure correct usage of the image alt text
-------------------------------------------------+-------------------------
 Reporter:  afercia                              |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  high                                 |   Milestone:  5.4
Component:  Media                                |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  wpcampus-report needs-design-        |     Focuses:
  feedback needs-patch                           |  accessibility
-------------------------------------------------+-------------------------

Comment (by joedolson):

 Just thinking about some of what would need to be done for this, it's a
 pretty substantial challenge:

  - Need to be able to account for multiple uses in a single instance.
 E.g., a featured image used on the single post screen serves a different
 purpose than a featured image linked from an archive page. There would
 need to be a way that themes could define how a featured image is used by
 the theme. Or would we pre-define a set of use cases (that could be
 extended), and provide different arguments to fetch an image based on use
 case?
  - Need to have alt texts stored for programmatic access: for a featured
 image, that could be several post meta entries.

 Handling alt attributes in posts is relatively trivial; the inserter
 places the image in a direct context that can be decided on at the time.
 Programmatically associated images would be much, much harder to handle -
 both the software and the user would have to have a full understanding of
 where an image would show up and how it would be used in each case.

 There are a lot of mechanisms that would need to be created to make that
 work - the editor interface is relatively trivial, but usages of media
 outside of post content raise a lot of questions.

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