12:28:23 <RRSAgent> RRSAgent has joined #eo
12:28:23 <RRSAgent> logging to http://www.w3.org/2015/06/05-eo-irc
12:28:25 <trackbot> RRSAgent, make logs world
12:28:25 <Zakim> Zakim has joined #eo
12:28:27 <trackbot> Zakim, this will be 3694
12:28:27 <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
12:28:27 <shawn> chair: Shawn
12:28:28 <trackbot> Meeting: Education and Outreach Working Group Teleconference
12:28:28 <trackbot> Date: 05 June 2015
12:28:39 <shawn> zakim, this will be EOWG
12:28:39 <Zakim> I do not see a conference matching that name scheduled within the next hour, shawn
12:30:41 <shawn> Present+ Shawn
12:30:47 <kevin> present+ kevin
12:30:48 <shawn> Present+ Brent
12:31:03 <Howard> Howard has joined #eo
12:31:10 <shawn> Present+ Howard
12:31:23 <shawn> zakim, this will be 3694
12:31:23 <Zakim> I do not see a conference matching that name scheduled within the next hour, shawn
12:32:16 <Howard> scribe: Howard
12:32:26 <shawn> Present+ Jon
12:32:53 <Howard> Topic: Quickstart tips
12:33:00 <shawn> http://w3c.github.io/wai-quick-start/index.html
12:33:13 <shawn> survey results https://www.w3.org/2002/09/wbs/35532/eowg1june2015/results
12:33:19 <shawn> Present+ Eric
12:34:32 <Metzessible> Metzessible has joined #eo
12:35:19 <jon> jon has joined #eo
12:36:23 <Howard> Kevin: looks like direction we're going in for titles is good. If everyone is happy, I'm happy.
12:36:39 <Howard> Shawn: what do you think of my suggestions in the survey?
12:36:51 <shawn> title/<h1>Designing for Web Accessibility: Tips for Getting Started</h1>
12:36:55 <Howard> the overview would stay the same as drafted
12:38:02 <paulschantz> paulschantz has joined #eo
12:39:11 <shawn> Present+ Paul
12:39:38 <Brent> Brent has joined #eo
12:40:28 <shawn> Conceptually, the content of the individual tips page is:
12:40:28 <shawn> * Tips for Getting Started Designing for Web Accessibility (specifically for user interface and visual design)
12:40:28 <shawn> * Tips for Getting Started Developing for Web Accessibility (specifically for markup and coding)
12:40:28 <shawn> * etc.
12:41:24 <shawn> title/<h1>Designing for Web Accessibility: Tips for Getting Started</h1>
12:41:53 <kevin> q+ to say that is fine although depends on introduction
12:42:36 <Howard> Shawn: only con to approach is that details like tips for mark up and coding isn't in the main title
12:42:51 <Howard> but only 2 of the topics provide that additional information.
12:42:52 <shawn> ack k
12:42:52 <Zakim> kevin, you wanted to say that is fine although depends on introduction
12:43:54 <Howard> Kevin: happy with Shawn's approach. Perhaps a little too much text for my liking.
12:44:26 <Howard> Important that key words are front loaded.
12:44:31 <yatil> +1
12:44:38 <Howard> Shawn: feedback
12:44:39 <Howard> -1
12:44:39 <paulschantz> +1
12:44:54 <yatil> s/text for/text in the h1 for/
12:45:19 <yatil> q+ to say throw-away on reread
12:45:21 <shawn> Howard: Think title/header longer. cuts down on scanning & quick reading of it.
12:45:42 <shawn> ... understand need to brand the page in some way. thought issue addressed better with box at right
12:46:36 <paulschantz> I amend my +1 to a +0.5
12:47:09 <Howard> Shawn: my concern not so much branding but clarity of information.
12:47:39 <Howard> Tips for getting started with accessibility - if that is just in box at right. My concern is that the H1
12:47:57 <Howard> does not say anything about "tips" or "getting started"
12:48:28 <jon> +1 to Howard
12:48:43 <Howard> Someone with a screenreader or enlarger won't see that "getting started" cue. Important to see "tips for getting started in the h1"
12:49:58 <shawn> Howard: title now has "quick Start Tips". true screen mag user miss that. hadn't thought about that.
12:50:44 <kevin> q+
12:50:51 <shawn> ... spomething in banner that's close the the H1 that screen mag
12:51:27 <shawn> ack j
12:51:37 <Howard> Shawn: that was my original thought but as Kevin and I discussed I changed to current suggestion.
12:51:41 <shawn> ack e
12:51:44 <shawn> ack y
12:51:44 <Zakim> yatil, you wanted to say throw-away on reread
12:52:18 <Howard> Eric: Having ":" Quick Start Tips is a good solution. H1 should describe the content of the site.
12:52:48 <shawn> s/ Quick Start Tips/Tips for Getting Started/
12:52:52 <Howard> If you decide to reread the page, you can stop at the colon. I think it's a pretty nice solution. Doesn't create a lot of different markup.
12:53:51 <yatil> s/":"Tips for Getting Started/“: Tips for Getting Started”/
12:54:10 <yatil> rrsagent, draft minutes
12:54:10 <RRSAgent> I have made the request to generate http://www.w3.org/2015/06/05-eo-minutes.html yatil
12:54:28 <Howard> Jon: I think Shawn's suggestion makes the H1 a little too long. I like the conciseness of it currently.
12:54:53 <Howard> Other ways of handling this issue for the screenreader.
12:55:40 <yatil> s/-1/Howard: -1/
12:55:41 <shawn> ack k
12:55:48 <yatil> rrsagent, draft minutes
12:55:48 <RRSAgent> I have made the request to generate http://www.w3.org/2015/06/05-eo-minutes.html yatil
12:56:32 <Howard> Kevin: H1 is only "Designing for web accessibility". Doesn't include the other text, which is a paragraph.
12:57:10 <Howard> Find the "Tips for Getting Started" as part of the heading clashing a bit with the similar text in the box at the right.
12:57:38 <Howard> Might be other solutions for screenreader and low vision users.
12:57:49 <yatil> i/scribe: Howard/ScribeOptions: -implicitContinuations/
12:57:53 <yatil> rrsagent, draft minutes
12:57:53 <RRSAgent> I have made the request to generate http://www.w3.org/2015/06/05-eo-minutes.html yatil
12:58:01 <Howard> Shawn: title and h1 should communicate what's in the page
12:58:16 <Howard> Feel it's important to have the title in the H1 to communicate that.
12:58:35 <Howard> Kevin: get that and comfortable exploring that.
12:59:56 <Howard> Jon: Way I'm looking at the page, "Designing for Web Accessibility" is what the page is about.
13:00:30 <Howard> I think that "Designing for Web Accessibility" is very concise.
13:01:42 <Howard> Shawn: boils down to how important "Tips for getting started" in the heading. People often skip intro paragraphs.
13:02:03 <Howard> Jon: wouldn't the title of the page carry that over?
13:02:17 <Howard> Shawn: most people would not see the title.
13:03:01 <shawn> Jon: happy with exploring it
13:03:10 <shawn> Howard: don't agree, but OK to explore it.
13:03:28 <Howard> Jon: wouldn't screenreaders catch that?
13:03:46 <Howard> Shawn: Next issue: banner
13:03:49 <shawn> banner https://www.w3.org/2002/09/wbs/35532/eowg1june2015/results#xbanner
13:05:09 <Howard> Shawn: this came from an idea Howard had last week. In the survey looks like
13:05:17 <Howard> there were preferences for the box.
13:06:05 <Howard> Shawn: one of challenges for Kevin is to consider if the box title needs to change if we change the H1.
13:06:34 <shawn> s/one of challenges for Kevin is to consider if the box title needs to change if we change the H1./one of challenges for Kevin is to consider how the box works if we change the H1.
13:06:58 <shawn> Howard: liked the styling before better
13:07:03 <Howard> Howard: liked the red color for the font title on the box - more eye catching.
13:07:14 <shawn> s/ liked the styling before better/ /
13:07:21 <yatil> q+ to say that I like the more muted style
13:07:35 <shawn> ack e
13:07:43 <Howard> Kevin: styling not written in stone yet - was playing around with it.
13:08:06 <shawn> q+ to say agree and maybe smaller text
13:08:10 <shawn> ack y
13:08:10 <Zakim> yatil, you wanted to say that I like the more muted style
13:08:11 <Howard> Eric: likes the more muting styling. Shouldn't be too attention grabbing.
13:08:11 <yatil> ack me
13:08:12 <shawn> ack s
13:08:13 <Zakim> shawn, you wanted to say agree and maybe smaller text
13:08:23 <jon> +1 to Eric no additional comment
13:08:44 <Howard> Shawn: agree to make it even quieter (the font styling on the box at right)
13:09:15 <shawn> s/quieter/quieter eg less bold maybe smaller heading text
13:09:23 <Howard> Kevin: not fixed on styling - whatever works as a device. If it's decided it needs to be quieter, ok.
13:09:41 <shawn> intro paragraph https://www.w3.org/2002/09/wbs/35532/eowg1june2015/results#xintroP
13:11:15 <shawn> Howard: ok
13:11:52 <Howard> Kevin: is the current intro tersified for you?
13:12:09 <Howard> Shawn: No, I think it's redundant.
13:12:33 <Howard> Needs to be tersified more.
13:12:55 <Howard> Kevin: not overly tied to what's there. This is just a start.
13:13:44 <Howard> Shawn: feel like what's there is overly wordy.
13:14:10 <Howard> Kevin: will have a look at it and also will play around with H1s and subtitles and see how it might all work together.
13:14:24 <Howard> Shawn: any other comments on intro?
13:14:45 <shawn> overview page: http://w3c.github.io/wai-quick-start/
13:15:47 <Howard> Shawn: Look at Howard's comment on "developing" and "designing" being next to each other.
13:16:16 <Howard> Shawn: Howard felt words were similarly shaped and shouldn't be next to each other.
13:16:54 <Howard> Kevin: Order of these items somewhat arbitrary. Designing and Dev'l came first but no reason they have to be next to each other.
13:17:52 <Howard> Shawn: open up for discussion - what are general feelings for this layout (instead of a list)?
13:17:56 <shawn> sub-topis: layout
13:18:03 <shawn> s/sub-topis/sub-topic
13:18:20 <Howard> Paul: nice that it's a change from the list. Nice to be different.
13:18:21 <Brent> I like this layout better than the list. List just seems perscriptive to me
13:18:34 <yatil> like it
13:18:39 <jon> i like the current format
13:18:50 <Howard> +1
13:19:30 <Howard> Shawn: in terms of order, is there benefit to having most common ones first. What might we do regarding placement?
13:20:15 <Howard> Paul: Okay with putting "writing" between "Designing" & "dev'l". Would put designing first.
13:20:28 <Howard> Shawn: any other input on order?
13:20:52 <Howard> Shawn: Kevin, please put notes on any decision you decide.
13:21:04 <Howard> Kevin: will put issues in GitHub.
13:21:31 <Howard> Shawn: probably don't want alphabetical.
13:21:49 <shawn> icons https://www.w3.org/2002/09/wbs/35532/eowg1june2015/results#xq4
13:21:51 <Howard> Shawn: Idea was to have icons for the overview page.
13:22:38 <jon> q+ to clarify my answer
13:22:53 <shawn> ack j
13:22:53 <Zakim> jon, you wanted to clarify my answer
13:24:09 <Howard> Jon: I'm huge proponent of iconography. Currently, too text heavy.
13:24:28 <Howard> Happy to create images but not with coming up with what they should be.
13:25:07 <kevin> q+
13:25:33 <Howard> Shawn: Anabelle liked iconography but she's on leave.
13:26:34 <Howard> Shawn: So okay with leaving the idea of icons open but need to decide who will address it.
13:26:42 <Brent> q+
13:26:50 <shawn> s/Anabelle/Anna Belle
13:27:05 <shawn> ack b
13:27:19 <Howard> Jon: maybe he, Howard and Brent could discuss icons offline.
13:27:33 <Howard> Shawn: probably best to do it online.
13:28:05 <jon> +100 Brent
13:28:13 <Howard> Brent: would go further with icons - once you learn icons, it's the quickest recognition tool.
13:28:35 <Howard> Assume when you put the icon on the overview page will carry over to tips page.
13:29:14 <Howard> Does the W3C need to create it's own icons or is here a catalogue we can pull from. Would be happy to pull from an icon.
13:29:56 <shawn> q?
13:29:57 <Howard> Shawn: don't have a catalogue of resources right now but Jon and Annabelle like to create these.
13:30:15 <shawn> ack k
13:30:26 <Howard> We can start with creative commons and then have Jon and Annabelle fill in any holes.
13:30:49 <shawn> s/Annabelle /Anna Belle/
13:30:59 <Howard> Kevin: might be beneficial to see how icons might work - not the selection - but how it goes in there.
13:31:06 <yatil> s/Annabelle /Anna Belle/
13:31:13 <yatil> rrsagent, draft notes
13:31:13 <RRSAgent> I'm logging. I don't understand 'draft notes', yatil.  Try /msg RRSAgent help
13:31:25 <yatil> rrsagent, draft minutes
13:31:25 <RRSAgent> I have made the request to generate http://www.w3.org/2015/06/05-eo-minutes.html yatil
13:31:34 <Howard> Shawn: might be good but not a a top priority.
13:32:01 <Howard> Shawn: option might be to open up a page in GitHub or a wikipage.
13:32:26 <Howard> Jon: open to a GitHub page but willing to do Wiki.
13:32:41 <yatil> s/+1/Howard: +1/
13:33:01 <Howard> Brent: okay with Wiki, don't know GitHub.
13:33:16 <shawn> ACTION: Eric & Sharron & others schedule github training
13:33:16 <trackbot> 'Eric' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., eeggert, evellema).
13:33:17 <Howard> Shawn: still need to have a GitHub session.
13:33:38 <yatil> ACTION: EricE & Sharron & others schedule github training
13:33:39 <trackbot> Created ACTION-309 - & sharron & others schedule github training [on Eric Eggert - due 2015-06-12].
13:35:00 <Howard> Shawn: Kevin, would you create an issue on GitHub and explicitly send it to the list.
13:35:06 <Brent> Can Kevin give us some specs on iconography? size requirements, color requirements, file type...
13:35:24 <jon> There's some people I can ask immediately, so I'll reach out to them today.
13:35:31 <jon> *for help on Github
13:35:32 <Howard> Brent, Jon, if you try to use GitHub and not working, feel free to get started with Wiki.
13:36:49 <Howard> Shawn: Kevin, any other questions you have for today?
13:37:14 <Howard> Kevin: No, feedback has been very helpful.
13:37:50 <Howard> Topic: work for next week (or this weekend)
13:37:54 <shawn>  Tips - Review the tips text (not the explanations underneath the tips yet) thoroughly for what we might want to Add, Delete, or Edit to be worded more clearly and succinctly; and complete the EOWG Survey on Tips Refinement
13:39:04 <Howard> Shawn: next steps on this: several people have contributed to the text - thank you.
13:39:18 <Howard> Want to finalize what tips themselves should be and Kevin will refine
13:39:42 <Howard> the explanations and examples. Need everyone to review the topic areas thoroughly.
13:40:08 <Howard> Are there any we might want to add or delete? Do we want to suggest any edits for clearness and succinctness.
13:40:27 <Howard> Then a survey to report what you've done on that. Any questions?
13:40:51 <shawn> survey https://www.w3.org/2002/09/wbs/35532/EOWGTipsJune1/
13:41:58 <Howard> Topic: Quickref redesign
13:42:12 <shawn> Mock-up: All on left side bar http://w3c.github.io/wai-wcag-quickref/?hide=filters&hide=overview
13:42:29 <shawn> Mock-up: Tags/Filters on right side bar  http://w3c.github.io/wai-wcag-quickref/alternative.html
13:42:59 <Howard> Shawn: EricE has been looking at different markups based on Austin feedback.
13:44:15 <shawn> zakim, mute me
13:44:15 <Zakim> sorry, shawn, I don't know what conference this is
13:45:36 <Howard> really like first markup
13:45:57 <Howard> s/markup/mockup
13:46:26 <paulschantz> +1 to left side markup
13:46:34 <shawn> Howard: like left side. see everyitng right away.
13:46:37 <paulschantz> tags box is so much cleaner
13:46:49 <shawn> ... tags got lost on right side mockup for me
13:46:59 <Howard> Howard: preferred left side mockup
13:47:12 <yatil> s/markup/mockup
13:47:22 <yatil> s/everyitng/everything/
13:47:39 <Howard> Jon: Question you're looking for?
13:47:52 <Howard> Shawn: first reactions?
13:48:18 <paulschantz> a lot less "busy"
13:48:23 <Howard> Jon: way cleaner. Not terribly thrilled with border break with 2 spaces.
13:48:24 <paulschantz> ...and that's a good thing
13:48:58 <Howard> .. Notices that when you're scrolling down on the left hand side it follows you.
13:49:26 <Howard> .. If click on something too many things are highlighted.
13:50:13 <shawn> q+ to say AFTER others have commented
13:50:57 <Howard> Jon: maybe make highlight color a different color.
13:51:19 <kevin_> kevin_ has joined #eo
13:51:44 <Howard> .. Background color on left hand info is a little too gray.
13:51:54 <yatil> ACTION: EricE to revise navigation highlighting.
13:51:54 <trackbot> Created ACTION-310 - Revise navigation highlighting. [on Eric Eggert - due 2015-06-12].
13:52:11 <Howard> Might help for more margin on left hand nav and main content.
13:52:21 <yatil> ACTION: EricE to revise page background.
13:52:21 <trackbot> Created ACTION-311 - Revise page background. [on Eric Eggert - due 2015-06-12].
13:53:43 <Brent> q+
13:53:52 <shawn> ack b
13:54:25 <Howard> Brent: expand/collapse clunky.
13:54:34 <shawn> q+ to say clutter left. top.
13:54:47 <Howard> .. on left side - looking at 1.2.4, 1.2 - 1.9 become navigable. But if
13:55:02 <Howard> .. I try to click on 1.3, I can't.
13:55:06 <yatil> ACTION: EricE to fix the overview navigation bug.
13:55:07 <trackbot> Created ACTION-312 - Fix the overview navigation bug. [on Eric Eggert - due 2015-06-12].
13:55:29 <Howard> .. When completed, will everything be navigable. If I want to go understandable, can I click on left
13:55:41 <Howard> .. navigation to do this or will I need to scroll down.
13:56:07 <Howard> EricE: Yes, that will work Not sure why it broke on change. w
13:56:21 <yatil> s/. w//
13:56:33 <shawn> q+ to sak how tags might work
13:56:36 <Howard> Brent: prefer everything on the left side. When you jump to
13:57:13 <shawn> +1 to strong division between SC
13:57:21 <shawn> +1 to stronger division between SC
13:57:24 <Howard> .. 1.2, .5 etc. Once you get used to all the information showing, okay. Wonder if line between success criteria should be thicker.
13:57:26 <kevin> q+ to ask about all left nav not scrolling
13:57:48 <Howard> .. Some separation lines between subitems and not between others.
13:57:49 <yatil> Action: EricE to fix separator line between Success Criteria.
13:57:49 <trackbot> Created ACTION-313 - Fix separator line between success criteria. [on Eric Eggert - due 2015-06-12].
13:58:05 <shawn> q+ to say tags minimize, too
13:58:09 <shawn> ack ke
13:58:09 <Zakim> kevin, you wanted to ask about all left nav not scrolling
13:58:13 <Howard> Paul: much cleaner now. Also likes everything on left.
13:59:00 <Howard> Kevin: raise a question: when scrolling down on left navigation. No way to scroll on navigation. Is that a feature?
13:59:34 <yatil> ACTION: EricE to make the Navigation scrollable.
13:59:34 <trackbot> Created ACTION-314 - Make the navigation scrollable. [on Eric Eggert - due 2015-06-12].
13:59:59 <Howard> .. EricE will make the navigation scrollable.
14:00:25 <shawn> q+ to ask search
14:00:47 <Howard> Kevin: to EricE: what other changes are you trying to achieve with this new version. What feedback are you
14:01:07 <Howard> .. responding to? Looks similar in structure to previous mockup.
14:01:32 <Howard> EricE:  I think thing we identified the most it that people didn't know their way around.
14:01:52 <Howard> .. I thought about the text and the tagging.
14:02:17 <Howard> .. Two approaches to things I heard. Hopefully tags addresses this.
14:02:30 <Howard> .. Will look through feedback again.
14:02:34 <shawn> [ shawn just scrolled to top and thought wish there was a back to top.... then remembered there is. I still think it needs more visual separation :-]
14:03:41 <Howard> Shawn: needs more visual separation - "back to top"
14:03:48 <shawn> ack me
14:03:48 <Zakim> shawn, you wanted to say AFTER others have commented and to say clutter left. top. and to sak how tags might work and to say tags minimize, too and to ask search
14:03:49 <yatil> Action: EricE to add more visual bling to the “back to top” link.
14:03:49 <trackbot> Created ACTION-315 - Add more visual bling to the “back to top” link. [on Eric Eggert - due 2015-06-12].
14:04:02 <shawn> [ shawn w/o chair hat on ]
14:05:31 <Howard> Shawn: Without chair hat: right now you have filters & techniques show/hide but not tags. Will that be added (the show/hide feature)?
14:05:33 <kevin> +1 for Level turn off
14:05:34 <jon> I agree.
14:05:51 <yatil> <input name="level3" checked disabled>
14:05:54 <Howard> EricE: haven't decided. Think people will want the tag information/option.
14:05:59 <jon> *I agree with Shawn that people will shut off Triple A
14:06:01 <yatil> s/<input name="level3" checked disabled>//
14:06:21 <Howard> Shawn: noticed this mockup doesn't have search. Will that be added?
14:06:46 <Howard> EricE: don't know if it's worthwhile to have search. Search seemed to be confusing to people.
14:07:08 <Howard> .. would be useful to bet more user feedback on this that we're planning.
14:07:28 <Howard> Shawn: my personal feeling was that search was too complex.
14:07:45 <Howard> .. Most people can just do cntl-F to find.
14:08:14 <shawn> Howard: User feedback, people confused by way the search worked. I'm a big advocate of having saerch
14:08:38 <Zakim> bot will restart in a few minutes after the host underneath reboots
14:08:43 <shawn> s/my personal feeling was that search was too complex./my personal feeling was that search was too complex. however  in EOWG survey, there was support for it
14:08:59 <yatil> s/bot will restart in a few minutes after the host underneath reboots//
14:09:04 <shawn> ... wanted it to work like a standard seach
14:10:39 <shawn> re: "<input name="level3" checked disabled>" NOOOOO please do not have it unchecked by default!!! just realizze that people will probably do it  <---eric
14:10:43 <Howard> EricE: I don't know if it's worth it to clutter the interface with the page. Might be able to simplify the search.
14:10:57 <Brent> q+
14:11:20 <shawn> s.re: "<input name="level3" checked disabled>" NOOOOO please do not have it unchecked by default!!! just realizze that people will probably do it  <---eric/ /
14:11:30 <shawn> q+
14:11:41 <kevin> rrsagent, draft minutes
14:11:41 <RRSAgent> I have made the request to generate http://www.w3.org/2015/06/05-eo-minutes.html kevin
14:11:44 <Howard> EricE: could have search as button on left column. Could use it if they want or not.
14:11:47 <shawn> ack b
14:12:21 <Howard> Brent: as far as search functionality, people say you can use the browser search.
14:12:27 <yatil> s|s.re: "<input name="level3" checked disabled>" NOOOOO please do not have it unchecked by default!!! just realizze that people will probably do it  <---eric/ /||
14:12:38 <yatil> s|re: "<input name="level3" checked disabled>" NOOOOO please do not have it unchecked by default!!! just realizze that people will probably do it  <---eric||
14:12:55 <yatil> rrsagent, draft minutes
14:12:55 <RRSAgent> I have made the request to generate http://www.w3.org/2015/06/05-eo-minutes.html yatil
14:12:58 <Howard> What I liked about previous search filter, it would say "6 of 21 showing". If had
14:13:41 <Howard> .. filter running it would still show the information not on the screen.
14:14:07 <Howard> EricE: some people didn't expect it to work that way.
14:15:08 <Howard> Shawn: personally, preferred the layout with the filters on the right. Prefers the left side cleaner.
14:15:40 <Howard> .. Minor point: expand/collapse icons don't work. Should fix before usability testing.
14:15:49 <yatil> Actions: EricE to take a look at the expand/collapse icons.
14:16:08 <Howard> .. Would encourage that we have both versions for usability testing. Alternate between which version people see first.
14:17:00 <Brent> I understand your perspective, but I still prefer everything on the left. On one side
14:17:01 <shawn> Howard: can see customize & filters on right. but like tags and overview onm left
14:17:10 <kevin> +1 to Howard
14:17:50 <Howard> Shawn: expand/collapse, arrows don't make as much sense as they did before.
14:18:11 <Howard> .. Like the heading being at the top instead of the overview - not a major thing.
14:18:32 <Howard> .. EricE, can you say how you see the tags working?
14:19:15 <Howard> EricE: Thinking of 2 different possibilities for the tags - either hide or show very faint success criteria not applicable to that tag.
14:19:40 <Howard> .. show the SC applicable to that tag. For eg. if select contrast, everything would fade
14:19:58 <Howard> .. but items related to contrast.
14:21:18 <Howard> Shawn: think it's vital that if things are hidden we make that clear.
14:21:51 <Howard> EricE: if open filter level and make selection, that happens immediately.
14:22:21 <yatil> Action: EricE to make clear when the main view updates
14:22:21 <trackbot> Created ACTION-316 - Make clear when the main view updates [on Eric Eggert - due 2015-06-12].
14:22:25 <yatil> Action: EricE to show filtered items.
14:22:25 <trackbot> Created ACTION-317 - Show filtered items. [on Eric Eggert - due 2015-06-12].
14:22:27 <Howard> Shawn: any other questions/suggestions?
14:23:16 <Howard> Brent: if person is searching for something and get to area they like, for eg. meaningful sequence.
14:23:31 <Howard> .. is there any reason someone would want to print that little section.
14:24:00 <Howard> .. or this more of a guide for them to find success criteria and other related info?
14:24:15 <Howard> .. With eval tool, want to print things for manager.
14:24:41 <Howard> EricE: there will be a print option but will be a challenge to do that without messing
14:25:06 <Howard> .. up the layout. Don't know if it will be possible to print one small section. Would need
14:25:10 <Howard> .. to figure that out.
14:25:21 <yatil> Action: EricE to explore printing possibilities for specific pieces of content.
14:25:21 <trackbot> Created ACTION-318 - Explore printing possibilities for specific pieces of content. [on Eric Eggert - due 2015-06-12].
14:26:23 <Howard> Brent: one of things don't have implement is share.
14:26:29 <shawn> [/me not like the future links tech italics ]
14:26:33 <yatil> Action: EricE to implement share link.
14:26:33 <trackbot> Created ACTION-319 - Implement share link. [on Eric Eggert - due 2015-06-12].
14:26:58 <yatil> Action: EricE to remove italics from future links for shawn ;-)
14:26:59 <trackbot> Created ACTION-320 - Remove italics from future links for shawn ;-) [on Eric Eggert - due 2015-06-12].
14:27:01 <Howard> .. Is there a way for me to share specific info ala the same filtering, etc., if wanted to pass onto a
14:27:04 <Howard> .. developer?
14:27:13 <Howard> EricE: yes, we will have that.
14:27:50 <Howard> EricE: usability testing will be Tuesday in 2 weeks.
14:28:05 <Howard> .. will try to send out a new version on Wednesday.
14:28:46 <Howard> Shawn: survey on quicktips is out now.
14:29:13 <jon> Bye everyone!
14:29:31 <Howard> rrsagend, draft minutes
14:29:42 <yatil> s/rrsagend, draft minutes/
14:29:52 <yatil> lool
14:29:56 <yatil> s/lool//
14:29:58 <Howard> rrsagent, draft minutes
14:29:58 <RRSAgent> I have made the request to generate http://www.w3.org/2015/06/05-eo-minutes.html Howard
14:36:15 <Zakim> Zakim has joined #eo
14:47:14 <Zakim> bot restarting once more
14:48:23 <Zakim> Zakim has joined #eo
16:22:40 <kevin> kevin has joined #eo
16:49:17 <Zakim> Zakim has left #eo
17:51:14 <kevin> kevin has joined #eo
18:17:06 <yatil> yatil has joined #eo
18:39:10 <yatil> yatil has joined #eo
20:33:21 <kevin_> kevin_ has joined #eo
21:35:53 <kevin_> kevin_ has joined #eo
22:24:58 <kevin__> kevin__ has joined #eo