-
Let’s return to the data visualizations we evaluated for Assignment 2.
-
For each visualization:
- Explain (with reference to material covered up to date, along with readings and other scholarly sources, as needed) whether or not you think this data visualization is accessible, reproducible, and equitable.
Your answer...
- How could this data visualization have been improved (in terms of accessibility, reproducibility, equity)?
Your answer...
- Explain (with reference to material covered up to date, along with readings and other scholarly sources, as needed) whether or not you think this data visualization is accessible, reproducible, and equitable.
-
Word count should not exceed (as a maximum) 300 words for each visualization.
- This ongoing assignment ensures active participation in the course, and assesses learning outcomes 2 and 3:
- Apply general design principles to create accessible and equitable data visualizations
- Use data visualization to tell a story
Component | Scoring | Requirement |
---|---|---|
Data viz classification and justification | Complete/Incomplete | - Data viz are clearly classified as good or bad - At least three reasons for each classification are provided - Reasoning is supported by course content or scholarly sources |
Suggested improvements | Complete/Incomplete | - At least two suggestions for improvement - Suggestions are supported by course content or scholarly sources |
🚨 Please review our Assignment Submission Guide 🚨 for detailed instructions on how to format, branch, and submit your work. Following these guidelines is crucial for your submissions to be evaluated correctly.
- Submission Due Date:
HH:MM AM/PM - DD/MM/YYYY
- The branch name for your repo should be:
assignment-3
- What to submit for this assignment:
- This markdown file (assignment_3.md) should be populated and should be the only change in your pull request.
- What the pull request link should look like for this assignment:
https://github.com/<your_github_username>/visualization/pull/<pr_id>
- Open a private window in your browser. Copy and paste the link to your pull request into the address bar. Make sure you can see your pull request properly. This helps the technical facilitator and learning support staff review your submission easily.
Checklist:
- Create a branch called
assignment-3
. - Ensure that the repository is public.
- Review the PR description guidelines and adhere to them.
- Verify that the link is accessible in a private browser window.
If you encounter any difficulties or have questions, please don't hesitate to reach out to our team via our Slack at #cohort-3-help
. Our Technical Facilitators and Learning Support staff are here to help you navigate any challenges.