Most often the result is not fully accessible; browser and assistive technology is inconsistent; and implementations vary across the web. This is why it’s always better to use native selects with HTML/web. (Native components is also a better choice for native apps as well.) Don’t forget that HTML selects can be styled with CSS; see these resources by RTD, Filament Group, and LugoLabs.
If you must implement a custom select dropdown, you will most like need to use the ARIA listbox role, combobox role (which specifies a composite widget), and often a combination of those roles. The option role is also required and usually a few other ARIA attributes (for label, state, etc.).
Here are some great examples which will save many folks a lot of time!
It’s 2015, so hopefully web developers know that table elements should not be used for layout. There are many reasons why CSS for layout is better but at the core, HTML tables are data tables; they’ve always been meant for data.
But even today, sometimes a table is used for layout, for whatever reason—time constraints, lack of CSS skills, legacy code, etc.
If a table is used for layout, add ARIA role of presentation to the table element. This will remove the table elements from the Accessibility API which provides for a better user experience for users of assistive technology, particularly screen readers.
Other elements such as caption, summary, and thead should be removed. See the Microsoft resource ARIA Presentation Table Error.
Here’s a code example derived from a W3C example for the use of role=presentation. The following code in the HTML tree:
Becomes this in the accessibility tree:
Here are some great links from this past summer. Enjoy!
Here are some good tools, code examples, and other resources for developing with WAI-ARIA. Know any other good recent ones?
Last week, my author Dennis Lembree attended the 28th Annual International Technology and Persons with Disabilities Conference (better known as CSUN) at the Manchester Grand Hyatt in San Diego, California.
Dennis presented one session “Developing an Accessible Widget with ARIA” representing his day job company. You may download Dennis’ PowerPoint file here.
WebAIM announced that there is now an API for WAVE, their web accessibility evaluation tool. It has a very affordable pricing model, and the first 100 “credits” are free with registration.
Besides the sessions, there are many activities happening at CSUN including the Tweetup, SS12 Finals, and the first WordPress accessibility meetup! A highlight was Deque Systems’ “Amazing Evening” event featuring a guitar player who played with his feet, and who was also a hilarious comedian!
Props to the Toronto accessibility crew who had great representation again. Met more Canadians this year (thanks to @Jennison) including Bill Gregory, George Zamfir and Jorge Mori.
Recommended session presentations:
Other great resources:
Mark your calendar for CSUN14 which is scheduled for 17-22 March 2014. In the meantime, you can plan for the upcoming, second annual Global Accessibility Awareness Day (#GAAD) on May 9th!