Also, it is good to keep your master branch up to date to reduce the risk of your changes conflicting with other recent changes. I can see that your fork's master branch is about 10 commits behind the main repository.
Here's your fork:
The main hhaccessibility:
This practice pull request was made quite well. Thanks.
In work for a real issue, you should name your branch after the issue you're focused on such as issue-744, if your issue was: https://github.com/hhaccessibility/hhaccessibility.github.io/issues/744.
Also, it is good to keep your master branch up to date to reduce the risk of your changes conflicting with other recent changes. I can see that your fork's master branch is about 10 commits behind the main repository. Here's your fork:
The main hhaccessibility:
![image](https://user-images.githubusercontent.com/11838191/50737726-8aa1b500-119a-11e9-8a52-0c0c81c00e14.png)
You can update your master branch using command sequences at: https://github.com/hhaccessibility/hhaccessibility.github.io/wiki/git-commands