1) About accessibility : A Button, which implemented in the way i imagined, would produce a <div> tag as well as a <canvas> tag. Both tags occupy the same position, but the <div> tag is on the top of the <canvas> tag. So, the <div> tag takes the responsibility for accessibility. 2) Everything (focus management, event handling, etc.) is still under browser's control. Each widget has its own <canvas>, not a universal shared one. You press Tab, and the focus jumps from button1 to button2. Nothing ever changes.
accessibility On Feb 17, 6:21 pm, Thomas Broyer <[email protected]> wrote: > How about accessibility? (one of the biggest complaint against canvas) > > Canvas is not meant for this use case. > > And why re-implement everything (focus management, etc.) that the browser is > already capable of (and at no cost)? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
