Amusingly enough, I actually started thinking a bit about this just the other night after being told about a talk given at Dropbox about accessibility. To be up front, we know very little about it and the other night was the first time I&#x27;d ever tried to use a screen reader, so it&#x27;s something we aren&#x27;t likely to be good at right of the gate, but it is something we&#x27;ve been setting ourselves up for completely by accident.<p>Many of the previous versions of Eve would be pretty completely inaccessible, so your dismissal would definitely be warranted. The version we&#x27;ve decided to run with though basically has three parts: a document editor, embedded spreadsheet cells, and a fancy plain english search. All three of which have a history of accessible solutions, so that makes me much more optimistic that we can provide something nice here. Along the way, another thing we&#x27;ve been very cognizant about is making sure no matter what form of input you prefer, Eve should be efficient and useful to you whether you&#x27;re using a keyboard, a mouse, or touch. Many of the interaction issues we&#x27;d need to solve to better work with screen readers popup when trying to support complete keyboardability, but I have no delusion that there will be plenty more to solve there. Another interesting aspect of this version of Eve is it&#x27;s really easy to imagine a voice interface to since virtually everything is done using plain english queries - it&#x27;d be kind of like having Jarvis in your google docs.<p>Admittedly, we don&#x27;t know what we&#x27;re doing when it comes to accessibility, but it is something we&#x27;ve been thinking about indirectly and it&#x27;s something I think we can at least do more naturally than the code editors of the world.<p>Thanks for raising the issue and it&#x27;s something I&#x27;d like to have a more concrete answer for in the future.