A rough timeline
Feb 23, 2017 · 2 min read
So I met my dissertation supervisor for the first time last week, we had a great chat and I now feel a lot clearer on my general direction and also what I’m going to deliver and how I’m going to deliver it.
Due to the nature of the project I was advised it’s best to break it down into small components that can be completed on a weekly basis. This is likely to evolve over time and I will be using Trello to track what I’ve done and what I’m doing (Kind of in a Kanban way). Here is a link to my dissertation Trello board.
In summary..
February
- Identify ways of working
- Identify stakeholders
- Go out to charities and users and find the most common issues they face
- Identify the most common web ‘components’ (e.g. dialog)
- Understand how accessibility issues can be identified (in the IDE, in the browser?)
- Gather tools for testing hypothesis’
March
- Use tools to assess common web ‘components’ on a range of sites
- Build these components as small web pages using common web frameworks.
- Produce more accessible friendly versions of all components
- Record & document the difference between how tools behave against these components
- Document how to’s and lessons learned
- Build education pages (Maybe a gitbook or something)
April
- Go back to users and ask for them to test the difference
- Produce case studies of them
- Design system for identifying issues in code
- Build a framework to enable addition of rules quickly
- Build a small set of rules
May
- Prepare for submission
These are just headlines. Throughout I hope to write this blog and my report.
