Accessbility Discussion Topics

• Using the WAVE tool to find errors for an ADA (American's with Disabilities Act) lawsuit?
• Can the next major version of WCAG be technology specific instead of technology agnostic?
• Section 508 Table of contents with links to all sections
• Alternate text for CSS background images, considerations and techniques
• Should WCAG 2.1, the next version of WCAG, require conformance on MAC OS
• What did WCAG do for people with low vision and cognitive disabilities
• Quick guide to what's new in WCAG 2.1 First Public Working Draft and How to Comment
• List of Proposed Success Criteria and Requirments for WCAG 2.1 as of Oct 27, 2016
• Long home pages, Smooth Scroll, and other animations
• My personal wish list for WCAG.NEXT
• Should shopping carts notify users who are blind that they have been updated.
• What are WCAG Success Criteria and how to write them?
• Should WCAG require all functionality on the site to work with a mouse/pointer in addition to existing keyboard requirements?
• Can the PDF Accessibility Checker ensure WCAG conformance?
• Unifying WCAG and PDF/UA for PDF Footers
• Should the accessibility industry revise the profile of a Keyboard-Only User
• CSUN: MathML Emerging Solutions
• Proposal for an HTML5 Footnote mechanism
• CSUN Talk 4 Hot Issues
• How well is Figcaption working for accessibility
• Is placeholder text a viable accessible label
• Can aria-label be put on an element that is for static content?

"How To" Topics

• Demystifying WAI-ARIA, 18 ARIA attributes for average web developers
• A quick accessibile Mega Menu using bootstrap buttons and dialog boxes
• Alternate text for CSS background images, considerations and techniques
• Make a heading in WordPress
• Making Math Accessible
• Make a table header row invisible
• An accessible expand-collapse mechanism
• When to use alt="" to conform to WCAG
• Is a missing Title on an iframe a WCAG Failure?
• How to toggle an aria-expanded on/off with JavaScript
• Ambiguous Link text options
• Long descriptions options
• Table Summary options
• Complex table options

Testing

We are often testing code and accessibility techniques in assistive technology and various browsers. Here's a links list archive of tests:

• Testing fieldsetand legend withdiv and span with JAWS and NVDA with aria-describedby, aria-errormessage and aria-live
• Testing error messages with JAWS and NVDA with aria-describedby, aria-errormessage and aria-live
• The new Success Criteria on Status Changes using ARIA-LIVE rigions
• Testing ARIA-LIVE with display:none and innerHTML
• Can a heading go inside a table caption element?
• Alternate text for background images, considerations and techniques
• Review the funtional Evaluation Test cases of the automatic checker from the University of Illinois
• Inserting Content with CSS and testing Assistive Technology and APIs
• Test 2 labels pointing to one form field with palceholder aria-hidden toggles labels on off so only one is on at at time
• aria-describedby and placeholder: what happens to AccDescription
• aria-describedby and labelledby
• CSS Background images and CSS inline content
• Testing sub headings inside a <header> Element
• Test the scope attribute

Feel free to comment on Twitter @davidmacd

Author information:

David MacDonald is a veteran WCAG member, co-editor of Using WAI ARIA in HTML5 and HTML5 Accessibility Task Force Member. Opinions are my own.