As a speedgolfer, I can view SpeedScore's graphical user interface, so that I can get an overall feel for how the app is organized

[chundhau]

Acceptance Criteria

App UI Components

• [x] App displays the SpeedScore log as its favicon in its browser tabs
• [x] App displays "SpeedScore" in the title of its browser tabs
• [x] App has top navigation bar with side menu icon, app icon, and content area title
• [x] App has expanding/contracting side menu that displays mode-specific menu items plus "About" and "Log Out"
• [x] App has bottom mode bar for switching between three app modes: "Feed," "Rounds," and "Courses"
• [x] App has floating action button for performing most common task in current mode
• [x] App has placeholder text and icon displaying mode name main content area

App Accessibility

• [x] Use semantic HTML wherever appropriate
• [x] Use ARIA attributes wherever appropriate

App Visual Design

• [x] Blue theme color
• [x] White text color
• [x] Menu items and buttons highlighted when hovered

Implementation Todos

• [x] Create ch2 branch
• [x] Create code snapshots (tags) for each implementation step

Testing:

• [x] Visual inspection of the user interface
• [x] Navigation of the user interface using a screen reader emulator

[chundhau]

I checked off the "To Do" items all at once, since I created this issue after a first draft of the chapter code was complete. I am satisfied with the state of the code at this point, but after the chapter code undergoes further review, things could change, in which case I may need to re-open this issue.

[chundhau]

After committing to accessible design, I have to redesign the Chapter 2 code. I am doing this in a different branch accessible-base-app. Once I am done reimplementing the entire app in this branch, I will break the code into segments to be presented in the early chapters of the book and implement the code in corresponding chapter branches (e.g., ch2, ch3), including tags to index project snapshots at strategic points in each chapter. Stay tuned!