Welcome to the Treehouse Community
The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.
Kartik Kapoor3,016 Points
In the accessibility course there are a lot of things to consider and adhering to everything will take forever.Solution?
In the accessibility course there are a lot of things to consider and adhering to everything will take forever. At the same time one would like that their site is accessible to as many as possible .So how do designers and developers go about it?
Ran ShemTov14,148 Points
This is actually not true. Accessability (as goes with commenting and common practices on your code) is something that should be done while coding, and not as quality check. for example. if you have a photo and want it to be accessible, you don't add alt later on, you do that the day you write the <img> html code. about vision and contrast. Most of the designs today don't have a problem of contrast or something similar, so it's just about seeing if what you already have is good enough.
Gina Scalpone21,330 Points
The best solution is to keep these accessibility guidelines in mind when you are designing and coding a website. You should always check accessibility after, but if you pay attention to it from the beginning, you will spend less time on accessibility in general, and you will not need to make many big changes to the design afterward, which just eats up time.
Design the site well from the get-go. Use the alt attribute, don't put text in images (unless it's a wordmark), don't use tables for layout (something I learned was good years and years ago), use relative units/responsive web design and if you find yourself ever having to write "Best viewed in <browser>", you know you've done something wrong.
Unless you're captioning a bunch of videos, making the site accessibility compliant is not that hard to do. A good way to ensure things are going well is to use online validators for your code during and after completion of the coding. There are even tools to test contrast (foreground/background coloring). Another great tool to see how your site looks to visually-impaired people and search engines is to pull it up in Lynx or some other text-only browser. If your site works in Lynx, it will work in anything.
Jonathan GrieveTreehouse Moderator 90,845 Points
Until such time as another accessibility course comes out on Treehouse I would suggest focusing on the WCAG The Web Content Accessibility Guidelines.
It's not great to look at, but it contains all the agreed guidelines for creating accessible websites and the recommendations for getting websites meeting certain conformance levels.
Check it out here! http://www.w3.org/TR/WCAG20/