Trac Tickets – the band’s taking requests

At the beginning of the past few releases or so, we’ve put a call out for community priority tickets. There are over 3000 tickets in Trac. If there’s a ticket you feel is neglected or should have light shined upon it: leave a comment here with a link so we can triage it. Help us help you.

I just added two new tickets:
Adding an image option to the post category: #31197 (which is depended on having #10142 – Add metadata support for taxonomy terms taken care of.)
and adding duplicate/clone option to the quick edit bar: #31198

Would be great if #30415 could be added in – it adds more logical and robust functions to taxonomies and doesn’t affect backwards compatibility at all, so there’s no reason not to include it really 🙂 My patch works 100%, but I’ll refresh it for 4.1 to make sure it’s all up to date.

Also, #26948 – it adds an argument to register_taxonomy() that allows you to set whether the taxonomy should display in the quick/bulk edit panel or not. Once again – it doesn’t break backwards compatibility, plus it already has a number of core committer’s give feedback. I’ll also refresh the patch for 4.1, but I doubt anything will change.

#16987 because we really would like to have a possibility to use a derivation of wp_list_table for custom post types and don´t want to stumble upon hardcoded capabilities, filters…. and this would be a benefit for many others, I think.

If we take a look at this six year old ticket. https://core.trac.wordpress.org/ticket/7580 almost all photographer use IPTC data and we created a plugin that pulls in the IPTC data right into the caption, The less manual entry the better right?

But their a is big question associated with this ticket. Do we populate just the caption? Or do we include the alternative text and / or the description field as well.

I’ve spoken / chatted both with Morten Rand-Hendriksen and Joe Dolson about captions with photos and IPTC integration. Joe really hazard to put the caption into all three fields as it was just repeating itself to the screen readers and suggests we use a aria-describedby. I do agree with his statement that we don’t want to repeat the same information over and over again just to fill a field. You can see the original public conversation here: https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2014-04-30&sort=asc#m843702

But isn’t that already what were doing in Line 716 in the media.php file linked above?

The ticket was made the high in priority way back when and I tried to get it nominated for a patch in v4.0. But I don’t have the knowledge to integrate this into core. I have open sourced the caption mapping plugin we created here: https://github.com/robertdall/iptc-caption-mapping

It auto populates the caption, alt and description for example purposes only.

It would be proper if we could map the IPTC ( International Press Communication Council ) description field to our caption field as the description field is defined by the IPTC as: “A textual description, including captions, of the item’s content, particularly used where the object is not text.” So it is a description of photo or a caption.

But as I mentioned above what’s left to be discussed is do we want to implement use of aria-describedby for the alternative text and / or description? Or should that be left to the themers to decided. I also believe this investigation would make WordPress more accessible in the use of images and captions.