December 2015 Newsletter
We have updated our evaluation quick reference. A one page printable version is also available.
We still have seats available for our training to be held February 2-3, 2016 in Logan, Utah. Register now to secure your seat.
Accessibility is often characterized as additional work, hard to learn and only affecting a small number of people. Those myths have no logical foundation and often stem from outdated information or misconceptions.
When an appetite for aesthetics over usability becomes the bellwether of user interface design, it's time to reconsider who we're designing for.
Goodwill, smart business, and even vague governmental regulation should compel ecommerce businesses to make websites accessible to all potential customers, including those who are blind or deaf or have other problems interacting with a website or mobile application.
Marco Zehe presents the absolute basics of web accessibility.
Quick Tip: Avoid Duplicate ARIA Roles
HTML elements have a default role that is presented via accessibility APIs to screen readers. The <button> element is presented as a button and links are presented as links, for example. ARIA allows authors to define or redefine the role for HTML elements - you can, for example, define a <div> as being a button. But duplicating the HTML default roles in ARIA is not necessary and introduces the possibility for issues. Avoid things like <button role="button">, <a role="link">, etc.