SV_MEETING_TITLE -- 05 May 2014

<Lisa_Seeman> agenda: this

<Lisa_Seeman> trackbot, status

<Lisa_Seeman> ACTION: Tim Accessibility review [recorded in http://www.w3.org/2014/05/05-coga-minutes.html#action01]

<trackbot> Error finding 'Tim'. You can review and register nicknames at <http://www.w3.org/WAI/PF/cognitive-a11y-tf/track/users>.

<Lisa_Seeman> ACTION: Tim PTSD review [recorded in http://www.w3.org/2014/05/05-coga-minutes.html#action02]

<trackbot> Error finding 'Tim'. You can review and register nicknames at <http://www.w3.org/WAI/PF/cognitive-a11y-tf/track/users>.

<Lisa_Seeman> ACTION: Suzanne Review of APPL [recorded in http://www.w3.org/2014/05/05-coga-minutes.html#action03]

<trackbot> Created ACTION-1 - review of appl [on Suzanne Taylor - due 2014-05-12].

<Lisa_Seeman> ACTION: Kinshuk Review of adaptivity [recorded in http://www.w3.org/2014/05/05-coga-minutes.html#action04]

<trackbot> Created ACTION-2 - Review of adaptivity [on Dr Kinshuk - due 2014-05-12].

<Lisa_Seeman> ACTION: Katie gettign the ageing subgroup ready for review [recorded in http://www.w3.org/2014/05/05-coga-minutes.html#action05]

<trackbot> Created ACTION-3 - Gettign the ageing subgroup ready for review [on Katie Haritos-Shea - due 2014-05-12].

<scribe> scribe: MichaelC

preview agenda

ls: moving user groups to later in the agenda

have spent time on it, not finished but need to turn attention to other stuff as well

still do want to look at things through the user group lens

also start thinking about good practice and bad practice for various user groups

even with specific solutions e.g., meta tags, need to know good practices

<slee> Hello all

please speak up if needed during the call e.g., noise distractions etc.

user groups, finding good practice and identifying bad practice

ls: what to start to figure out what makes a good practice

what works and what doesn´t, e.g,. low contrast is confusing

identify what challenges make an impairment more difficult

helps with developing techniques

the more we understand about why, the more we can abstract

jo: sent message with idea to create a secondary interface

available with reference from primary interface

to lower threshold for cognitive comprehension

e.g., someone had a successful v1 app because it was simple, v2 was more complex and the v1 users had trouble with it

ls: what decreases cognitive load?

jo: targets on buttons, fewer items per page

ls: a flat-screen design going around makes it harder to identify regions

so a design practice might be that it be visually clear what controls go together

and how sections of page relate together

and that boundaries between sections are visible so it´s clear which one you´re clicking on

<SuzanneT> https://creativemarket.com/blog/2013/07/31/12-creative-examples-of-flat-web-design

<JohnRochford> q

jr: there isn´t much emperical research about what works

so we have to guess about solutions

jo: clearly user testing is required

in my example above, it was real-world, and developer went back to user group to improve

mc: in this case, post hoc user testing

st: before user testing, we need to have a clear sense of the propose techniques

in some other work I´m in, there are good ideas but not clearly defined

which can make it hard to get a reliable result in user testing

kd: about anecdotal data

be careful of promulgating ¨urban legends¨ about e.g., reading

if we´re making a best guess about a group, be careful that we don´t speak with more authority than we have

have seen that some user testing labs have the same people testing all the time

thereby end up with optimizing for that particular set

ls: we do need to change that

get to the most general population we can

impacts our choice of user groups in this phase

some steps:

identify some bad practices users encounter

using ourselves and others

e.g., I´ve worked with difficult sites, and try using them and take notes about why I struggle

we also should collect the anecdotal evidence that´s out there

but be very conscious of its provenance

don´t want to waste good research, but don´t build up a house of cards

what might be a good way to collect this?

mc: suggest use wiki

maybe a page for ¨Good and Bad Practices¨

just put down ideas, maybe sorted by user groups

and indications of provenance

sort through it all later

ls: how about actions?

mc: if specific actions

but still wiki seems place to ultimately collect the info

ls: ok, I can set up a page. If people need help posting to wiki, can send to mailing list

JohnR and @@ agreeing to help get that stuff migrated to wiki

<Lisa_Seeman> ACTION: JohnRochfor and Kinshuk to maintain page on good and bad practice [recorded in http://www.w3.org/2014/05/05-coga-minutes.html#action06]

<trackbot> Error finding 'JohnRochfor'. You can review and register nicknames at <http://www.w3.org/WAI/PF/cognitive-a11y-tf/track/users>.

s/@@Kinshuk

<scribe> ACTION: rochford to maintain page on good and bad practice [recorded in http://www.w3.org/2014/05/05-coga-minutes.html#action07]

<trackbot> Created ACTION-4 - Maintain page on good and bad practice [on John Rochford - due 2014-05-12].

<scribe> ACTION: kinshuk to maintain page on good and bad practice [recorded in http://www.w3.org/2014/05/05-coga-minutes.html#action08]

<trackbot> Created ACTION-5 - Maintain page on good and bad practice [on Dr Kinshuk - due 2014-05-12].

issue: Good and Bad practices for user groups

<trackbot> Created ISSUE-1 - Good and bad practices for user groups. Please complete additional details at <http://www.w3.org/WAI/PF/cognitive-a11y-tf/track/issues/1/edit>.

trackbot, associate action-7 with issue-1

<trackbot> Error associating: Tracker returned unparseable XML. Please mail <sysreq@w3.org> with details about what happened.

trackbot, associate action-8 with issue-1

<trackbot> Error associating: Tracker returned unparseable XML. Please mail <sysreq@w3.org> with details about what happened.

kd: will look for a study I found once on good design practices for adults with intellectual disabilities

had info about not making the UI childish

jr: wiki tracks who adds what?

mc: yes

though in practice a little hard to sleuth

better to add your name by contribution

jo: ~~~~ will cause mediawiki to put in your name

ls: anyway the page is just for brainstorming, doesn´t have to have mature info

can people do some gathering?

Kate, John, Lisa volunteering

housekeeping : User group research, technology reviews, mixing up groups, setting and reviewing actions

ls: there has been a lot in the past week on gap analysis

status on non-vocal?

jo: not yet complete

find my path narrowed by constraining to stuff in our scope

have been adding stuff (with Kinshuk assistance)

might be two weeks before I can complete this

<Lisa_Seeman> ACTION: Joseph get the info on non-vocal updated in 2 weeks [recorded in http://www.w3.org/2014/05/05-coga-minutes.html#action09]

<trackbot> Error finding 'Joseph'. You can review and register nicknames at <http://www.w3.org/WAI/PF/cognitive-a11y-tf/track/users>.

<Lisa_Seeman> ACTION: Seeman check that Josephs get the info on non-vocal updated in 2 weeks [recorded in http://www.w3.org/2014/05/05-coga-minutes.html#action10]

<trackbot> Created ACTION-6 - Check that josephs get the info on non-vocal updated in 2 weeks [on Lisa Seeman - due 2014-05-12].

action-6 due 19 may

<trackbot> Set action-6 Check that josephs get the info on non-vocal updated in 2 weeks due date to 2014-05-19.

ls: what about aphasia?

sl: that can impact beyond non-vocal

since it´s in both comprehension and formulation

mc: suggest we just look at things where they come up

may later re-sort our taxonomy

khs: non-vocal component of dementia and aging may be further down than we´ll be exploring, as it´s usually final stages afaik

ls: might be good to mix up the groups

anyone else want to pitch in on non-vocal?

ls: aging and dementia, still another week out?

khs: yes

ls: then want Neil to review?

khs: think so

ls: maybe when you hand the baton to Neil, you can then look at non-vocal?

khs: sure

ls: Down´s - JohnF?

jf: plan to deliver in a week

<Lisa_Seeman> ACTION: john folit to get downs ready for review [recorded in http://www.w3.org/2014/05/05-coga-minutes.html#action11]

<trackbot> 'john' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., jfoliot, JohnRochford).

<Lisa_Seeman> ACTION: jfoliot to get downs ready for review [recorded in http://www.w3.org/2014/05/05-coga-minutes.html#action12]

<trackbot> Created ACTION-7 - to get downs ready for review [on John Foliot - due 2014-05-12].

ls: KateD, can you look?

kd: yes

jr: me too

ls: ADD/ADHD

kd: will look here as well

also autism

CSS review questions, how to do a technology review.

tb: started to look how CSS could be used to assist or be problematic for people with cognitive disabilities

sent some ideas to Lisa to forward

had some questions about where to focus

ls: @@

<KateDeibel> Sorry. Going now. Just learned of the birth of my nephew

tb: design patterns that can be difficult for users to understand

style can be overridden but not easy

authors don´t recognize issues

ls: can review technology, but it is ubiquitous

think more about good and bad practices that can be enabled through CSS

<Kinshuk> Need to log off.. another meeting starting...

jr: think we´re too early to sort though this yet

sk: maybe too early to finalize, but can certainly start thinking about formats

<Lisa_Seeman> http://www.slideshare.net/ISOCIL/accessibility-and-css-lisa-seeman

<JF> must drop now for another call - bye all

- DRAFT -

SV_MEETING_TITLE

05 May 2014

Attendees

Contents

preview agenda

user groups, finding good practice and identifying bad practice

housekeeping : User group research, technology reviews, mixing up groups, setting and reviewing actions

CSS review questions, how to do a technology review.

Summary of Action Items

Scribe.perl diagnostic output