I think Scott makes the right point here; screen reader vendors bear the responsibility for reflecting the current state of the DOM, not just the static HTML. While I'd love to make Cappuccino as accessible as possible, only part of the equation can ever lie with the framework. And I don't think its in anyone's best interest to halt progress on pushing the boundaries of the web while we wait for everyone to catch up. I'm confident that all these things will come together over time. After all, Cappuccino is only a few days old.
by Ross Boucher — Sep 08
@Nick
I think Scott makes the right point here; screen reader vendors bear the responsibility for reflecting the current state of the DOM, not just the static HTML. While I'd love to make Cappuccino as accessible as possible, only part of the equation can ever lie with the framework. And I don't think its in anyone's best interest to halt progress on pushing the boundaries of the web while we wait for everyone to catch up. I'm confident that all these things will come together over time. After all, Cappuccino is only a few days old.