Week 3 — A New Format

So I decided to try something different, and turn this into a weekly post summarising all I have achieved. This will improve things for you as the content will be less fragmented. I’m also hoping this can form a part of my ‘project diary’ to include in my final submission.

For items which stand on their own I will produce a separate post.


  • Report is now available on Github with travis-ci building the pdf on commit
  • Met with my academic supervisor
  • Listed my key stakeholders
  • Identified the most common web frameworks
  • Identified the most common web components

So yeh, a lot’s been going on!

The report

So I mentioned previously how I would like to produce my report completely in the public eye. I discussed this with my supervisor (just to check I’m not going to shoot myself in the foot) and I have the all clear! I am writing it using latex a tool for typesetting, and I found this great template courtesy of Jordan Suchow.

Wearing my software engineering hat I thought “wouldn’t it be great if every time I pushed to github it built me the pdf and served it from somewhere so anyone could read it”. So I got looking around and stumbled upon someone who had the same idea, but had already gotten something working, took some inspiration and set up my own.

The latest version can always be found at this url: https://github.com/Geeman201/building-a-more-accessible-web-report/releases. You can find my .travis.yml file on Github if you want to get yourself setup.

Meeting with supervisor

It was great to catch up with him. I had a few questions which we we’re able to resolve, mainly around the report aspect and the ethics of potentially working with and observing people with assistive technologies. None of my tasks should have ethical issues, but I still need to submit a short form to the ethics board just to verify what I’m doing is acceptable. I also updated him on my progress to date (which unfortunately has been slower than I had hoped).

Key stakeholders

As with most projects its good to identify those who are involved early on so for one you know who your target audience is, but secondly who needs to be involved throughout the process. The main ones other than myself are:

  • Users of assistive technologies, without them this whole task would be impossible and have no impact
  • My two supervisors — Academic and Company, these are the people I will eventually present my report to.
  • Web development engineers — If I want to improve the experience for the users these are the people that need to produce better code

Common web frameworks

See other post — March snapshot for common web frameworks