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

Proposed updates to the WCAG2ICT work statement #942

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

maryjom
Copy link
Contributor

@maryjom maryjom commented Oct 31, 2024

Preview

This is to update the work statement for phase 2 work remaining.

This is to update the work statement for phase 2 work remaining.
Copy link

netlify bot commented Oct 31, 2024

Deploy Preview for wai-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit c1d6c41
🔍 Latest deploy log https://app.netlify.com/sites/wai-website/deploys/673f5f9be2839a0008100ddf
😎 Deploy Preview https://deploy-preview-942--wai-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 71 (🔴 down 26 from production)
Accessibility: 100 (no change from production)
Best Practices: 92 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

@ChrisLoiselle ChrisLoiselle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @maryjom I read through this and it reads well. I won't approve until we talk through it on the upcoming task force call.

@maryjom
Copy link
Contributor Author

maryjom commented Nov 1, 2024

Hi @maryjom I read through this and it reads well. I won't approve until we talk through it on the upcoming task force call.

@ChrisLoiselle This extra markup is handled by the W3C website rendering/processing as it was already in the file and then appears on the rendered page as the table of contents at the top of the page. I don't know how to get a view that is the rendered content in my branch.


Explicitly out of scope for the WCAG2ICT Task Force work are:

* proposing changes to WCAG 2.x;
* developing techniques or interpretations of WCAG 2.x for implementing WCAG 2.x in Web technologies;
* developing any specific, sufficient techniques, including platform-specific techniques, for implementing WCAG 2.x in non-Web ICT, though examples may be in scope;
* determining whether WCAG, as a whole, _should be_ applied to non-web content; and
* determining whether WCAG, as a whole, _should be_ applied to non-web content;
* providing a determination of which success criteria are applicable to a particular non-web technology; and
Copy link
Contributor

@bruce-usab bruce-usab Nov 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am of the opinion that line 55 should be moved to in scope! (But maybe soften "determination" to "recommendation"?

Copy link
Contributor Author

@maryjom maryjom Nov 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am trying to schedule a meeting between AG WG chairs, WCAG2ICT co-facilitators, and hopefully at least Kevin White (for the WAI perspective) to see what leeway we have. Tentatively, it's on Monday 18 Nov.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bruce-usab Per the 18 November discussion with the AG WG leadership on changing the scoping and the TF discussion of changes on 21 November, I've made adjustments to the in scope and out of scope bullets.

Copy link
Contributor

@bruce-usab bruce-usab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Delete line 55 (which is to say, do not add it work statement).

To scope of work, and bullet something like:

To the extent determined by TF, provided recommendations as to which success criteria are not applicable to a particular non-web technology

@bruce-usab
Copy link
Contributor

I am strongly of the opinion that work statement should/could be revised so as not to preclude guidance similar to:

2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated in software.

See the [21 Nov. meeting minutes](https://www.w3.org/2024/11/21-wcag2ict-minutes.html) for details of what was discussed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants