I’m working on ensuring that our custom Omeka theme is in compliance with accessibility guidelines, and I’ve run into a snag. One of the things that’s required is that markup signal to assistive technologies the language of the content. I already have the appropriate tagging in place to designate all pages overall as US-english. However, some of our records contains spanish-language metadata. Often, those records will have two title, description, and subject fields, one in spanish and one in english. I need to signal to assistive technologies that some of the page content is in spanish, not english, as is the rest of the page. This would be simple if the content was not auto generated from the database, I’d just wrap it in a tag and set the “lang” attribute to the appropriate value. But that won’t work here because the content is auto-populated into the page template.
My inital solution was to try wrapping tags around the metadata itself in our CSV spreadsheets, and than marking it as HTML in the CSV import, but to my surprise, I discovered that the CSV import plugin seems to strip off any “lang” attributes of any tag loaded.
Is there a better solution? Is there a solution at all? How do I mark up foreign-language content on Omeka pages for assistive technologies?