Hi,
I may have solved my own problem.
It turns out, in MLA, you separate the XMP namespace from the field name with a dot.
So, I have a content template for the new IPTC Alt Text (Accessibility) field that looks like so: template:([+xmp:Iptc4xmpCore.AltTextAccessibility+]) and it appears to be working.
For Extended Description (Accessibility) I have : template:([+xmp:Iptc4xmpCore.ExtDescrAccessibility+])
This is great news. Any WordPress user who needs to map contents of the new IPTC fields into pages or posts can use your plugin. Issue solved! (At least this part of the issue. Disabled people still need to be able to access the data. I’m not really qualified to speak to that half of the equation.)
Thanks for your positive comments on the plugin and for your question; thanks as well for finding the solution yourself before I could respond.
The IPTC support in MLA is based on a PHP library function that hasn’t been updated for the newer IPTC 4 extensions. However, the new data is stored in XMP format and you can get it from there. As you discovered, the xmp:Iptc4xmpCore. prefix gets you to any of the new fields.
You can use the new “Attachment File Metadata” meta box on the Media/Edit Media screen to inspect all of the IPTC, EXIF and XMP data and get the right syntax to access them in MLA applications.
Thanks for posting your solution and for your interest in the plugin.