Categories
articles expert

Tips for eCommerce Accessibility

E-shop accessibility: from theory to reality is an article from Juicy Studio discussing issues and proposed solutions for web accessible e-commerce web sites.

Here’s a thoughtful response from Accessibility expert Joe Dolson in his post Accessible e-Commerce Tips.

Categories
forms lists option podcast

Podcast #51: Option Groups (OptGroup)

Option lists with many items may cause problems for users with assistive technology, such as screen readers. The solution is to use the Optgroup element to split options in the Select list into manageable groups. This also better practice for usability.

Download Web Axe Episode 51 (Option Groups [OptGroup])

WCAG 1.0 says: Guideline 2.3 Divide large blocks of information into more manageable groups where natural and appropriate. [Priority 2]

Links

Sample Code:

News

Categories
articles motor

Improving accessibility for motor impaired users

Improving accessibility for motor impaired users is a great article from WebCredible.com.

Topics include:

  • Provide the largest possible area for links
  • Use a focus state for links
  • Provide a visible ‘skip to content’ link
  • Have users opt in for audio
  • What not to do
Categories
jobs

Job Opening for Web Accessibility QA

If you or someone you know has good experience and knowledge in Web Accessibility, and wants a good job in California (Silicon Valley), please contact me, Dennis, at webaxe at gmail dot com. The position is in the QA department for a company that does a financial web application.

Categories
expert podcast wcag

Podcast #50: Analysis of WCAG 2.0

The lastest version of the W3C’s Web Content Accessibility Guidelines is discussed by Dennis, Ross, Jared Smith and Joe Dolson.

Download Web Axe Episode 50 (Analysis of WCAG 2.0)

News

Announcements

  • Refresh Detroit, June 20th – Catherine Hayes Inner Circle Media, Ruby on Rails
  • Refresh San Fran? Refresh San Jose? Who’ll start one?

Questions/Topics Include

  • Do you feel that (good) progress is being made after the concerns voiced about a year ago?
  • Do you feel that “Success Criteria” make more sense than the previous “Priority levels/Checkpoints”?
  • There is still a “loophole” for an alternative accessible page. Is this acceptable?
  • Valid code is still not a requirement (politically motivated?). Should it be?
  • Do you think that the WCAG 2 is too broad and vague?
  • Is the quick reference an acceptable method for developers to understand WCAG2 if the actual documents are to complex?

WCAG 2.0 Links