/WAI/TechSupport

From W3C Wiki

This page describes some of the tech support that WAI desperately needs. 

status of this page: some updated 17 September 2022

How PWDs Use Web coding

Task:

Time estimate, rough:

  • ? 0.5-1.0 FTE for a couple days

Schedule:

  • Can start anytime
  • EOWG plans to publish update mid-2023

Technical Requirements:

  • ? Jekyll with liquid templating and includes
  • ? GitHub

Notes

  • WAI News has an "all on one page" option. Possibly we can use some of that coding?

Updating Quick Ref

Quick Ref current, QuickRef Documentation

This is updating an existing web app, with mix of front end code and static back end.

Schedule:

  • Ready now
  • Needed now for WCAG 2.2, mid-April at the latest.

Tasks:

  • [high] Update for WCAG 2.2
    • Michael created a new JSON. We need to update the UI and code to add Filters for WCAG 2.2.
    • Need changes to deal with obsolete SC
  • [medium] Address pull requests and issues in GitHub (some of which might be in the JSONs rather the the QuickRef itself), versions of WCAG support docs linked to
  • [low] revise to use new visual design and code

Time estimate, rough:

  • update for 2.2: 0.5-1.0 FTE for a couple - few days
  • address issues: 0.5-1.0 FTE for a couple - few days
  • revise to new design: many weeks

Technical Requirements:

For update:

  • GitHub, Jekyll, Node, JSON

For redesign:

  • Accessibility expertise developing with HTML, CSS, WAI-ARIA, JavaScript
  • Ability to test on multiple platforms, devices, browsers, and assistive technologies
  • ?Svelte
  • ?Netlify serverless functions

WAI website build and deployment

This requires detailed knowledge of the WAI static website architecture as well as the technologies used to build and deploy the live site and previews.

Tasks:

  • understanding the current website architecture and improving it. This is a large Jekyll static site with many GitHub repos using git submodules and symblinks
  • understanding the use of Jekyll abstractions such as collections, includes, CSS and frontend JavaScript that make up the WAI Website Theme
  • understanding the Netlify previews via GitHub integration and deploy to GitHub Pages using GitHub Actions
  • integration and publication of new resources (e.g., several of the WAI-CooP deliverables, new translations) and updates from "Improving WAI website code" below
  • supporting process for form submission to GitHub Pull Request

Time estimate, rough:

  • 0.5-1.0 FTE for a few weeks
  • 1-3 days every 1-3 months

Technical Skill Requirements:

  • including skills for "Developing WAI website"
  • Git including submodules,
  • basic Linux bash including symbolic links ("symlinks")
  • GitHub, GitHub flow and protected branches, Workflows (Actions), GitHub Pages
  • Netlify (existing skill or ability to learn) Deploys, GitHub integration for Continuous Integration, Functions, basic build settings
  • many aspects of Jekyll with Liquid templates, especially Jekyll configuration options and file processing, plug-ins
  • local development as well as netlify builds and GitHub Action build

(note, accessibility expertise not needed)

Developing WAI website

This is static web site site development using the existing tools and architecture

Tasks:

  • updating individual pages (some could hopefully be done across the site with scripts or such, some might mean touching all pages)
  • updating the shared HTML, CSS, ARIA of WAI website theme and layout templates (5-year-old code has accessibility issues now, some minor CSS issues)

Time estimate, rough:

  • 0.5-1.0 FTE for a few weeks

Technical Requirements:

  • Accessibility expertise developing with HTML, CSS, WAI-ARIA, JavaScript
  • In-depth knowledge of web accessibility requirements across different types of disabilities, and of assistive technologies
  • Ability to test on multiple platforms, devices, browsers, and assistive technologies
  • Jekyll with liquid templating and includes (existing skill or ability to learn)

[covered!] Updating Tutorials

August 2022 update: EOWG participant has taken this on! will leave here just in case need it for the future

Tasks:

Time estimate, rough:

  • 0.5-1.0 FTE for a few weeks
  • 1-3 days every month

Technical Requirements:

  • In-depth knowledge of web accessibility requirements across different types of disabilities, and of assistive technologies
  • Ability to test on multiple platforms, devices, browsers, and assistive technologies
  • Accessibility knowledge in HTML, CSS, WAI-ARIA, JavaScript

Translations for new resources

e.g., COGA Supplemental Guidance is being translated into Japanese

@@ shawn to add info here...

WCAG Techniques and Understanding

lower priority:

  • use standard WAI site components
  • remove dependency on Michael

Related info

Retrieved from "https://www.w3.org/wiki/index.php?title=/WAI/TechSupport&oldid=116066"