Search the Community
Showing results for tags 'screen reader'.
Found 2 results
Hi there. I am trying to figure out what format Evernote notes open in when they open in a new window on the Desktop client. This is because I am totally blind and every screen reader I use cannot read a note opened from the Evernote desktop client. It just has a blank screen. However, when I do a Select All and then copy the text to the clipboard and paste into a plaintext app like notepad, I can read the note. The problem is that all the formatting is gone. So, I understand that Evernote uses the ENML for notes, but I wonder if there would be a way to have a note rendered in the desktop client as if it were a webpage, so that I could sue my screen reader's web viewing mode to read the note and its contents? it's as if the note is just an image of the actual note itself. i'm just trying to figure out how to make this desktop client usable because the web clients (beta and regular) are becoming less so as time goes on. But when I open up a new note in the desktop client and look at the window class, it says something like WebhostView. I don't know what that signifies but it seems like there would be a way to get the text of the note in some sort of navigable format. The problem, too, is that I can't read what I've written in a note once i"ve typed it. Because whatever it is being rendered in isn't recognized by the screen reader to read it back. So, my main question is, how is the info in a note encoded in the desktop client and how hard would it be to modify that encoding so that it looks like, say, an email in MS Outlook, which is fully accessible with my reader. Does anyone have any advice on this? Sorry for the long post, but I just wanted to get my ideas out there. Thanks, Dave
Hello, First of all, let me start off by saying that I am a totally blind computer user. I recently signed up for evernote and have been using a combo of the web beta and the windows desktop app. Both are resonably accessible with my prefered screen reader, Window-eyes by gwmicro. A screen reader is software that uses synthasized speech to convey information to a blind/visually impaired individual through the use of keyboard navigation. This information can be manipulated and customized in hundreds of ways to suit the user's preferences. However, I just now read the announcement about testing the new beta and was not expecting to be told NOT to use the beta if we were using assistive tech software. I have to dmit, I'm disappointed in this request. I feel that, should the Evernote creators care about accessibility at all, they should invite screen reader and other AT users to test their product for accessibility issues. Wouldn't it be better to address them now in a beta stage and not have to deal with them later? Don't I have as much right to test the web beta as any other user and provide feedback? It's a little like saying, "you can test our new chocolate candy, but not if you like milk chocolate." Isn't that still chocolate? It would seem to me that, by not wanting AT users to participate in the beta test, Evernote is limiting their potential market of users of their products. Presently, I can't write notes in the desktop app, I can't delete them in the web app. The desktop app has hotkeys, the web app doesn't, and I use full keyboard navigation for my entire computing experience. it's faster to drag and drop notes into notebooks in the web app, there are more shortcuts for moving notes in the desktop app though. What the Evernote devs might not know is that Window-eyes is currently in a beta testing cycle of its own. Part of this testing is for an advanced and entirely new version of Browse Mode. This is the interface mode that the software uses to communicate with web page elements. By rewriting the code for this feature from the ground up, GWMicro has made it possible for Window-Eyes users to FINALLY use a web version of the Evernote client; both the old version and new beta version are now somewhat accessible. Also, they have updated the use of Window-Eyes so that it can read the screens on the desktop app; it was unable to do this before due to a conflict in the UI of the native app. I still can't read the document window to write notes in the desktop app though. So, keeping this in mind, I would like to enquire as to the decision to not have AT users involved in a beta testing cycle of a product that is by far the most used notetaking software out there. Also, I would like to request that AT users be given the freedom to test and submit accessibility issues with the beta as well as suggestions on how to make it easier to navigate. By doing this, the devs would be weeding out issues that they might have to deal with in future. By not doing this, the devs are showing a sad lack of ambition to make their products accessible in a world where accessibility is becoming more of a recognized issue in the web development community. One need only look at mlb.com and amazon.com at the tops of their respective pages to notice this. I would appreciate any feedback on this issue and encourage discussion. I will freely admit that these are my opinions and, as such, can be taken with however many grains of virtual salt you desire. That said, I thank you for reading this and hope you will consider my concerns as valid. If you would like any further explanation and/or a demo of how I navigate the web and your evernote apps in particular, please don't hesitate to ask. thank you, Dave