General (site-wide): UX issues

Testing conducted with these details in mind:

Target audience: tech individuals, everyday people who want to learn more about their role in being more than not racist but becoming an antiracist and understanding how intersectionality applies to them
Used Chrome Version 84.0.4147.89 (Official Build) (64-bit) and Firefox 78.0.2

Issues

[ ] Update the site title, description, and favicon for search engines, etc.
[x] Needs to be mobile responsive
- Specifically, the menu items overlap with each other
[ ] Pages need breadcrumbs, especially so you can figure out where you are
- For example, the library page is a separate page linked from the educate section, but when you're on the library page, you won't know how you got there
- Expected format example: Home > Educate > Library
[ ] Need site map (index of all available forms, glossary of words, resources, etc.)
[ ] Explore the use of a subnavigation along with the main / toplevel navigation
- This is useful for getting a big picture of the site and its offerings so you know exactly where you should go
- Several pages are buried under the main navigation that makes it difficult to browse or know where to return (examples: take a learning path, library, and train your team are linked off educate)
[ ] Make forms consistent style (each form has a different look and feel, which is inconsistent)
- Since many options currently go to google forms, would it be possible instead to use a surveymonkey account (or a smarter form service) to make a more generic form with options for why they're contacting that goes to different question/answer response paths depending on what they select?
[ ] Add space between footer and end of page
[ ] Make all font styles consistent and complementary (Ally Guide being a different font is distracting)
[ ] Digital accessibility concerns
- Are labels and buttons in order and can they be tabbed through for those with digital accessibility needs (for example, alt text for images)
- All words reflected within an image should be removed and instead added as actual text for screen readers and those with digital accessibility needs
[ ] Make treatments for buttons consistent across site so that users have an understanding and expectation of how the site operates
[ ] Why is "stay updated" a form rather than having an email entry field in the footer for email subscriptions
- Is this something you want to start recording in mailchimp or surveymonkey?
[ ] Move toolbar / menu to the top instead of in the middle
- [ ] Remove highlight box around subscribe because this makes it seem that you're on this page regardless of where you are in the site (highlight this with an email or subscribe + symbol instead)
- [ ] If the Ally.Guide placeholder is in the toolbar, it looks like a button (especially with the red underline) but it doesn't link to anywher—is this a home button? If it's a home button, maybe we can use a home icon and add a title to the site instead

OpenSourceFellows / ally-guide-app

General (site-wide): UX issues #49

Issues