• Research how to make elements tabbable
• Implement this in the code

Your testing suite should test all of the functionality of the application, including the following:

Class default properties
Class methods
Anything that updates class properties

• User will select a date, duration, number of travelers and choose from a list of destinations
• User should see an estimated cost (with a 10% travel agent fee) for the trip.
• Once user submits the trip request, it will show on dashboard as “pending” so that the travel agency can approve or deny it. (POST)

• Branch must NOT have any login functionality so that accessibility audit is focused on dashboard alone

• Research how to choose colorblindness-friendly color scheme
• Update current DOM using this scheme

• Create method to filter out dates that are no longer "present", filter only specific trips for user id.
• Display all past trips on the dom
• Consider if past trips need less information displayed, as they have already passed and user might not need so much information displayed at a glance for past trips.

• Wire up POST request so user input posts to local server
• Make sure data makes a round trip and renders to the dom (get request can be helper with this)

• Write fetch requests to get data from appropriate endpoints
• GET requests triggers the DOM display functions so that DOM is re-rendered each time API is updated by POST

• Determine what "present" means for this data set
• Create method to get all data that falls into present data for specific user travel data
• Display present trips on the DOM

• Should be calculated from the trips data
• Should include a travel agent’s 10% fee

• Test use-ability of site using screen-reader
• Audit HTML for alt tags

• Write method that will calculate amount spent on trips over year
• Will be for a single user
• Will add 10% for agent fee
  --Note: cost is found in destinations endpoint-- this is accessed using the destinationID in the trips endpoint

• Run lighthouse when branch is finalized to show 90% accessibility score (at least!)

• Display yearly amount spend on the DOM
• Format for readability

• Determine what "upcoming" means-- for example, is it within the next week or the next month (I'd lean towards month).
• Create method that will filter to see if trip for user ID is within the date span to make it upcoming
• Show data for user ID on the DOM

• Write method to filter out only user's requests that have a status of pending
• Display all trips for user ID with "status": "pending"

• Research fonts that are accessibility friendly
• Consider dyslexia as well as colorblindness/ vision

• When first arriving at the site, a user should be able to log in with a username and password.
• Should login with the following:
  username: traveler50 (where 50 is the ID of the user), password: travel
• This should reveal the dashboard
• Will need method to check username and pw against all available users.
• Refer to Get single traveler endpoint