Accessibility

Nobody has claimed this yet.

The vision of druid includes accessibility, and I think it should drive architectural decisions. For example, imgui has a reputation for not being easy to integrate accessibility features; we want to avoid that.

I've looked a little into accessibility (most recently, watching the relevant [SwiftUI video](https://developer.apple.com/videos/play/wwdc2019/238/)), but don't have a very strong sense what that would entail. One of the key features is integration with speech for visually impaired users, but there's also control over focus and selection.

There's a little bit of work in the Rust ecosystem, including [jdm/accessible](https://github.com/jdm/accessible). It would be good to cooperate with others sharing the concern.

I've been thinking about this for a while, but the impetus to file this issue now was a yaah.dev [blog post](https://yaah.dev/2020-accessibility), and a link to resources in the [Reddit discussion](https://www.reddit.com/r/rust/comments/duxrcq/2020_rust_accessibility/).

Start by reviewing the linked SwiftUI accessibility video and the Rust jdm/accessible project, then compare their approaches with druid's architectural goals. The issue names no files or tests; done would require a concrete accessibility direction, including speech support, focus and selection, and potential cooperation with related Rust efforts.

Written by the indexing model from the issue text.