<scribe> scribe: jeanne
<Cyborg> i'm on call but can't hear anything
<Cyborg> ah good thanks
<Imelda> +1
<kirkwood> Test and share testing protocol.
Discussion of Examples of tests documents
Cy: People with disabilities should be involved in testing at a lower level than Gold. It should be Silver, but not have to have high results, they could be at the starting phase of of starting user testing.
Shawn: One of the problems is getting testers for specific websites that aren't for the general public.
Kim: In my company, we build sites for lawyers. It is very difficult to find people who have the legal knowledge to be able to test the site.
Shawn: I think Cy is saying that we should recognize that people tried to test. Say "here are things you can do" and then you are creating a demand for it.
Kim: I think a checklist of what you have to do. We need to have pressure to be more inclusive. Give them a pathway to take baby steps.
Jeremy: I see this in higher education. We can test with students, but they are students first, and not testers -- so they can't do the amount of testing with PwD needed.
Kim: This will be harder with some communities than others.
RESOLUTION: In order to speak to the difficulty that some organizations will experience with testing with people with disabilties, we want to give them a path for trying to do it, and even if you fail, you can get some kind of credit. The goal is to get testing with users with disabilites to a medium level (silver) instead of a hard level (gold).
Cy: This would be a part of testing with people with disabilities. Have meta guidance on testing with people with disabilities. We would need to test the meta guidance.
Luis: Have the guidance for testing be separate from the actual state of the page, to be an overall test of the site.
Jeremy: What it means to build a testing team.
Kim: We may need to give alternatives: Maybe if they can't recruit, that they have an advisory board of people with disabilities.
Luis: I would have to have a list of "have you tried this?"
<Lauriat> +1
https://docs.google.com/forms/d/1A3YCt85sXXMc5fPGJ_jC0XandkiYisWEpyNWG70w4CI/edit
<kirkwood> don’t have edit, sent a rqst.
https://davatron5000.github.io/a11y-nutrition-cards/
Jeanne: It's a clever and usable approach to giving information about components
Jemma: I'm concerned about overlap with the ARIA Authoring Practices. How can Silver keep something synchronized with the most current ARIA work?
<mikeCrabb> Heydon Pickering work on creating inclusive components: https://inclusive-components.design/
Shawn: This is good for testing, and maybe we should talk with the author and APG about how to keep the advice current.
Jeanne: I was thinking about it as an example of how Silver could show component level advice.
Jemma: That's how APG approaches it.
Shawn: I want to keep component advice out of Silver. We should just link to the APG and keep it out of Silver.
<jemma> +1
Mike: This is atomic design, and the Silver guidance will apply to these components, but I don't think this is the kind of thing we should be focusing on. Maybe we could have an API that allows people to extract the Silver guidance so it can be applied.
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Present: jeanne KimD Jan jemma LuisG MichaelC AngelaAccessForAll shari kirkwood mikeCrabb Lauriat Imelda Jeremy Found Scribe: jeanne Inferring ScribeNick: jeanne Found Date: 07 Aug 2018 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]