Scope of "Third Party Content" about wcag HOT 9 CLOSED

I have provided fixes for developers for the "like" button... I've asked developers to add the title attribute to the youtube iframe. If they can't fix it I'd say it is a statement of non conformance which means it does not conform but it would if these things were removed... here's the statement.

http://www.w3.org/TR/2008/REC-WCAG20-20081211/#conformance-partial

from wcag.

Focussing on the business case primarily and saying to anyone who is providing TPC that it must meet a certain standard before it will be included. This could be as simple as making titles mandatory on iFrames (as DavidMcD points out) - to captioning video etc. My point is make it about the business case, and not explicitly about a11y - this is a way to get a11y in via the backdoor.

from wcag.

If they can't fix it I'd say it is a statement of non conformance which means it does not conform but it would if these things were removed... here's the statement.

That is the point. If we could make a partial conformance claim (= non conformance), we can use these things even if they have an accessibility issue. If not, we may have to give up using these things in order to make a conformance claim or eliminate the web pages from the scope for the conformance claim.

WCAG is ambiguous and it results in different interpretations. Some developers say "This is not under our control and can be updated automatically without notice. So we can regard it as the Third Party Content". Other developers say "If we find an accessibility isuue, we should fix it. If we can't, we won't make even a partial conformance claim and we have to give up using this."

I'd like the working group to draw a line and add some specific examples to the Understanding document to clarify the line.

from wcag.

I think that the has drawn the line with the partial conformance statement that David cites. To conform to WCAG you can't have non-compliant content for any reason, but for partial conformance you can have non-compliant content provided that it is truly out of your control. Whether a particular country's policy allows partial conformance is up to the policy makers in that country.

Looking at a specific example, a developer needs to evaluate whether a facebook "share" button is developer-configurable and can be made accessible, or if it is 3rd party content that they can't control.

https://developers.facebook.com/docs/plugins/share-button has the information and it tells me that I need to add a div that contains a reference to the Facebook script source, and that I also need to add a div which will ultimately contain the button, but then at runtime the button div is modified by the script at runtime.

It seems that even if your average author could make modifications to the resulting code that is generated in order to improve the accessibility, he wouldn't know if or when the code that is generated might change and possibly break the improvements.

On the other hand, a developer who uses the Facebook API to build accessible buttons (or uses an alternate 3rd party solution) should be able to avoid accessibility problems.

The question seems to be "what level of pragmatism is appropriate for allowing authors to claim partial conformance?"

from wcag.

The question seems to be "what level of pragmatism is appropriate for allowing authors to claim partial conformance?"

What about the following?

When a third party content (e.g. social plugin, video player, interactive map) has an accessibility issue and an author want to embed it in a web page;

• If an author fix it, then conformance claim can be made.
• If an author can't fix it or use it as it is, then the statement of partial conformance (= non conformance) can be made.

It seems to be almost impossible for us to define "level of pragmatism". So this could be a simple solution. If you want to make a conformance claim, you must fix it by yourself. If partial conformance is acceptable for you, you can use the code provided by a third party as it is and make the statement of partial conformance.

from wcag.

@lorettaguarino has taken an action item to draft response to this:

http://www.w3.org/WAI/GL/track/actions/308

from wcag.

Proposed response:
We are adding a new section to Understanding Conformance to discuss partial conformance - third party content. The proposed addition can be found at https://www.w3.org/WAI/GL/wiki/Understanding_Partial_Conformance_-_Third_Party_Content

from wcag.

RESOLUTION: Understanding Partial Conformance - Third Party Content
When an author makes a decision to use a third party implementation, they should choose products that meet WCAG requirements. If all content on a page, including third party content, meets all WCAG success criteria the page conforms to WCAG. However, if the page does not conform to WCAG only for reasons that are legitimately outside the author's control then the author can make a claim of partial conformance. It is important to recognize that this is a statement of non-conformance and there are users who will not be able to access some of the content this page.
One reason that content may be outside the author's control is because it is being provided by a third party (blogs, portals, news sites). Web pages may also include content via third party libraries, plugins, or widgets.
Be sure to monitor any content that can change without approval from the web page author, as a page which once conformed may suddenly fail to conform. If it is not possible to monitor and repair the third party content, it may be possible to identify the non-conforming parts of the page to users. If the rest of the web page conforms to WCAG, such a page qualifies for a statement of partial conformance, third party content.
https://www.w3.org/WAI/GL/wiki/Understanding_Partial_Conformance_-_Third_Party_Content#Understanding_Partial_Conformance_-_Third_Party_Content

from wcag.

Add section to: http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html

Section to be in "Understanding conformance claims section and immediately precede "Information about any additional steps taken that go beyond the Success Criteria" heading.

aa79702?diff=split

from wcag.