Update 4

What I’ve done:

I’ve added ARIA to the homepage login process. So now the screenreader will be able to detect:

  • if a wrong password is entered
  • forgotten password link
  • create new user link

What I’ll be doing:

I’ll be continue to add ARIA to the rest of the website, as the screenreader can skip important features of the website. Another issue is the that ordering of things being read is not logical. I want to see if I can control the flow of items being read so as to illustrate the structure of the website better.

Problems:

I’ve been editing Orion within Orion itself. When I create a git branch, do my chances, and try to send a pull request, it merges my changes with changes from the past as well. However, if I do this the “regular” way (i.e. through terminal), it works just fine. I’ve contacted Ken and Carolyn about this. Ken says he will look into the issue and will also fix the wiki so as to make the process clearer.

Update 3

What I’ve done:

I made a list of accessibility issues on the Orion hub. These issues can be found in this document:

https://docs.google.com/document/d/1Vkm_JMkl7tH0otyOfzT09I4b1vmI9CFDZN3R1-g0gt8/edit?usp=sharing

I created a subset of them on Bugzilla and have started on working to fix them.

What I’ll be doing:

I’ll be getting familiar with the codebase and I’ll learn how to self-host the Orion project so that I can test the changes made locally. I’ll continue to fix the bugs, with the guidance of Carolyn and Ken.

Problems:
None

Update 2

What I’ve done:

As per Carolyn’s instructions, I read up on what makes a website accessible. Here are a list of useful websites to view on this topic:

After that, I activated VoiceOver on my computer (the built-in screenreader for Macs) and tried to do simple tasks, such as sending an email. I found it very unnatural at first, as I was so tempted to use my mouse to navigate instead of listening to an automated voice and using hot keys. The tutorial that is provided (as tedious as it may be) is definitely something you should go through as most of the commands are not intuitive (i.e. you can’t just tab around – there are specific commands for various actions).

What I’ll be doing:

  • Applying my new found knowledge on to the Orion project to find areas where it fails on accessibility
  • Compose a list of bugs (and fix them!)

Problems:

  • None