W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > April 2015

Scope of "Third Party Content"

From: <noreply@w3.org>
Date: Tue, 21 Apr 2015 13:47:06 +0000
To: public-comments-wcag20@w3.org
Message-Id: <E1YkYW2-0005Y7-Jw@deneb.w3.org>
Name: Makoto Ueki
Email: makoto.ueki@gmail.com
Affiliation: Infoaxia, Inc.
Document: W2
Item Number: Statement of partial conformance - third party content
Part of Item: 
Comment Type: question
Summary of Issue: Scope of "Third Party Content"
Comment (Including rationale for any proposed change):
We need specific examples which can be applied to "Third Party Content". There can be the following issues.

1. Social plugins
Examples of issues including, but not limited to:
 - When Windows high contarst mode is on, the logo (icon) and/or the button label is invisible
 - When it uses the <iframe>, the title attribute is not provided or the value of the title attribute doesn't describe the contents of inline frame.
 - When "Timeline" widget is embedded in a web page and it includes an image, ALT text is not provided for the image.

2. Video player
Examples of issues including, but not limited to:
 - Controls (play/pause button, volume control slider, etc.) are not keyboard accessible.
 - Label/ALT text is not provided for each control.
 - Controls are invisible when Windows high contrast mode is on.


In many cases, they are not content that are under the author's control. Authors don't have any alternatives as the codes are officially provided from the third party they are using. For example, when they are using Twitter, there is no option. Authors have no choice but to use the plugin which is officially provided by Twitter even if they already found an issue to be fixed.

However, WCAG says "it is not possible to know at the time of original posting what the uncontrolled content of the pages will be." Authors can check if the third party content meet WCAG SC or not before they use it.  

Can we apply "Statement of Partial Conformance - Third Party Content" to them? 

Proposed Change:
We should have specific examples in "Understanding WCAG 2.0" to clarify what would be included and what would not be included. 
Received on Tuesday, 21 April 2015 13:47:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 21 April 2015 13:47:08 UTC