Writing Outcomes as User Needs

Writing Outcomes as User Needs

Basic Information

Primary Point of Contact: Jeanne Spellman and Accessibility Guidelines Working Group Planning

Assigned to: Silver Task Force

IRC channel: [https://irc.w3.org/ irc.w3.org] channel:#silver

Friday 10:00AM ET - Zoom Call Info (requires password)

---

== Current Work ==

• Writing Outcomes as User Needs - presentation to AGWG
• Alt Text example
• Audio example
• Alt Text - Writing Outcomes as User Needs
• Alt Text Flows Organized into 7 categories

== Minutes ==

== Issues and Comments == [https://github.com/w3c/silver/milestone/(topic number) Issues relating to (Topic)]

== Referenced Research ==

• Silver Archives These are links to the work that has already been done related to writing process and identifying user needs. It has been updated with the flow analysis that the Errors group pioneered. WCAG to Silver Migration Outline Map - document produced by the SIlver F2F meeting of 12 March 2019 that roughly groups existing WCAG 2.0 Success Criteria by user need.

• Template for Content Creation Process - this is the template for starting all new guideline work. The Part 1 Define Flows and User Need is applicable to this exercise.

• Content Creation Process for Migrating WCAG SC - This gives the instruction for the template. It includes the step by step process that the Errors group did to Inventory User Flows, Identify User Action, Common User Needs, Unique User Needs, Functional Needs, and List of Barriers encountered by different groups. (I note that this could be useful for developing critical errors.)

Guideline User Need Analysis documents:

• Alt Text Guidance - SCOPE EXPLORATION - This is the early work that Makoto's group did to identify user needs. Keep in mind, that Makoto was requested to make minimal changes to 1.1.1, so his group deliberately doesn't have the depth of analysis that Errors Group did.

• Visual Contrast of Text Wiki page: Who What When Where How - The Visual Contrast group did not follow the template of identifying user needs. This seems to be the most useful page for identifying user needs.

• Headings Test by Functional Needs - this doesn't seem to be finished, but is a start at identifying user needs from Functional Needs list. Proposal for including ACT definitions with Outcomes - has the list of User Needs.

• Captioning User Requirements - The XR group did their work in Github. This page lists the user requirements with links to the issues behind them. Captioning - Functional Outcomes and XR Captioning - How TO may also be useful.

• Clear Language Scope Exploration - early work that Clear Language group did related to User Needs. They may have more up to date documents as well.

• Errors Working Documents - This is the list of documents that Errors created. Errors User Needs Worksheet is the spreadsheet of their work.

== Key Decisions Agreed On with Date ==

== Working Document History ==

== Participants == Silver Task Force