August 2015 Newsletter
The results to our most recent survey have been published.
Our commentary on the survey data that indicates a significant increase in ZoomText and Window-Eyes usage among respondents.
Our October 6-7 WebAIM training is full, but we have just opened registration for our next training to be held December 8-9 in Logan, Utah.
Lainey Feingold has provided another update on the recent legal developments impacting technology and information access for people with disabilities.
Examples of maps that are optimized for users with visual disabilities.
Dennis Lembrée provides a good summary of and links to articles discussing the accessibility implications of this increasingly popular design technique.
Straight talk from Karl Groves on the realities of web accessibility lawsuits and complaints.
These guidelines will cover the major things you need to know in order for your products to be "design-ready" to meet the minimum of standards in Section 508 and the Web Content Accessibility Guidelines 2.0.
Quick Tip: Identifying Dialog Windows
There is no accessibility requirement to identify links or buttons that open dialogs or prompts (though if there is a visual indication of this, it should also be made accessible to screen reader users). However, it can be helpful for screen reader users to know that a link or button will open such a pop-up, as opposed to taking them to another page or submitting a form. Simply adding aria-haspopup="true" to the link or button will cause the screen reader to identify that the control will open a dialog when activated.