Web accessibility - Aria or no Aria, that is the question!
Was wondering if any DU web developers have ventured into the world of web accessibility using Aria. I work in a small design group and we have just started reviewing all of our apps, forms, etc. for web accessibility. I find myself doing less and less design and more advanced mockups using minor Javascript/Jquery coding to make them look real to the clients, and basic payment forms that feed to an external payment processor.
I've been using NVDA and ChromeVox to "test" our forms with screen readers. Truthfully, the old forms without Aria, even though they're formatted using layout tables, seem to work better than some of the newer forms containing Aria code. Everything I read re: Aria says the first rule of Aria is to NOT USE ARIA. In addition to testing with the screen readers, we also use Lighthouse, Wave, and Site Improve accessibility checkers.
Today I've been beating my head against a wall trying to troubleshoot a programmer's code to tell him what he needs to put in to make a question prompt, instructions, and the field read properly. Also trying to troubleshoot a set of radio buttons. When I tab to the first one, it reads fine, arrow or tab to the 2nd one and it totally ignores the text.
