Requiring JavaScript Some advanced web applications would not be possible without JavaScript. Both Section 508 and WCAG 2.0 allow JavaScript to be required so long as the JavaScript content and interactions are compliant and accessible. Whether you should require JavaScript is not really an accessibility question. It is a general usability question. Some users (most […]
Read Full Post »
Do you use Twitter? Do you use it for work? If so, there are some key actions you can take to ensure that the content you’re tweeting is accessible. Check out our tips: Twitter Put your 800 number in bio line Put prefixes before tweets (PIC, VIDEO, AUDIO, etc.) so that a screen reader users […]
Read Full Post »
Avoid Screen Reader “Freak Out” Modern screen readers are able to read dynamic, scripted content updates within a web page. However, if the content a screen reader is currently reading or focused on changes or is removed/hidden from the page, the screen reader “freaks out” due to this loss of focus, and typically reverts focus […]
Read Full Post »
CAPTCHA CAPTCHA stands for Completely Automated Public Turing test to tell Computers and Humans Apart. A CAPTCHA is typically presented as a graphic with distorted letters or numbers that a user must decipher and enter into a text field. Although CAPTCHA attempts to ensure a response that is generated by a person, nearly all modern […]
Read Full Post »
Empty Table Headers When marking up data tables, avoid empty table headers (<th> element). Empty headers can cause confusion for screen reader users because there is no information to be read for a data row or column, or they may cause the screen reader to associate a header to an incorrect column or row. Pay […]
Read Full Post »
AT news is off-the-hook this week! I kid you not – there’s a lot of it and it covers all sorts of topics, like 3-D prosthetics, hand-free smartphones, smaller & sleeker hearing aids, and much more. Check it all out right here – AT in the news for the week of 2/9 thru 2/13. 3D […]
Read Full Post »
