This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.
After running my original website through WAVE web accessibility evaluation tool it came back with three errors, 2 alerts, 1 feature, 5 structural elements, 0 HTML5 and ARIA and 0 contrast errors. My first error was that I had an empty heading above my second column. Also, I did not have any alternative text tags for any of the images on my site. Overall, across the different webpages on the site, the same errors were present throughout. To combat this problem, I added alternative text tags and deleted the empty heading. According to WAVE, my website is rather accesible.
Another issue with my website is that it is not easy to read on a phone or any other device other than a computer. I need to make sure my website is accesible to people using it on a variety of different devices. I added media query tag so my website is more accesible on other devices. The tag I used made the menue bar stay in view when scrolling. I was considering adding a second break between the two colums, but it ended up looking strange having two pictures at the end of a large block of text. If I were to start this project over again, I would consider designing for moble first. This concept is popular when designing websites. Rather than designign for a website only, the designer makes sure to consider how the design would look on other, smaller devices. Making my website more readable on different devices ensures that I will reach more users. Users who are looking at my website on a variety of devices.
On the W3C CSS Validation Service one error and one warning was found. The error was a parse error on line 69 of the new CSS. This parse error has to do with the media query tag that allows the website to be more assesible on modle and other devices. I think this might not be an error in my CSS, but rather an error in the validation software. The problem was I did not have a closing bracket at the end of the tag. Adding a closing bracked fixed the problem. When I ran my CSS through the checker agian it came back with no errors.
On the W3C Markup Validation Service two errors in my HTML showed up. The first error was at line 4, column 22. I was not using the prefered name of a character. For error two, I again was not using the prefered name for the same character as in the first error. I made the changes the website signified.
According to Cross Browser Testing my website is accessible in Microsoft Edge 15, Google Chrome 65, Firefox 59, and Safari.
The initial HTML5 and basic Dublin Core metadata was added to each page of the site.
After running the new website through WAVE web accessibility evaluation tool it came back with 0 errors, 3 alerts, 2 features, 4 structural elements, 0HTML5 and ARIA, and 0 contrast Errors. Overall, there were no major problems to adress. A few of the alt tags were long and the headings were out of order for one heading level. Other than that, adding the new code did little to the accesibility of the document.
On the W3C CSS Validation Service it came back with no new errors. Which is expected becuase the new code did not alter the css. It was only put into the html of the website. Therefore, the css problems were resolved in my initial validation checks.
On the W3C Markup Validation Service seven errors were found. The first error is a bad value schema.dc for attribute rel on element link: The string schema.DC is not a registered keyword. The rest of the errors stated, the scheme attribute on the meta element is obsolete. Use only one scheme per field, or make the scheme declaration part of the value. According to some research I did online, html5 does not support DCTERMS as it appears on the initial meta data. After fixing the meta data I was able to get no errors. The first error was on line 7: bad value schema.dc for attribute rel on element link: the string scheme.dc is not a registered keyword. I deleted that line and left only < link rel="schema.dcterms" href="http://purl.org/dc/terms/">. The next step was to fix incorrect writing of the Dublin Core metas. Rather than DC. the meta for Dublin core in HTML5 is dcterms: followed by the meta that is supported by dublin core. For example, DC.creator became dcterms:creator. Finally, the language marker for English was written incorrectly. Rather than "English" the abbriviation "en" should be used throughout.
For search engine optimization, I used tags in the Dublin Core. The tags I chose went from general to specific. Therefore, if someone searched specifically for the name of my site or one of the pages, those will come up. Also, if someone searched for web help or other general terms, my site will appear for those searches as well. Findability was increased through the use of these tags.