scribe+ Jan

any pressing updates?

<Zakim> Jennie, you wanted to discuss note

user study analysis

Rain: We have 1 document that did not get finished, but it will get done today or tomorrow.

<Rain> Analysis: https://docs.google.com/spreadsheets/d/1ivrG_nl0Ox90hoMv9yHj1yt5-pbw-pmKXmdZ_epCwz4/edit?gid=1370486415#gid=1370486415

Rain: First, we will read what we learned about the different themes, then we will talk about what we think that means in general, and then the actions we want to propose.
... Using sticky notes in Figma, Rain has begun capturing common user journeys and missing patterns and concepts.
... Want to narrow themes as we go through this.
... The first two are about appendices preference - one said they would want to go through the appendix to get additional information
... There was only one reference to appendices preference, so we are changing this one to research and authoritative sources because they were wanting to understand the research behind the recommendation.
... Let's look at Content Chunking for people looking at the HTML prototype.
... The one person who said they needed more white space was looking at content that was more dense - the Content is Understandable Section in the HTML was more dense. Under "Know You User," there was a really long bulleted list.
... Showed examples of smaller bulleted lists with less content per bullet. She then showed the functional needs section where the list items themselves are small paragraphs - there are also no headings to break up the wall of text.
... One user said, for design build, recommend accordions within accordions. It was recommended that there should be a short description of each item when it was in its collapsed state so that you understand what is in there. In the HTML version, they wanted to have the subsections in accordions (recognizable purpose, distinguishable, and

consistent). Not sure this recommendation is valid because it was based on the HTML version where there was too much white space, which made it difficult to see that information was grouped together. So, the line heights need to be intentional and clean.

Tiffany: Need purposeful sizing for headings, subheadings, and indentation.

Rain: Yes, I agree - we need to create a specific style guide.
... We are done with the HTML feedback. Let's look at the TR note next.
... One person reacted that there was an abrupt switch from text to accordions. This same person also wanted everything expanded.
... Another person had trouble determining sections from subsections - especially in Design and Build. For example 3.1 Objective header is not significantly different from the Design and build. People were confused that Design and Build was suppose to be a section header and that 3.1 was a subsection under it.
... In the TR note, it's going to be a challenge to change these.
... Got feedback that the short bits of content were easy to read.

Tiffany: It's mostly about the sizing of the H2 - if is were slightly larger, it would help people to perceive and understand the H3s underneath.

Eric - There were a couple of people who just wanted the W3C style and nothing else.

Rain: There are limitations to the style guide that limit side-by-side examples. Maybe the way around it is to have one image that has both examples.

Tiffany: Could use figure description to help describe the images within the TR format.

Jan: The visual layout of content contributes to comprehension.

Tiffany: We need to be careful with wording - almost everyone had difficulty with finding icons under scaffolding.
... There were some positives from the TR format and from the Figma version. Figma version was great for chunking, but requires more clicks.

Rain: We had a number of people perseverate on our language - even our use of the term, "User Story." We had people who are not necessarily a part of the accessibility community. We had authors, educators, etc. and not everyone knew was "user story" was. We had people call us out for using the word "impairment" in different places and for using

minor, major, or severe.

Rain: Just plain language in general was pointed out as a need (scaffolding being one example).

Eric: Someone said that they thought they had a definitive list of every possible thing - there was no disclaimer that said this was just an example of multiple possibilities.

Rain: There were similar comments about really trying to clarify ways in which different groups might need different things. There were some people who did not find images useful, so it might be confusing if images are present. People need to be aware that what they are doing to make something accessible doesn't inadvertently make it inaccessible

for someone else.

Rain: I will work on a more thorough synthesis so that we can have a plan for what we can do.

Jan: Change is difficult, but we need to emphasize that the reason we are doing this is to make WCAG more understandable and more adoptable by people who are not already entrenched in this work. The complexity of the documentation contributes to the reasons why companies don't integrate these practices into their workflows.

This is scribe.perl Revision VERSION of 2020-12-31
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: julierawe, Laura_Carlson, Makoto, mike_beganyi, kirkwood, JohnRochford, LenB, Eric_hind, Rain, Lisa, Jennie, Jan, DavidSwallow, tiffanyburtin, Frankie
Present: julierawe, Laura_Carlson, Makoto, mike_beganyi, kirkwood, JohnRochford, LenB, Eric_hind, Rain, Lisa, Jennie, Jan, DavidSwallow, tiffanyburtin, Frankie
No ScribeNick specified.  Guessing ScribeNick: Jan
Inferring Scribes: Jan

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

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.)