Achieving WCAG and screen-reader accessibility, for the most part, isn’t too hard—web fonts and robust button formats have removed the need for text-as-image-file graphics, and CSS layouts rescued all of us from inaccessible, table-based presentations. But tab elements, with their semantically-separated button controls and content panels, present a special challenge. In this session, we’ll discuss:…
Contributor: Andrew Ortolano
Lead developer at Lipman Hearne, serving the nonprofit sector, specializing in enrollment and philanthropic solutions.