W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > August 2014

Re: Social Media Buttons ( LC-2941)

From: <akirkpat@adobe.com>
Date: Tue, 05 Aug 2014 16:05:05 +0000
Message-Id: <E1XEhEX-0006xA-Hn@jessica.w3.org>
To: makoto.ueki@gmail.com
Cc: public-comments-wcag20@w3.org
 Dear makoto.ueki@gmail.com,

The Web Content Accessibility Guidelines Working Group has reviewed the
comments you sent [1] on the Last Call Working Draft [2] of the Web Content
Accessibility Guidelines (WCAG) 2.0 published on 11 Dec 2008. Thank you for
having taken the time to review the document and to send us comments!

The Working Group's response to your comment is included below.

Please review it carefully and let us know by email at
public-comments-wcag20@w3.org if you agree with it or not before 12 August
2014. In case of disagreement, you are requested to provide a specific
solution for or a path to a consensus with the Working Group. If such a
consensus cannot be achieved, you will be given the opportunity to raise a
formal objection which will then be reviewed by the Director during the
transition of this document to the next stage in the W3C Recommendation
Track.

Thanks,

For the Web Content Accessibility Guidelines Working Group,
Michael Cooper
W3C Staff Contact

 1. http://www.w3.org/mid/E1X53yX-00086F-3x@stuart.w3.org
 2. http://www.w3.org/TR/2008/REC-WCAG20-20081211/


=====

Your comment on Statement of Partial Conformance - Third Party Content:
> Name: Makoto Ueki
> Email: makoto.ueki@gmail.com
> Affiliation: 
> Document: W2
> Item Number: Statement of partial conformance - third party content
> Part of Item: 
> Comment Type: question
> Summary of Issue: Social Media Buttons
> Comment (Including rationale for any proposed change):
> Can "Statement of Partial Conformance - Third Party Content" be applied
> to social media buttons such as "Like!" button and "tweet" button?
> 
> In general, scripts and HTML codes are generated and provided by the
> social media. It is not content that is under the author's control as
> described in "Statement of Partial Conformance - Third Party Content".
> When putting these kind of buttons on a web page, authors can't change
> the scripts and codes.
> 
> For example, generated code for "Like!" button of Facebook is:
> 
> <button type="submit">
> <i class="pluginButtonIcon img sp_plugin-button
> sx_plugin-button_favblue"></i>
> </button>
> 
> This would fail under SC 4.1.2 as the name for the button can't be
> programmatically determined.
> 
> There is a social media button which uses CSS background image for the
> button and it fails under SC 1.1.1 as well. However authors can't change
> it.
> 
> This means any web pages which have these social media buttons can't
> conform to Level A.
> 
> I'm wondering if "Statement of Partial Conformance - Third Party
> Content" can be applied to these cases. 
> 
> Proposed Change:
> If "Statement of Partial Conformance - Third Party Content" can be
> applied, please add the information to Understanding document.


Working Group Resolution (LC-2941):
If the code required to include social media buttons does not enable any
modification by the page author, perhaps because the content is injected
dynamically much in the same way that occurs with many 3rd-party banner
advertisements used on pages, then the statement of partial conformance may
be applied to those areas.

It is also important to note that a page with a statement of partial
conformance for such a button does not conform to WCAG 2.0 Level A as a
result, and the statement of partial conformance helps to clarify this. 
Please see the Understanding document on Statements of Partial Conformance
for more information
(http://www.w3.org/TR/2008/REC-WCAG20-20081211/#conformance-partial).

However, not all social media buttons are created in the same ways, so  it
is impossible to say that all social media buttons will have this problem,
and it is important for authors to evaluate the accessibility of the button
options available and do their best to find options that will result in
accessible experiences for users.

----
Received on Tuesday, 5 August 2014 16:05:08 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 14 July 2018 08:23:16 UTC