QuickRef redesign

<shawn> prototype 1 http://w3c.github.io/wai-wcag-quickref/

<shawn> prototype 2 http://w3c.github.io/wai-wcag-quickref/2

Shawn: We have two prototypes to consider thanks to Eric. A reminder that next week Eric will be conducting some user feedback sessions and we want to take a look to consider particularly first if there are high priority issues to change before the sessions and second
... if we want Eric to focus on specific things during his sessions.
... A minor minor thing, scrolling down on the left hand panel to where I see Show levels filters and click to see it I have to scroll farther down to actually see it. It would be nice to reveal all of it when I activate that choice

Eric: I am not sure how to do it but will consider

Brent: When I go to load a fresh page in Chrome and FF, if I show tags it pushes other filters down and I can only see Techniques filters and if I expand that, I can't get it to show the filter unless I collapse the others.

Eric: The left column should be scrollable as well. We must decide it we want the menu to come with us down the page or not.

<yatil> ACTION: EricE to explore scrolling behavior in left navigation. [recorded in http://www.w3.org/2015/06/12-eo-minutes.html#action01]

<trackbot> Created ACTION-321 - Explore scrolling behavior in left navigation. [on Eric Eggert - due 2015-06-19].

Brent: Great job of showing what has been filtered out and I like how the filtered out stuff is always clear. You did a great job on that functionality

Kevin: I like the way that functions. Wondered whether people preferred to know what was filtered in rather than filtered out and it seems there may be a slight bug with linking into?

Eric: Problem is the fact that what is filtered in tends to be very long

<yatil> ACTION: EricE to explore displaying filtered-in items. [recorded in http://www.w3.org/2015/06/12-eo-minutes.html#action02]

<trackbot> Created ACTION-322 - Explore displaying filtered-in items. [on Eric Eggert - due 2015-06-19].

Brent: Some exploration is worthwhile, but my inclination is to prefer seeing what I have filtered out with the assumption that everything else is showing

Shawn: If I select only one technique, I get a dot dot dot, the filtered out is not all shown

Eric: I don't think all things that are filtered out need to be shown there. I had previously truncated but do not need to do that any more.

Shawn: Especially important if it is printed

<yatil> ACTION: EricE to not truncate filtered-out items. [recorded in http://www.w3.org/2015/06/12-eo-minutes.html#action03]

<trackbot> Created ACTION-323 - Not truncate filtered-out items. [on Eric Eggert - due 2015-06-19].

<paulschantz> Please never ever change the spinning checkmark/hourglass icon

Kevin: Consider the order of the filters that appear.

Shawn: I thought the filter levels would be one of the more common things. Would we want Level filters before Techniques filters?

Kevin: Agreed, Level filters more likely to be relevant. It may cause confusion if what is most important to people is not most prominent

Shawn: If I have just CSS and just AAA I will not see the levels at all. It may need its own line

Eric: OK please reload and we will have Levels first

<yatil> ACTION: EricE to reorder tags-levels-techniques. [recorded in http://www.w3.org/2015/06/12-eo-minutes.html#action04]

<trackbot> Created ACTION-324 - Reorder tags-levels-techniques. [on Eric Eggert - due 2015-06-19].

Kevin: Not sure if this is a bug or unintended consequence. The anchor becomes hidden behind the filter. The position seems not quite right
... when I open up "Adaptable" the main content will move to that anchor. Because there is now an overlay with the filters, the title becomes hidden behind the overlay.

<yatil> ACTION: EricE to manipulate anchor behavior so that the jumping to ids works as expected and is not obfuscated by the filters bar. [recorded in http://www.w3.org/2015/06/12-eo-minutes.html#action05]

<trackbot> Created ACTION-325 - Manipulate anchor behavior so that the jumping to ids works as expected and is not obfuscated by the filters bar. [on Eric Eggert - due 2015-06-19].

Shawn: Notice Back to the Top is more visible, clear and enlarges on focus - good!

Brent: Color scheme and the way to show where you are as you scroll is greatly improved

<kevin> +1 to visibility of location

Paul: Is there a way to reset all filters?

Eric: Not yet but it will come back

<yatil> ACTION: EricE to reintroduce the clear all filters button. [recorded in http://www.w3.org/2015/06/12-eo-minutes.html#action06]

<trackbot> Created ACTION-326 - Reintroduce the clear all filters button. [on Eric Eggert - due 2015-06-19].

Shawn: OK let's look at prototype #2
... Eric, I am missing the ability to get to the bottom, I am missing scroll bars when I have techniques shown etc.

<yatil> ACTION: EricE to introduce scrolling in the right column in prototype 2. [recorded in http://www.w3.org/2015/06/12-eo-minutes.html#action07]

<trackbot> Created ACTION-327 - Introduce scrolling in the right column in prototype 2. [on Eric Eggert - due 2015-06-19].

<Lydia> if one closes the tag or on this page how does one get it back?

Brent: back to Shawn's points from last week, you are likely to get different input about which they like best. We should be sure to show them alternately. What people see first will influence what they like best.

Shawn: And something to observe is whether they figure out on their own that they can collapse columns. See if they find it and then what they think of it.

Brent: When you collapse the left side, you get a button that says sidebar. When you collapse right side you get the wrench with a black column beneath it. Left side is a floating button, right side is a "gutter" - why the difference?

Eric: The right should behave the same as the left it is actually a bug.
... when you collapse and begin to scroll, the buttons will scroll with you and you can open it at any time. I do not object to the gutter but it needs exploration.

Sharron: Did you have a preference Brent?

Brent: Only that they should be the same.

<yatil> ACTION: EricE to make gutter behavior consistent, explore other for the possibility. [recorded in http://www.w3.org/2015/06/12-eo-minutes.html#action08]

<trackbot> Created ACTION-328 - Make gutter behavior consistent, explore other for the possibility. [on Eric Eggert - due 2015-06-19].

Shawn: Personal preferences for 1 vs 2?

<paulschantz> I still prefer 1

<Brent> Outstanding work Eric!

<shadi> +1

<paulschantz> http://w3c.github.io/wai-wcag-quickref/

Lydia: Like the way the right gutter looks, and the way to interact with the website.

<kevin> I think I have a mild preference for 2

Shawn: One possibility, there is a back to top banner all along the bottom, a banner along the top might include the collapsed tools.
... may be too hard to implement

<Lydia> I like 2

Eric: Yes I have been thinking along those lines as well. Having a top border that simulates the sidebars and would be a quite nice touch
... I will play with that

<yatil> ACTION: EricE to explore a top banner thingy thing! [recorded in http://www.w3.org/2015/06/12-eo-minutes.html#action09]

<trackbot> Created ACTION-329 - Explore a top banner thingy thing! [on Eric Eggert - due 2015-06-19].

Sharron: Bravo Eric, bravo, bravo!

<Howard> +1

Howard: I like the visibility of the tags and filters on the left side, so I lean toward that one. On the other hand, the black background really does draw attention to it on the right. #1 is my preference.

<shawn> ftr, I strongly like the customize on the right. I think it's way too cluttered on the left :)

<Lydia> In reviewing it again. it may be best on the left side so #1 would be better as most users will be trained to look in one area instead of different places on the page.

Shadi: I really liked the first version until the menu is expanded. It gives me an overview that I can use to jump to what I am looking for. A first time user might not see the other filters that are put all the way in the bottom.

<shawn> +1 to look & ask users which they'll use more - tags, tech filters, level filters

Shadi: it may be able to be made more visible and we might provide more tags than we have now which could push customization items even further down. I suggest to also look at the most common customization choices.

<shadi> +1 shawn

Shawn: There are different preferences. maybe what we look for is a "do no harm" approach. What is best and worst case of each. For example "If they are on the right, people just don't see them" vs "On the left they become so complex it becomes confusing and unworkable" So, beyond just preferences,
... are there negative and positive aspects that should be considered.

Lydia: People will become accustomed to where we place the menus, we need to be consistent and perhaps we could in the place where there are Principles, those could be expandable and collapsible within the side bar. So that they are not all exposed , making the left hand menu less complex.
... when you move it to the right hand side, you train the user. We need to be consistent.
... So rather than having to scroll on the left side bar to get to the other configurations, they would all be expandable by choice.

<shadi> +1 Lydia

Shadi: There are actually two functions. One is navigational- helps you position within the page and the other, the other is the customization - that changes the content. Perhaps there is a way to allow a big button that says "Customize".

Eric: Where do want this to be, above the navigation elements?

<yatil> ACTION: EricE to try out having customize button on the top. [recorded in http://www.w3.org/2015/06/12-eo-minutes.html#action10]

<trackbot> Created ACTION-330 - Try out having customize button on the top. [on Eric Eggert - due 2015-06-19].

Shadi: Yes, a button that spans the width

Eric: Yes so when it is activated, it will push the navigation elements down.

Shadi: The two functions are quite different. The navigation will be more often used and it makes sense to be expanded by default.

<Zakim> shawn, you wanted to say eric's off-record comment and to say separate not necessarily right

Shawn: I see the potential issues with having the right hand nav, but even if it is a static mockup, it is important to show people where the Configure is separated from the navigation. However it is done, even if is a static mockup, we should show at least one or two more possibilities where the separate functions are clearly delineated.

Eric: Thanks for this feedback and I agree it is important. I will do what i can to give options to the users next week. I agree with Brent's comment as well that we need to be mindful of which prototype users see first.

Shawn: anything else on this?

Tips text comments

<shawn> status: Changes related specifically to the tips text have been mostly incorporated

<shawn> Still exploring comments from specific people

<shawn> Managing and Advocating are undergoing a quote a bit of a change so anything for this has not yet been included

Kevin: Thanks to all who commented. I have been working my way through them. Main ones are related to tips that need to be added, removed or title edits.
... you are welcome to add more comments, have been exploring some comments with specific people to clarify and trying to tease apart managing and advocating and will be updating soon.

Tips icons

<shawn> survey https://www.w3.org/2002/09/wbs/35532/EOWGTipsIcons1/results

<shawn> summary https://github.com/w3c/wai-quick-start/issues/12

<Lydia> I didn't get a chance to enter my thoughts but I really really really like the icons!

Shawn: Currently draft icon is a paintbrush, but comments noted that this is also interaction design, there was an idea for a protrator/ruler.
... quick thoughts or additional comments?
... does the ruler/pencil work?

Howard: What about an architectural drafting icon?

<Howard> Here's what I see: http://bit.ly/1IOGbnL

Sharron: Or this http://bit.ly/1GiUHAD

<Howard> I like the ruler/triangle icon

<Lydia> I am leaning towards the paint brush

<shawn> +1 to combining the images

<shawn> to cover both

Sharron: here is one that is more painterly http://bit.ly/1GiUQ72

<shadi> +1 to avoiding complexity

<shawn> +1 to the one of a paintbrush over a monitor!

Howard: The icon makes people think about certain concepts, it may not have to inlcude every aspect. I would caution us not to overthink it. If people associate it with the category and help them scan and find the one they are looking for.

<shawn> [ there's also one of of a wrench & paintbrush ]

Lydia: I like the icons that were clear and would suggest that we need just one item. Would not want to have more than one per category. I can make the connection immediately between the titles and the icons. I would not change anything.

Shawn: My concern with the paintbrush is that it communicates only visual design and not the interaction design.

<Lydia> good suggestion Brent for a compass

Brent: I am following along the same way Lydia and Kevin are tracking. Don't combine symbols, keep it as simple as possible. When it comes to design, I think a compass may be better than a paintbrush. if we tried to pick just one, a compass would be more accurate in this context.

<Brent> http://png-3.findicons.com/files/icons/2711/free_icons_for_windows8_metro/512/drafting_compass.png

<kevin> http://w3c.github.io/wai-quick-start/index.html

<yatil> I like the consistency of the current icon set.

<Lydia> It is suppose to be a bug

<Lydia> we are looking for bugs - we use this in our office for programming language

<shawn> https://github.com/w3c/wai-quick-start/issues/12

Sharron:search result for evaluation icon: http://bit.ly/1B7FQKr

Lydia: I like the bug because working in IT, I associate it right away. But what about a big eye?

Eric: I like the clipboard with just lines, I think it is a good symbol maybe without the check boxes, but simply some text, maybe WCAG-EM
... It should be as general as possible

Shadi: More people can relate to theh bug than to WCAG-EM

<Howard> I didn't get the bug at all

Shadi: would look at the clipboard

Kevin: We need to be very conscious of target audience. A bug will have meaning to evaluators.

<shawn> brent's https://encrypted-tbn2.gstatic.com/images?q=tbn:ANd9GcSgjZgGsrbTQDgRUARvWydWVhD8ikJj4EFWoQm3H9mnoXqItOMA

<shadi> [ i could live with clipboard or lens too, depending on icon ]

Brent: I am looking for icons as well, I found a magnifying glass over the computer, and found another one. I understand to be careful of magnifier since often used for search. But this one seems OK. My first inkling was not to see the current icon as a "bug" but as a little creature crawling through and looking at things.

Shawn: So we came to this: Options are keep the bug as a posibility, consider a clipboard without checks, or a magnifier over a computer screen or a page.

<shadi> [ i could live with clipboard, lens, or measuring tape too, depending on icon ]

Shawn: Adovating is currently a megaphone. My concern is whether a megaphone might have a connotation of a loudspeaker and as an aggressive, obnoxious thing.

Brent: Not for me, it seems more like a tool for an important announcement. Asking for attention to an important matter.

<shadi> +1 to Brent

<Lydia> no concerns

Sharron: Cheerleading association in US culture

Shadi: Good point Shawn but it has not reached the level of concern for me

Brent: This icon is electonic, might be used by police or more authoritative agents. A non-electonic megaphone would tone it down

<shawn> +lots to Brent - more cheerleading one, not electronic !

<Sharron> analog megaphone: http://bit.ly/1KKCAqj

Kevin: I welcome suggestions for iconography around managing

Shadi: What is your discomfort about the Managing icon.

Kevin: People's enthusiasm was just pretty tepid for that one. So I wanted to show the interconnection of things.

Shadi: I thought it got this concept of getting things moving together and in context it works very nicely.

Shawn: Upcoming work:the Showcase examples

Upcoming work: the Showcase examples

<shawn> Make sure you understand the Requirements Analysis. Review the draft proposed Scenario Descriptions; and complete the EOWG Survey on Showcase Examples

<shawn> (there are links in Agenda)

Shawn: Make sure you understand the requirements, follow links in today's agenda, see what questions you have.

<shawn> GOAL is to draw people into accessibility, not "teach" details

Shadi: Shawn forwarded some feedback from HTML5 training where there were people saying "Wow, I never heard about accessibility before" We are in this field and assume that people know about it but it is amazing how many do not.

Sharron:: m-enabling summit. (Knowbility won award from FCC) Developer on panel from Spain said members of accessibility community talk to each other and think there is progress. But he was speaking to a room of over 200 developers, asked how many thought about accessibility during dev process and NOT ONE raised hand...I was really shocked.

<Sharron> ...these are meant to get people engaged, motivated, and interested in finding more resources.

Shawn: Each of these scenarios will be within a page about a specific accessibility issue, the video, some text and links ot additional resources (that is the idea now)
... any other questions, comments on that?

Practice on WebEx

Shawn: Most people will probably want to download the client so that WebEx can call you.
... it provides a tollfree call. You can also call a toll number and enter a code

Eric: There are apps for different smartphones, so you can use the client on a smart phone on the go as well.

Shawn: To find the client, use the link from our agenda

<paulschantz> yep

<paulschantz> I set you as the presenter

Sharron: will we still use IRC?

Shawn: we will use webex only for the phone, will stay on IRC, so we will be unable to use zakim for muting, unmuting or queue

Brent: If you go the the Best Practices link, it says you can still use zakim for floor control

Shawn: But will have to use WebEx for muting (or local)

Eric: The presenter role will not be important unless we are screen sharing

Shawn: I connect through WebEx and then try to ignore it. To continue to do queue management etc in IRC

Eric: The big advantage in IRC is the ability to make notes about what you want to say. You can also use Call using your computer

Shawn: Glad that it is set so you can talk without me and if you have time to join early next week. Other than solving Paul's audio, we are adjourned, have a great weekend.

trackbot, end meeting

<shawn> work with paul