- Description
- Website-Preview
- Live-url
- Developer(s)
- Technologies
- Foresight
- Incentive
- Challenges
- Reasoning
- Solution
- Take-away
This webpage displays an example of how a website should be structured with properly placed semantic elements in a HTML file that corresponds to an external CSS file.
[Link to deployed URL] (https://jjg1488.github.io/web-accessibility-website/)
James J. Gault
-
[Screen-Reader] (https://chrome.google.com/webstore/detail/chromevox-classic-extensi/kgejglhpjiefppelpmljglcjbhoiplfn)
The future of this website is based upon Website Accessibility Standards. As standards change, this webpage will continue to reflect the proper structure and implementation of semantic elements in html.
Driven by the need to display proper semantics that will allow any and everyone to navigate this page and any future web pages clearly and with meaning.
There were parts in the HTML of this website that had lots of similar lines that had to be consolidated. Also, this HTML is without any styling tags. All of the styling and positioning tags were placed in the CSS file.
This project was built as a means to show competence in Website Accesibility with HTML semantics.
If websites are not up to date with accessibility, then there could be lawsuits brought about. Not practicing Web Accessibility could result in a challenge under Title III of the ADA. Title III of the ADA does not support public accomodations that discriminate against someone on the basis of a disability. To avoid consequences, work with a developer that displays Web Accessibiity compliance. [Click Here For More Information] (http://www.adatitleiii.com/2016/02 lack-of-website-accessibility-regulations-is-no-bar-to-suit-another-judge-affirms/)
Web Accessibility is a vital piece of web development. It gives everyone the advantage and ability to leverage and learn the same information.