This Wiki page is edited by participants of the Cognitive and Learning Disabilities Accessibility Task Force. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Task Force participants, WAI, or W3C. It may also have some very useful information.

FTF issues and agenda

From Cognitive Accessibility Task Force
Jump to: navigation, search

Issues so far

what should a wcag extension be? They will be normative

wearables and mobile interaction, what is the interaction, will they make disabilites worth

internet of thinkgs

google translates makes things confucing or incorrect messuring readibilty. - wcag technice of SC v techniques

tweek the voice ml solution for practical purposes.


terms use may be readdressed. - follow up with our glosary develop techniques across interfaces

JSON scrips issues

should it be REST or cookie or HTTP attribute ?

inject AT settings and prefrences such as font size.

missed out

Review of table of cognitive functions

Agenda

Tuesday, 21 April 2015

Morning

9.30. Coffee and equipment check

10.00 Orientation

  • Meeting technologies, issues page, agenda review
  • Our deliverables and how they fit together
  • Our technologies - wiki, github etc
  • WCAG and PF

Gap analysis 1

  • Tree
  • Table of content for gap analysis (and part of roadmap)
  • Review edit methodology for gap analysis,

11.30 - 11.45 Break

Gap analysis 1 (cont)

  • Testing methodology against the techniques and issue papers.
  • Update

1.00 - 1.30 Lunch

Afternoon

1.30 - 3.00 User research document

  • Restructure of the user research document,
  • Review of table of cognitive functions, feedback.
  • How we do citations with worked example

3.00 - 3.15 Break

3.15 - 4.30 GPII and adaptable content

  • what is supported and deployed?
  • holes in semantics and support
  • portable web preference

4.30 - 4.40 Break

4.40 - 5.30 Techniques

  • Restructure the document?
  • User testing
  • What do we still need? Brainstorming solutions for numbers on the web

Wednesday, 22 April 2016

Morning

9.30. Coffee and equipment check

10.00 Techniques

  • Restructure the document?
  • User testing
  • What do we still need? Brainstorming solutions for numbers on the web


Gap analysis 2

  • Re-review draft of TOC - after new experience what is missing?


11.30 - 11.40 Break

Issue papers:

  • What do we still need as full issue papers? What issue papers are week?
  • Brainstorming solutions in issue papers

If time: Perform more Gap Analise, against the techniques and issue papers.

1.00 - 1.30 Lunch

Afternoon

1.30 - 3.00 Road-map.

  • Identify next steps for road-map. What do we want to go in?
  • Road-map TOC

Set schedules and next steps

  • Current deliverables
  • Gap analysis
  • Road-map

3.00 - 3.10 Break

3.10 - 4.30

Discussion on Symbols and adaptable content - possibly with guests

  • What do we have, and what pieces are missing?
  • Update schedules

4.30 - 4.40 Break

4.40 - 5.30

Outstanding issues

Recheck: Next steps and assign actions