Guidance to Write at AccessU

I sent Jeanne a few suggestions for new topics to create test guidance 
for Silver (e.g. at AccessU):

It would demonstrate the value Silver adds, if the Editor's Draft 
includes guidance, methods, and conformance for: emerging technology, 
multiple ways to measure, personalization, task-based assessment, and 
overall guidance.  All in plain language.

If you could show all this, what more could W3C ask for?

For EMERGING TECH:
VR, AR or IoT - e.g. guidance on VR and vestibular disorders (warnings, 
alternative way to get content, partial immersion options, timer 
settings to limit use).

For MULTIPLE WAYS TO MEASURE:
SC rejected by COGA only due to inability to test with pass/fail,
or guidance on measuring/managing proxies/attributes of impact risk for AI

For PERSONALIZATION/CUSTOMIZATION:
address conflict use cases in email sent,
or guidance on consent and disclosure, especially with IoT/smart tech 
(opt-in/opt-out and granular control)

For TASK-BASED ASSESSMENT:
retail check-out process or travel planner related use cases
Why?  We need a piece of guidance and a method to test task-based 
assessment to demonstrate how this works.

For OVERALL GUIDANCE:
Accessibility Statement
Why?  It's fairly straightforward and gets overall guidance into 
architecture.  Plus it provides an opportunity to consider what is 
bronze, silver, gold level.

And for MIGRATING CURRENT SC:

Do the timing one! :)
Why?  It's AAA and shouldn't be.  It gets at COGA cognitive needs.

Otherwise, why not choose the ones you tested to start with? We've 
already had a go at them, and it would be great to get some other 
activity tabs written for them too.

Thoughts?

C.

Received on Tuesday, 7 May 2019 13:38:35 UTC