As a Web developer, I would vote in favor of retaining the element.ariaFoo properties, and encourage other browser vendors to support that in upcoming versions. We've dropped namespace support in the name of developer and author convenience; this falls in the same bucket. Writing e.ariaChecked = true is far easier than the more convoluted e.setAttribute(...)
Marc Silbey writes: > I'm sorry for my delayed reply - as Chris mentioned, I was at MIX last week, > on vacation until Tuesday and out of the office yesterday with a sinus > infection...it's been a busy :) > > Before I dive into the details of this thread, I want to step back and say > that I'm excited for IE to be a part of ARIA and to be mostly in-line with > other browser implementations with our beta - I think we're working together > to make a very positive change in web accessibility. > > We've been testing our implementation and will continue to test it using the > test cases linked to in the best practices document. That said, we're > clearly not done with ARIA yet. I appreciate the open feedback we
