WAI/Website/Technical and Background Information

From W3C Wiki
< WAI‎ | Website
UPDATED information maybe be in the WAI Website Re-Architecture Project page (Google doc)

This page has information on how WAI tools are developed and implemented (links to documentation), what skills are needed to update them, and upcoming updates. Please feel free to add information or questions.

UPDATED information maybe be in the WAI Website Re-Architecture Project page (Google doc)

WAI Website Overall

WAI Website Manual includes technical info, guidance on creating new resources, design components, icon library, and more.

Info on work needed moved to W3C-Team-only page, Skills section

The following are not currently integrated in the WAI website deploy system:

  • WCAG Techniques & Understanding
  • Michael's WG and TF pages
  • Before-After Demo (BAD)

Translations

Translation documentation

Skills needed:

  • attention to detail
  • Javascript

Projects:

  • to All Translations page
    • [medium] add subtitle languages to https://raw.githubusercontent.com/w3c/wai-website/master/translations.md
      skills needed: JavaScript
      effort: probably small
    • [medium-low] add navigation at the top to the languages (Shawn to provide design skills)
      skills needed: JavaScript
      effort: fairly small
    • [low-medium] order and group resources like in the main IA/nav under each language -- at least for languages where we have a lot of them (e.g., Spanish and soon French)
      skills needed: JavaScript, other?
      effort: probably complex-ish project
  • [low-medium] Pull French translation of main navigation (Spanish done)
    skills needed: ? JavaScript
    effort: probably small
    (I think I know how to, ~Shawn)
  • [low] make it easier for translators to:
    • update the meta data -- e.g., the fill in the info in a simple form and that updates the meta data.
    • start a new translation.
      effort: medium
  • [low] For Video Intro page, provide way to add a subtitle file one place and it updates all the translated pages.
    skills needed: ? JavaScript
    effort: fairly small
  • [low] In the About this translation box, have the English stay in the same place. (not changes based on if outdated or not)
    skills needed: ? JavaScript
    effort: very small
  • [low] home page - enable translation of parts of it (Eric started, didn't finish)
    skills needed: JavaScript, other?
    effort: medium

WCAG 2 resources

/TR/WCAG, Understanding, Techniques

...

WCAG Supporting Docs Redesign

In-progress June 2022

WCAG QuickRef

Address open issues and pull requests asap

More info in https://www.w3.org/wiki//WAI/TechSupport#Updating_Quick_Ref

Lists with Filters

Laws & Policies List

resource: https://www.w3.org/WAI/policies/

Update ASAP to include known content updates. Coding/back-end effort and skill level: low?

Update in 2021 for WCAG 2.2. Effort and skill level: low?

from Hidde: "It’s all done in Jekyll, with custom JavaScript to make the filters work. Redoing in Svelte may be easier once one of the other lists is successfully ported and we’ve figured out the UI and code aspects of it."
from Shawn: "In addition to consistency, I suspect that a major motivation for updating it will also be to make the submission easier from a user perspective, and also make process of reviewing and updating submissions easier."

Evaluation Tools List

resource: https://www.w3.org/WAI/ER/tools/

documentation: https://github.com/w3c/wai-eval-tools/blob/gh-pages/README.md

status: update in progress throughout 2022 (WAI-CooP)

Courses List

Requirements Analysis for list of courses

status: update in progress throughout 2022 (WAI-CooP)

Authoring Tool Accessibility List

status: on hold; probably get active again in 2021 (WAI-Guide)

Report Tools

ATAG Report Tool

https://www.w3.org/WAI/atag/report-tool/

ATAG Report Tool documentation

Published. A few open issues -- a couple easy to fix and maybe some already addressed just not closers?

WCAG-EM Report Tool

https://www.w3.org/WAI/eval/report-tool/#!/

Published. A few open issues. Eric V team can address. Eric V team likely to update for WCAG 2.2.

Others

Before-After Demo (BAD)

https://www.w3.org/WAI/demos/bad/

An update to BAD was started in 2017, yet not finished. Judy managed and Bocoup did the design and coding. This is an EOWG resource.

Update as soon as feasible for visual design, WCAG 2.1, and maybe WCAG 2.2.

  • Effort and skill level: medium-high ?

Tutorials

Address open issues asap

See https://www.w3.org/wiki//WAI/TechSupport#Updating_Tutorials

Accessibility Statement Generator

https://www.w3.org/WAI/planning/statements/generator/#create

Update in-progress to prepare for translations. Expected completion: September 2020.

WAI website CSS other

Most fairly low priority (although getting annoying :-)

UPDATED information maybe be in the WAI Website Re-Architecture Project page (Google doc)