w3c / wai-about-wai Goto Github PK

See Requirements Analysis, particularly User Scenarios.

What might we want to title this page? Think from the user perspective...

All brainstorms welcome! — including ideas you don't really like, and list here to help generate ideas from others :-)

What might we want to add, delete, or change in the Requirements Analysis for What WAI is Working On?

(Please put comments on the page title in separate Issue 127.)

Note: the Requirements Analysis is an internal document so we do not want to spend effort wordsmithing or polishing, or including every possible detail.

Reviewing https://w3c.github.io/wai-about-wai/about/translating/

Qualifying accessibility/disability or translation organizations

I suppose there is a typo as I can't figure out what this means as it is now; in paragraph “Links to organizations. (Exception: Qualifying accessibility/disability or translation organizations. To request an exception, e-mail [email protected] with subject [Translations link request].)”.

Please publish the recordings and the transcripts of the symposium

rel: w3c/wai-translations#22

The link to the ARIA group https://www.w3.org/WAI/about/groups/aria/ is a 404.

Does the group still exist?

This looks great! It flows right in with the rest of the content, thanks for sharing and for the work you do.

Contribution of truth: listening to, engagement, transparency, good will , love. All acts of no fear. Every connection must know truth.

Link to: https://www.w3.org/WAI/standards-guidelines/wcag/translations/
From: https://www.w3.org/WAI/about/translating/
Rationale: make it easier to find

Is the groups page that lists task forces an old page that needs deleting? If it is still a valid page, it needs a bit of updating.

• WCAG working group is now AG WG.
• It is missing the re-established WCAG2ICT task force under the AG WG. A description of this TF is:

The objective of the WCAG2ICT Task Force is to develop documentation describing how WCAG 2.x and its principles, guidelines, and success criteria could apply to non-Web Information and Communications Technologies (ICT).

• Is the SVG task force still active? The SVG TF link goes to yet another old page that lists Rich Schwerdtfeger as a contact. He hasn't been involved in W3C for quite some time now.

I imagine that some of the other TF sub-pages are out of date as well.

Comment below on [DRAFT] Accessibility Work at W3C

Or, start a new issue with Assignee @shawna-slh

Small question:
« WAI remercie ces traducteurs, » implies we have several translators for the present document, yet most documents are translated by one person. In French it sounds a bit awkward. (And I'm guessing it's the same in most languages.)

What about saying: “WAI thanks translators” which would be translated then to « WAI remercie les traducteurs »?

👋 The redesign is coming to this repository soon. (Hooray! 🎉) We need to check off several steps before we can link your content to the redesign repository. I marked some of the steps with RM meaning Resource Manager. Others are marked with @yatil, and I’ll do/help you through the technical parts.

In addition to this issue, you might find other issues in your repository that are labeled with wai-redesign-before that should be addressed/resolved before the redesign. That might mean to postpone working on it until after the redesign (use the label wai-redesign-after for those issues).

• Content is updated and ready to be put into the new design. (RM)
  • The best case scenario would be that the content is ready before doing step three below. However, that might not be feasible in every case, so @yatil might do the next step before the content is ready and just port the content that is available to him.
  • Once done, add label wai-redesign-content-done.
• Tech Create branch/repository with the new structure (@yatil)
  • For simple resources (separate pages/pages that don’t need a left navigation), you will find the documents in the root directory of the repository.
  • For more complicated resources, @yatil creates a Jekyll collection which adds the left sidebar navigation amongst other things. You will then find your files in a folder called _resource_name.
  • Documentation should be available in the w3c/wai-website wiki soon.
  • Once done, add label wai-redesign-repo-done.
• Content Use current content and port it to the new design (@yatil)
  • Once this is done, all previews will be in the new design.
  • Once done, add label wai-redesign-content-ported.
• Content Check if content renders well, make changes as needed/wanted. (documentation) (RM)
  • Once done, add label wai-redesign-content-checked.
• Tech Link this repository to the w3c/wai-website repository (@yatil)
  • Once done, add label wai-redesign-repo-linked.
• When all checkpoints above are checked, close this issue.

https://www.w3.org/WAI/about/projects/wai-tools/

D3.1: Accessibility Statement Generator — open source tool, possibly extending the WCAG-EM Report Tool , to assist the creation of accessibility statements.

WCAG-EM Report Tool -> https://www.w3.org/WAI/planning/statements/generator/#create