Silver Task Force Teleconference

14 Nov 2017




<Lauriat> https://github.com/w3c/publ-a11y/wiki/Publishing-issues-for-Silver

<jeanne> https://docs.google.com/document/d/1x8uJRINJvHnAHqZ3HS30Z6Adrl6JX_N4QTXaKJ1jLAE/edit

ACT Notes from TPAC: https://docs.google.com/document/d/1x8uJRINJvHnAHqZ3HS30Z6Adrl6JX_N4QTXaKJ1jLAE/edit

We may be getting some additional members - IBM will be looking for people in their organization.

Jeanne: One idea from TPAC is that there are needs of people with disabilities that are structurally having difficulty being included in WCAG due to testing requirements
... example - plain language - how do you test that something is written in plain language
... a solution was proposed that we look at "best practice" as "needs of people with disabilities" that are difficult to test, but that we should require companies to document how companies address the SC that cannot be easily, quantifiably tested

Charles: This sounds like an extension of VPAT where you would talk about your own process for meeting a requirement

Shawn: a theme from the meetup was the consumption of a11y guidelines - a lot of people would prefer that they guidelines be easy to understand within the role a specific person is filling - how do designers apply the guidelines vs. developers, etc.
... we asked people where they go for a11y reference when they need it - things like Webaim and other resources that describe "how to do" a specific task. While people find this helpful, how do we balance that with the implementation details that are needed?

Jeanne: I talked with people from browsers at TPAC. We discussed a lot of things that are happening around accessibillity - the "potential" of using the Accessibility Object Model for accessibility testing
... with the accessibility object model, people are now starting to think about how accessibility of the browsers could be tracked regularly - they are going to start with how well browsers are implementing ARIA

With the accessibility object model, there is potential to include browser accessibillity testing in the web platform test that would push browsers to address accessibility more consistently and effectively

Jeanne: Raquel (a member) is interviewing people at her University about accessibility and would like to know if there are questions that we would like for her to ask.
... we planned legacy and conformance interview questions, so we should probably look at conformance.

Jenisen: Why don't we use the questions that we used at the meetup? It's information we have already and it's information that we need.

Jeanne: Where do you go when you need a reference on accessibility and why?

<Lauriat> Questions:

<Lauriat> Where do you go when you need a reference on accessibility? Why?

<Lauriat> What works well for you around accessibility guidelines?

<Lauriat> What doesn't work well for you around accessibility guidelines?

<Lauriat> What's on your wishlist? (around accessibility guidelines)

Ryan: Could we ask questions about which disabilities people have trouble designing for?
... What persona models do you feel the most prepared for when designing accessibility solutions?

Jenisen: The largest group that people seem to struggle with are people with cognitive disabilities because it's so large.

Ryan: In a lot of cases, just being able to discuss disabilities, opens the door for people to discuss their disabilties
... for example, when we started looking at color blindness, people that I work with stated that they were color blind and I never knew that

Jenisen: In the design world, there seems to be concern on the part of designers who don't want to admit they are color blind because they are concerned about the effect on their career

Jeanne: We need to think about the law of unintended consequences and consider how the structure of the guidelines might lock out certain disabilities

Ryan: If you could make a list of the potential accessibility narratives or personas and see what people's comfort level is when designing for a particular person.
... For example, ask people "How confident do you feel about designing a bar chart that is accessible to all types of color blindness?

Charles: To extend that in survey questions, you would need to ask questions about the general approach to solving a particular process - for example, one way to solve color blindness issues is to provide a view control that would allow users to control their own color scheme.

Jeanne: This is a good topic to kick off our Friday meeting.

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/11/14 15:33:17 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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: Jan

WARNING: Fewer than 3 people found for Present list!

No ScribeNick specified.  Guessing ScribeNick: Jan
Inferring Scribes: Jan

WARNING: No "Topic:" lines found.

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 14 Nov 2017
People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report

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]