Notes from brainstorming in California - March 2019
dynamic description:
designed complexity disconnect to implementation complexity. How to map communication tighter
complexity of learning description
preview while designing descriptions
complexity of design doc, metadata mixed into actual descriptions
How to know that things don't break
JG: what about test driven development for descriptions
potential solutions. note not all solutions fix all problems (lightly ordered from easiest to hardest)
make "static" a11y strings available to designers to change, run the sim, then commit. Organizing a11y string files so that it is obvious to designers what can be changed safely and easily.
"simpler" design doc?
BASE like tests when needed to ensure that descriptions don't change.
google form for implementing simple static descriptions
description course as an assistant in onboarding
a11y view with "blanks" to fill in descriptions,
perhaps machine readable output (like phet-io studio work)
"preview" button seems key
Notes from brainstorming in California - March 2019
dynamic description: designed complexity disconnect to implementation complexity. How to map communication tighter complexity of learning description preview while designing descriptions complexity of design doc, metadata mixed into actual descriptions How to know that things don't break JG: what about test driven development for descriptions
potential solutions. note not all solutions fix all problems (lightly ordered from easiest to hardest) make "static" a11y strings available to designers to change, run the sim, then commit. Organizing a11y string files so that it is obvious to designers what can be changed safely and easily. "simpler" design doc? BASE like tests when needed to ensure that descriptions don't change. google form for implementing simple static descriptions description course as an assistant in onboarding a11y view with "blanks" to fill in descriptions, perhaps machine readable output (like phet-io studio work) "preview" button seems key