Please visit my completed webpage at: https://dvicj.github.io/Horiseon-Accessibility/
Horiseon is a marketing agency, which specializes in making their clients web presence more meaningful and productive. They specialize in social media presence, search engine optimization, and online reputations. Horiseon has expressed interest in making their website more accessible and easy to use for those with disabilities. On the backend, they would like a more organized and purposeful code so that any future developers will have an easy transition in working with their website. Horiseon knows the importance of SEOs and how important user experience on a website can be. Horiseon also finds it important to protect themselves from any potential litigation from lack of accesibility.
It was my job to "refract" the code to meet common accessibility standards such as:
- alt attributes
- header attributes that accurately describe the content of the webpage to assist with search engine optimization
- a descriptive title
While "refracting" the code, I was also tasked with making the code more organized, easy to understand and accessible to anyone who may be working on this project in the future. I did this by:
- updating all of elements to be more nuanced and specific
- consolidating duplicate CSS values
-added comments to the HTML and CSS documents to further organize the content and make it easier to understand
I am working on this project because I believe that everyone should have equal access to the internet. If someone is differently abled, it does not mean that they shouldn't be able to enjoy the internet in a meaningful and engaging way. Improving the accessibility of this website will make it available to a portion of the population that it was not available to before.
Features:
There is no installation required. All files must remain in the position in which they are saved to ensure that all links, styles and photos function properly.
Below are examples of the links for the CSS style sheet and the images used in this webpage.
In the gif included below, I have demonstrated how all of the bookmarks work. When the links in the navigation bar are clicked, they will jump to the corresponding section in the webpage.
These are some sources I used to help me along:
Here are the highlights of what I learned and issues I had while refracting this code. For a more throrough experience, please consider reading the Wiki for this repository!
- The importance of using semantice elements over more general elements.
- Adding meta tags and other keywords in the head section.
- Consolidating CSS selectors and organizing them to make sense with the flow of content in the HTML document.
- The importance of the "cascade" and in what order and precedence that values are assigned.
- The usefulness of comments and proper indentaion in understanding code more clearly.
In all honesty, I found putting together this README to be the most challenging part of this challenge. It was fun to learn the README "language" and I liked creating the images and gif, but I found myself pretty stuck on the "Installation" and "Usage" sections of this document. Even after googling examples, I'm still not sure that I understood what those two sections are for. I'm sure understanding will come with more practice.
MIT License
Copyright (c) 2020 Devin Jones
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.