Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing templates / reusable widgets; responsibility for 3rd party content #948

Closed
sajkaj opened this issue Nov 11, 2019 · 1 comment
Closed
Labels
Challenges with Conformance Issues relating to the document at https://w3c.github.io/wcag/conformance-challenges/

Comments

@sajkaj
Copy link
Contributor

sajkaj commented Nov 11, 2019

Detlev Fischer on October 14 commented on:
[https://w3c.github.io/wcag/conformance-challenges/#challenge-3-3rd-party-content](Challenge #3)
It can also provide / mandate user input templates (e.g. define a meaningful heading, require alt text of uploaded images) to constrain the well-formedness of user-generated content to some degree? Most of the issues
coming from this corner seem comparatively minor compared to faults with navigation, with dynamic widgets / focus handling, form markup & error handling etc.
|| ||
For third parties in terms of advertisers, the site owner can publish and enforce entry criteria (e.g. "we only accept ad animation no longer than 5 secs OR a control to stop it"). My guess is that it is profit
interests, not technical limitations, that may stop site owners from imposing such third-party content rules.
|| ||
Alastair Campbell on October 14 commented:
I think the guidelines need to stay neutral about what entity would be responsible, all they can evaluate is whether the interface for the user is accessible. In the UK/EU responsibility comes from the
legislation/regulations, the guidelines are the measure.
|| ||
Jake Abma on October 15 commented:
is it always up to third parties? Great example is the BBC which provides accessibility guidance for third parties they MUST follow or otherwise be excluded.
|| ||
Alastair Campbell on October 15 commented:
That is to be encouraged, but some locations have laws that define it, so we shouldn't.

@sajkaj sajkaj added the Challenges with Conformance Issues relating to the document at https://w3c.github.io/wcag/conformance-challenges/ label Nov 11, 2019
@detlevhfischer detlevhfischer changed the title Detlev Fischer on October 14 commented on: I would argue that if a page consists largely of self-contained building blocks and a strategy is in place to quality control these building blocks (say, will a any pop-up get and trap focus, and on closing, return focus to the trigger?) those permutations should not create serious accessibility issues? I'd be interested in large site case exampes where permutations make it in principle impossible to conform in the WCAG 2.X sense. (I can see issues around consistent heading structure when building blocks are re-used in different contexts since the outline algorithm did not take off, but those issues are unlikely to be show-stoppers - there are probably techn. solutions to that?) Testing templates / reusable widgets; responsibility for 3rd party content Nov 14, 2019
@sajkaj
Copy link
Contributor Author

sajkaj commented Dec 3, 2019

Merged into 943

@sajkaj sajkaj closed this as completed Dec 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Challenges with Conformance Issues relating to the document at https://w3c.github.io/wcag/conformance-challenges/
Projects
None yet
Development

No branches or pull requests

1 participant