See also: IRC log
<scribe> Scribe: Brent
<shawn> https://lists.w3.org/Archives/Public/public-wai-eo-site/2017Sep/0022.html
Home Page Issue 93: https://github.com/w3c/wai-website-design/issues/93
Alicia: In general stock photos will be very generic.
I think we should not be trying to convey information or content via the image used.
Alica: Agree with comments. I think I understand the issue and comments and will work at pullilng together images that can be used.
Eric: It should have something to do with accessibility. But should change. Time is running out for my subscription.
Shawn: Eric has 8 for free and we should use those.
Alicia: okay.
Home Page Issue 96: https://github.com/w3c/wai-website-design/issues/96
Issue 96: https://github.com/w3c/wai-website-design/issues/96
Eric: I don't believe people come to the home page to read the news. I think the location and prominance is okay for now.
Shawn: The issue is that we want people to pay attention to the news.
Sharron: In the past they don't come for the news, we want to change that and have people pay attention to the news in the new site design.
<shawn> related issue: What are the middle boxes? Are they mostly more featured resources?
GitHub Issue 82: https://github.com/w3c/wai-website-design/issues/82
Alicia: The intent of the design is to give people another way to navigate to the different parts of the site.
Shawn: Are you thinking that they would be "plan & manage, advocate, etc"
Alicia: Wasn't thinking they
would be links directly to specific resources.
... More like main categories for content on the site.
<shawn> Brent: Are people going to be able to click on top level page of nav and get overall pages
<shawn> SLH: yes
<Zakim> shawn, you wanted to anser brent
Alicia: We could mirror the top navigation or may be benefit to linking to specific resources.
<shawn> breadcrumb will have link to overview page
<shawn> acl y
<Zakim> yatil, you wanted to say not duplicating main navigation links!
Eric: Would give a direct link to
resources that we wanted people to see.
... Links that would go deeper than the WAI site nav may go
into.
... Having more features in those boxes gives a better
overview. Could even add another set underneath the news to
focus on even more topics/resources.
Shawn: What if they are featured
resources, and then people get use to the links to them there,
then when we rotate out old and put in new, people cannot find
what they were use to seeing in these middle buckets.
... Or people might just focus on those only and not get used
to search out the other resources in the navigation.
<shawn> A primary goal with the new redesign is to help people know abou tthe range of WAI resources
Charlotte: If we do a good job with the IA and the nav, it should not be a problem when these featured things change. They will be able to find it in the nav. Also believe people will bookmark the resources they go back to often.
<shawn> brent: long ago we talked about role. if we use boxes as featured resources. James, do you feel nav is good enough for role
<shawn> james: yes
Shawn: If these become featured resources or hot topics, will it be confusing to have one Featured Resource at the top and four others lower on the page?
Charlotte: See that all the time.
James: We are trying to make the site "sticky" and draw people in with many different ideas and things to view.
Shawn: Back to the news topics. Should we make this area two columns. Left: news and announcements - Right: Featured Content.
<yatil> [ Shawn Don’t we have three news on the front page and all others on the news page?]
James: Those that are coming in looking for news and announcements will be fine searching for them and they will find them.
Laura: If you really want to move news up, is it possible to just have a link or button to News under "what is the W3C WAI.
Eric: Could have both. Top three news topics on this page and then also a news page that has everything.
Shawn: We have that now. Won't restrict it to three, could be more.
Eric: There are a lot of technical solutions that we could implement to show the news topics. These can be decided later.
<shawn> [ in reply to [ Shawn Don’t we have three news on the front page and all others on the news page?] -- no, often need more than 3
<yatil> Eric: We can have as many news pieces featured as we want, even have news items featured that are older than the x newest news items.
<shawn> https://github.com/w3c/wai-website-design/issues/82
Shawn: There is a couple of
solutions.
... 1) Title of resource, description, whole box is
clickable.
... 2) Topic (category of the resource), description, link to
the resource.
<shawn> Getting Started Featured Resource
<shawn> If you need to urgently address accessibility in an existing web project, see Web Accessibility First Aid: Approaches for Interim Repairs.
Alicia: I am not sure that having
the categories will help me understand the resource.
... Would use the title of the resource as the link instead of
using "learn more"
<yatil> [ notes strongly + READ MORE in the teaser which is completely linked ]
<shawn> brent and shawn provide specifics to alicia
<shawn> https://github.com/w3c/wai-website-design/issues/87
<shawn> Brent: link to the Tip itself, and not to more design tips.
Laura: Agree with Brent. Tip of the week is that you are looking at one tip.
James: +1 too
Eric: When you link into a page, people will be missing the heading and overview paragraph, they may be lost or be confused.
<shawn> https://github.com/w3c/wai-website-design/issues/89
Shawn: When looking at the specific wording for the video text, do we want to try and incorporate the perspectives tag line into the text.
Sharron: Yes, we do want to
include the tagline.
... Not in the heading. Makes it too long.
Eric: I want to keep the button and not link the text,
+1 to Eric
Laura: Like the example, with the button.
Shawn: All other items in the email were for others to address specifically. Just calling attention to them.
Charlotte: Any questions that you have on the questions provided in the email, please send them to me by the end of this week if possible.
James: No other topics. Meeting adjourned.
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) Succeeded: s/Issue #93/Topic: Issue #93/ Succeeded: s/New prominance/News prominence/ Succeeded: s/eough/enough/ WARNING: Replacing previous Present list. (Old list: Laura, Sharron, Brent, Eric, Shawn, Charlotte, Howard, Alicia, James) Use 'Present+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Present+ Alicia, Shawn, Brent, Charlotte, James, Laura, Sharron, Eric Present: Alicia Shawn Brent Charlotte James Laura Sharron Eric Found Scribe: Brent Inferring ScribeNick: Brent Found Date: 20 Sep 2017 Guessing minutes URL: http://www.w3.org/2017/09/20-eo-minutes.html People with action items:[End of scribe.perl diagnostic output]