Working on Section 508 compliance for a website, and our tests trigger warnings on the lack of a title on the iframe created by the oembed, and the lack of noframes content. I’m just starting with accessibility, and know that in some cases things that trigger warnings may not be actual problems that need to be fixed, but wasn’t sure in this case.
I guess I’m trying to say that the developers who setup oembed are way smarter than I am, so I’m betting it’s not an issue – but need to find out.
You may want to bring this up with the WordPress accessibility team over at http://make.wordpress.org/accessibility/ but I’m pretty sure that modern screen reader software is quite capable of handling iframe content and that it’s really Section 508 that needs bringing up to date. 🙂
What, a government regulation that needs brought up to date? Couldn’t be! And yeah – was looking to see if anyone had a definite answer before I bothered them. 🙂
Thanks for posting this.
We discussed this issue in the Accessibility team chat.
Joe Dolson investigated this and his conclusion was the following:
I don’t believe that WordPress provides the iframe if there is one; that appears to be provided in the rich OEmbed object received from the source. In which case, if there’s a problem, it’s not one that can be easily fixed by WordPress.
Hypothetically, WP could filter the HTML returned in the OEmbed object to add a title, but that would be some very fragile code, dependent on the source API not changing their HTML. Probably not a good idea to attempt.
So this is out of WordPress hands I’m afraid.
- The topic ‘oEmbeds and Accessibility’ is closed to new replies.