Web Standards


Alt Attribute

You know the ‘alt’ attribute is required for all media, but what are you supposed to put in there? In this article we discuss the alt attribute, how it is used, and best practices for making your ALT attribute work for both search engines and screen readers more »

WCAG Recommendations

Web accessibility is the ability of users with various functional requirements to use web sites easily and effectively. This includes keyboard access, screen enlargement, screen reading and voice recognition. If you don’t think this is important, just remember that your two most important visitors are blind, deaf and unable to use a mouse: googlebot and slurp, Google and Yahoo!’s spiders, can only read the text of and tab thru your page. They can’t see your cool mouseover effects, interpret the nuances of your images, or enjoy your nifty sound effects. WCAG were the guidelines when the web was mostly static. For AJAXed sites, read up on ARIA – Accessible Rich Internet Applications instead.
more »

ARIA – Accessible Rich Internet Applications

With the proliferation of internet applications, there has been an increase in the number of sites requiring javascript that update without page refreshes (AJAX). This imposes accessibility issues that weren’t addressed by WCAG 1, as those specifications were written when “sites must work without javascript” was a reasonable accessibility specification. With the increase of web based “applications” (versus “sites”) requiring JavaScript, and improved support of javascript in assistive technologies, new accessibility issues have emerged. ARIA attempts to handle some of those issues. In this article we discuss the inclusion of roles, states and properties your dynamically generated content can be made accessible to assistive technologies.
more »