- From: Bakken, Brent <brent.bakken@pearson.com>
- Date: Thu, 2 Nov 2017 09:04:02 -0500
- To: Shawn Henry <shawn@w3.org>
- Cc: "Frausto, Alicia" <afrausto@visa.com>, "Wise, Charlotte" <cwise@visa.com>, WSTF <public-wai-eo-site@w3.org>, "Green, James" <jgreen@visa.com>, Sharron Rush <srush@knowbility.org>, "Keen, Laura" <lkee@loc.gov>, "Sinclair, Norah M" <norah.sinclair@amac.gatech.edu>
- Message-ID: <CAE6qf-Hj+q-u2Seg9frrPndXagTdbvPnn8xn=d8ZbRaegpDanA@mail.gmail.com>
Shawn, Thank you for looking over the mock-ups and providing more "soothing" language where needed. Sharron and I appreciate your quick effort so that Alicia can implement quickly. Norah, Thank you for forwarding the blurb that is useful too. Looking forward to the informal testing next week. Brent Brent A. Bakken Director, Accessibility Strategy & Education Services Pearson 512 202 1087 brent.bakken@pearson.com Learn more at pearson.com [image: Pearson] On Thu, Nov 2, 2017 at 12:02 AM, Shawn Henry <shawn@w3.org> wrote: > Thanks again for additional work on these! > > Below are the few things that I think need to change before anyone sees > them. Note that these are just quick fixes so we can show them next week -- > the wording can be improved later if we want. > > * W3C "Creates global standards to define web accessibility" > -> "Develops international standards for the Web." > > * WAI "Creates tools and resources to help you understand and implement > W3C accessibility standards." > -> "Develops standards and support materials to help you understand and > implement accessibility" > > * "Web Content – WCAG" and "WAI-ARIA" links > -> "Accessibility Standards Overview" link > > * "Did you know the W3C provides technical guidelines and standards for > making the web accessible?" > -> "Did you know the W3C provides guidelines and other standards for > making the web accessible?" > > See also Norah's wording: <https://lists.w3.org/Archives > /Public/public-wai-eo-site/2017Nov/0002.html> > > (I have some other tweak suggestions throughout, but those can wait.) > > Thanks!!! > > ~Shawn > > > On 11/1/2017 12:41 PM, Frausto, Alicia wrote: > >> Hi All, >> >> Here are the mock links + summaries for the versions we can go over at 1. >> >> *V1: * >> >> https://visa.invisionapp.com/share/5WE8V9VBJ#/261508336_v1-A >> udiencePortals >> >> -Addition of tagline to top nav >> >> -Addition of events icon to top nav >> >> -Top nav goes full width of page >> >> -First row of body: >> >> o‘What is WAI?’ as text w/photographic background image >> >> -Second row of body: >> >> o‘What is accessibility’ content for users new to the topic >> >> oLink to guidelines >> >> oLatest news >> >> -Third row of body: >> >> oAudience portal, with people photos and links to multiple resources for >> each >> >> *V2:* >> >> https://visa.invisionapp.com/share/CAE8VAS2R#/261508335_v2-I >> nfographicLinks >> >> -Addition of audience portal to top nav >> >> -Addition of events icon to top nav >> >> -Change Search Bar to Icon >> >> -Top nav goes full width of page >> >> -First row of body: >> >> o‘Making the Web Accessible’ include tag line >> >> oHorizontal Infographic to explain relationship between W3C, WAI, and the >> User >> >> -Second row of body: >> >> oAudience portal, with people photos and links to multiple resources for >> each >> >> -Third row of body: >> >> oW3C Callout ‘Did you know…” with links >> >> *V3*: >> >> https://visa.invisionapp.com/share/YEE8V8CWZ#/261528150_v3-I >> nfographicSimple >> >> -Addition of audience portal to top nav >> >> -Addition of events icon to top nav >> >> -Change Search Bar to Icon >> >> -Top nav goes full width of page >> >> -First row of body: >> >> o‘Making the Web Accessible’ include tag line >> >> oVertical Infographic to explain relationship between W3C, WAI, and the >> User >> >> -Second row of body: >> >> oAudience portal, with people photos and links to multiple resources for >> each >> >> -Third row of body: >> >> oW3C Callout ‘Did you know…” with links >> >> *V4:* >> >> https://visa.invisionapp.com/share/U3E8VB7S6#/261528099_vers >> ion4_InfographicLinks >> >> -Addition of events icon to top nav >> >> -Change Search Bar to Icon >> >> -Dropdown to navigate to persona portals in top navigation >> >> -Top nav goes full width of page >> >> -First row of body: >> >> o‘Making the Web Accessible’ include tag line >> >> oInfographic to explain relationship between W3C, WAI, and the User >> >> oAddition of Resource links in infographic >> >> -Second row of body: >> >> oFeatured Perspective Video & Latest News share row >> >> Thanks, >> >> Alicia >> >> *From: *"Bakken, Brent" <brent.bakken@pearson.com> >> *Date: *Wednesday, November 1, 2017 at 8:09 AM >> *To: *"Wise, Charlotte" <cwise@visa.com>, "Green, James" <jgreen@visa.com>, >> "Frausto, Alicia" <afrausto@visa.com>, Sharron Rush <srush@knowbility.org>, >> Shawn Henry <shawn@w3.org>, WSTF <public-wai-eo-site@w3.org> >> *Subject: *Re: Re: mock-ups and UT info ahead of time -- Re: New >> Navigation Idea >> >> [FTR] (forgot to include WSTF list) >> >> -------- Forwarded Message -------- >> Subject: Re: mock-ups and UT info ahead of time -- Re: New >> Navigation Idea >> Date: Tue, 31 Oct 2017 16:09:34 -0500 >> From: Bakken, Brent <brent.bakken@pearson.com <mailto: >> brent.bakken@pearson.com>> >> To: Wise, Charlotte <cwise@visa.com <mailto:cwise@visa.com>> >> CC: Shawn Henry <shawn@w3.org <mailto:shawn@w3.org>>, Green, >> James <jgreen@visa.com <mailto:jgreen@visa.com>>, Frausto, Alicia < >> afrausto@visa.com <mailto:afrausto@visa.com>>, Sharron Rush < >> srush@knowbility.org <mailto:srush@knowbility.org>> >> >> >> >> Hey Charlotte, >> >> Thanks for the detail of where everything is at in prep for TPAC and >> follow-up after. >> >> Just so that I am clear on this, we (the task force) will be able to >> see everything that will be shown to anyone at TPAC during the call >> tomorrow (or sometime before TPAC) so that we can be okay with the content >> shown, correct? >> >> We can't have anything shown that we all have not all seen and >> quickly checked for "hives" with this audience. There are people at TPAC >> that if they see something, even on a draft sample page, they will raise a >> big concern or issue with and blow it way out of proportion. We want to >> avoid that at all costs.** >> >> ** >> >> *I am not suggesting by any means that we spend time wordsmithing >> anything to any degree.* Just that we look over everything and remove or >> change anything that would cause this type of reaction with this audience. >> I am referring to content mostly and not design and visual styling. We can >> do this in the meeting tomorrow. If there are further changes after that, >> we can set up some more time on Friday or Monday to look over drafts as >> well. We just have to all be okay with what we are going to be putting in >> front of this audience for feedback. >> >> Looking forward to seeing it all. >> Brent >> >> >> >> *__* >> >> Brent A. Bakken >> Director, Accessibility Strategy & Education Services >> Pearson >> >> 512 202 1087 <tel:512%20202%201087> >> brent.bakken@pearson.com <mailto:brent.bakken@pearson.com> <mailto: >> brent.bakken@pearson.com <mailto:brent.bakken@pearson.com>> >> >> Learn more at pearson.com <http://pearson.com> <http://pearson.com> >> Pearson >> >> >> >> On Tue, Oct 31, 2017 at 3:10 PM, Wise, Charlotte <cwise@visa.com >> <mailto:cwise@visa.com> <mailto:cwise@visa.com <mailto:cwise@visa.com>>> >> wrote: >> >> Hi Shawn, >> >> We don't have additional user testing feedback at this time, and >> Alicia, Erica and I are still working on the home page variants (in fact, >> the versions you see tomorrow likely won't have completely final "sample" >> text). We'd love to get them to you beforehand but I have a feeling we will >> be working on them right up to the time. >> >> Also, keep in mind that we're not really evaluating these design >> variants for anything *specific* tomorrow. It's more of a preview of what >> we will show to get user feedback on during TPAC--and once we have that >> feedback, then we can spend the time later in November doing a deeper dive >> into any necessary refinements and make a choice as to which one we want to >> go with. So, there's no need to worry about getting exhaustive feedback >> covered on these preliminary variants tomorrow. >> >> Best, >> Charlotte >> >> -----Original Message----- >> From: Shawn Henry [mailto:shawn@w3.org <mailto:shawn@w3.org> >> <mailto:shawn@w3.org <mailto:shawn@w3.org>>] >> Sent: Tuesday, October 31, 2017 2:30 PM >> To: Wise, Charlotte <cwise@visa.com <mailto:cwise@visa.com> >> <mailto:cwise@visa.com <mailto:cwise@visa.com>>>; Green, James < >> jgreen@visa.com <mailto:jgreen@visa.com> <mailto:jgreen@visa.com <mailto: >> jgreen@visa.com>>>; Frausto, Alicia <afrausto@visa.com <mailto: >> afrausto@visa.com> <mailto:afrausto@visa.com <mailto:afrausto@visa.com>>> >> Cc: WSTF <public-wai-eo-site@w3.org <mailto: >> public-wai-eo-site@w3.org> <mailto:public-wai-eo-site@w3.org <mailto: >> public-wai-eo-site@w3.org>>> >> Subject: mock-ups and UT info ahead of time -- Re: New >> Navigation Idea >> >> Hey Charlotte & Alicia & James, >> >> Please would y'all send material before the meeting? If you have >> UT feedback, we can review that outside of the meeting and save precious >> meeting time for any discussion needed. Also for the mock-ups, I'd do >> better if I can look at them ahead of time, rather than just seeing them >> for the first time in the meeting. >> >> Thanks!!! >> >> ~Shawn >> >> >> On 10/31/2017 2:26 PM, Shawn Henry wrote: >> > I can meet at 1:00C on Wednesday. Good to find a time that >> works for y'all! >> > >> > On 10/31/2017 2:06 PM, Wise, Charlotte wrote: >> >> I have the same issue with the CEO visit as James. Alicia >> will as well. Could we postpone the meeting to 1 pm CST or find a time on >> Thursday or Friday? >> >> >> >> Best, >> >> Charlotte >> >> ------------------------------------------------------------ >> --------- >> >> ------------------------------------------------------------ >> --------- >> >> ------------------------------------------------------------ >> --------- >> >> ------------------------------------------------------------ >> --------- >> >> ------------------------------------------------------------ >> --------- >> >> ------------------------------------------------------------ >> --------- >> >> ------------------------------------------------------------ >> --------- >> >> ------------------------------------------------------------ >> --------- >> >> ------------------------------------------------------------ >> --------- >> >> ------------------------------------------------------------ >> --------- >> >> ------------------------------------------------------------ >> --------- >> >> ------------------------------------------------------------ >> --------- >> >> ------------------------------------------------------------ >> --------- >> >> ------------------------------------------------------------ >> --------- >> >> ------------------------ >> >> *From:* Sharron Rush <srush@knowbility.org <mailto: >> srush@knowbility.org> <mailto:srush@knowbility.org <mailto: >> srush@knowbility.org>>> >> >> *Sent:* Tuesday, October 31, 2017 12:58:14 PM >> >> *To:* Eric Eggert >> >> *Cc:* Green, James; Frausto, Alicia; WSTF; Shawn Henry; Wise, >> >> Charlotte; Brent Bakken >> >> *Subject:* Re: New Navigation Idea >> >> Let's do plan to meet tomorrow if only briefly. Charlotte, I >> believe you and Alicia have comps to share, is that right? >> >> >> >> Since we are closing in on TPAC week, I think we should take >> advantage of every chnace we have to get together and be sure we all >> understand what we are sharing and what we expect to learn from our time >> there. >> >> >> >> Thanks all, let's try to meet at the normal time tomorrow. >> if brent can't run the meeting I will give it a try. >> >> >> >> Best, >> >> Sharron >> >> >> >> On Tue, Oct 31, 2017 at 3:24 AM, Eric Eggert <ee@w3.org >> <mailto:ee@w3.org> <mailto:ee@w3.org <mailto:ee@w3.org>> <mailto: >> ee@w3.org <mailto:ee@w3.org> <mailto:ee@w3.org <mailto:ee@w3.org>>>> >> wrote: >> >> >> >> __ >> >> >> >> Hi James, TF, >> >> >> >> I will be on a plane to Austin during our normal meeting >> time and not available on Thursday. I might be able to carve out time on >> Friday. >> >> >> >> Brent, Sharron: Can you pick a day and time? Or do we >> want to >> >> roll the TF meeting into the regular meeting if there is >> time? (In >> >> the sense that we have the regular meeting for some time, >> then offer >> >> everybody not on the TF to leave and switching into TF mode.) >> >> >> >> Best, Eric >> >> >> >> On 31 Oct 2017, at 3:25, Green, James wrote: >> >> >> >> Hi Team,____ >> >> >> >> __ __ >> >> >> >> I will not be able to make our TF meeting as >> scheduled this >> >> week. I am assuming we want to meet, so I propose Eric >> running the >> >> meeting or pushing it back to Thursday, same time.____ >> >> >> >> ____ >> >> >> >> Let me know what everyone thinks,____ >> >> >> >> James____ >> >> >> >> __ __ >> >> >> >> __ __ >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> Eric Eggert >> >> Web Accessibility Specialist >> >> Web Accessibility Initiative (WAI) at World Wide Web >> Consortium >> >> (W3C) >> >> >> >> >> >> >> >> >> >> -- >> >> Sharron Rush | Executive Director | Knowbility.org | >> @knowbility >> >> /Equal access to technology for people with disabilities/ >> >>
Received on Thursday, 2 November 2017 14:04:47 UTC