- From: Eric Eggert <ee@w3.org>
- Date: Sat, 04 Nov 2017 09:07:34 -0500
- To: "Shawn Henry" <shawn@w3.org>
- Cc: "Frausto, Alicia" <afrausto@visa.com>, WSTF <public-wai-eo-site@w3.org>, "Green, James" <jgreen@visa.com>, "Wise, Charlotte" <cwise@visa.com>
On 4 Nov 2017, at 8:04, Shawn Henry wrote: > Thanks, Eric! > > Sorry I didn't get to reply sooner. :-( Comments below. > > Eric Eggert wrote: >> Hi Alicia and TF! >> >> I did implement the idea with some caveats and changes, I wonder what >> you and others on the TF are thinking: >> >> * >> >> The current implementation *only works on wide screens*. I did >> not manage to make the solution responsive just yet. > > No problem -- it's a prototype in development! > >> * >> >> There are *browser bugs* with the multi-column layout and I had >> not the time to work around them (I’ve seen it *mostly in Firefox*: >> wrongly positioned items in the navigation and list items >> disappearing. It seems to be tolerable for UT currently.) > > fyi, I think it's working for me on Windows Chrome. > >> >> * >> >> I made some changes to the header, so it did not look out of >> place too much (as we ripped the main nav out of the header area). I >> hope it is OK as it is for UT. > > Looks like we'll be tweaking header later anyway. I think OK as is for > UT (although having "Initiative" on separate line might draw > comments). It should not be on wide screens, there is one size where it breaks but I did not bother to fix it as the header is not working in smaller sizes anyway. >> * >> >> Instead of using the arrow that has little contrast (dark blue on >> lighter dark blue). I opted to give the navigation more of an tab >> look when the submenu is opened and also added a yellow bottom border >> to the main icon, similar as we had before, to add to the visibility >> and accessibility. > > I don't have strong reactions either way at this point. > >> >> * >> >> I still have the shifting-down of the sub menu because a) it was >> easier to implement with limited time, and b) because I see many >> advantages for accessibility (works well with a screen magnifier, for >> example) and kind of don’t want to let go of it :-) I am totally >> interested if it is a problem in UT… > > I don't have strong reactions either way at this point. > > +1 for "easier to implement with limited time" for now! > >> >> * >> >> I left the chevron in there after the sub-pages because it was >> there and I think it highlights that the following items are >> sub-items, but I’m happy to remove it before the UT. > > -1 for leaving the chevron, although not super strong I’ll remove it Monday. > >> https://w3c.github.io/wai-website/ > > The biggest issue I see is that sub-pages are wrapping to 2 columns. > We don't want that -- even though it will mean un-even length columns. See above: There are browser bugs with multi-column layout. Either we have it the way it is now, or it breaks horrendously. (Missing links…) We can search for another solution when we have the final nav content and design, but it is impossible to have a good solution at this stage. In addition to browser weirdness it sometimes had only one item in one column. It just was weird. I tried multiple solutions, if anyone has a good working idea, I’m happy to put it on the prototype, but I think I tried everything. > Hover & Focus or Click to open? I think hover & focus. We can talk > about this later. (I suspect click instead of hover will annoy UT > participants.) I feel click is the better solution for accessibility, as outlined above. I am personally annoyed by menus that disappear when I move my mouse, so I guess we will have both reactions in the UT. Let’s see :-) > > Thanks, Eric! > > ~ Shawn > >> >> Best, Eric >> >> On 25 Oct 2017, at 20:04, Frausto, Alicia wrote: >> >> Hi Eric, >> >> Here’s the zeplin link for building out a full-width nav: >> >> https://zpl.io/awqwA1D >> >> >> thanks! >> Alicia >> >> On 10/25/17, 10:30 AM, "Eric Eggert" <ee@w3.org> wrote: >> >> On 25 Oct 2017, at 17:24, Shawn Henry wrote: >> >> > Hi folks, >> > >> > Sharron and I missed these GitHub issues, so figuring others >> might >> > have, too. So here is what I know of October work on home page >> and >> > navigation: >> > >> > * Updated goals of the home page and some brainstorms (as >> discussed in >> > 11 October Task Force telecon): >> > >> https://www.w3.org/WAI/EO/wiki/Redesign_-_October_Revisions#Home_page >> > >> > * Homepage Brainstorm GitHub #101 -- includes mock-up ideas >> that Norah >> > sent in e-mail previously and mock-up ideas from Brent: >> > https://github.com/w3c/wai-website-design/issues/101 >> > >> > * Navigation Brainstorm GitHub #102 >> > https://github.com/w3c/wai-website-design/issues/102 >> > >> > Also, an important reminder: EOWG resources are only part of >> the WAI >> > website and part of W3C's accessibility work. The >> standards/guidelines >> > themselves are the foundation of the W3C's work on >> accessibility. EOWG >> > resources support the standards. Please see this reminder: >> > >> https://www.w3.org/WAI/EO/wiki/Usability_testing_Oct_2017#Important:_Audiences_and_Tasks_not_included >> > >> > Looking forward to the next iteration of the home page! >> > >> > Thanks, >> > ~Shawn >> >> Thanks for the reminder, Shawn! >> >> Just for completeness sake, here is the email that I wrote which >> details >> what we want to archive with that brainstorming exercise: >> >> https://lists.w3.org/Archives/Public/public-wai-eo-site/2017Oct/0015.html >> >> Looking forward to discuss with all of you in a bit! >> >> Eric >> >> -- >> >> Eric Eggert >> Web Accessibility Specialist >> Web Accessibility Initiative (WAI) at World Wide Web Consortium >> (W3C) >> >> -- >> >> Eric Eggert >> Web Accessibility Specialist >> Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C) >> -- Eric Eggert Web Accessibility Specialist Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)
Received on Saturday, 4 November 2017 14:11:10 UTC