Jump to content

dcbahr

Level 2
  • Content Count

    31
  • Joined

  • Last visited

Everything posted by dcbahr

  1. I have been advocating for this feature ever since I became an evernote user. If they implemented keyboard shortcuts, us blind people would be able to use the web version more which is really the only version from the desktop that I could remotely use. Why it hasn't been implemented, I have no idea. It seems so simple and since evernote is all about writing, wouldn't it be easier to keep your hands on the keyboard so you can keep writing away and just use keyboard shortcuts? Furthermore, as I have advocated, if the people at Evernote were to implement keyboard shortcuts, they might be able to get an entirely new market of blind computer users such as myself to use their apps. The only app that is sort of accessible is the Iphone app, and that's even a stretch. The other issue is that the EML is propriotary and the HTML elements that screen readers need to access are all barred from use. But still, even with that aside, keyboard shortcuts are the main thing in the web version that would make it work.
  2. Because the view that EN uses to display their notes is unreadable to Every screen reader out there. i've tried them all, even with OCR it doesn't work. It's labeled as a class called WebViewHost and it doesn't seem to employ any sort of browser-like functionality, say, like, an html5 window might. So I can't interact with it like a normal webpage. It's just an unknown control type and reclassing the window as an edit box or rich edit box doesn't give me any feedback either. It's very frustrating because I don't know how to get around it. Other than that, the desktop app works fine. If I could render that WebViewHost as something that Window-Eyes could read, like a regular webpage (so I could use html-esque navigation hotkeys), then we'd really be getting somewhere.
  3. Because the view that EN uses to display their notes is unreadable to Every screen reader out there. i've tried them all, even with OCR it doesn't work. It's labeled as a class called WebViewHost and it doesn't seem to employ any sort of browser-like functionality, say, like, an html5 window might. So I can't interact with it like a normal webpage. It's just an unknown control type and reclassing the window as an edit box or rich edit box doesn't give me any feedback either. It's very frustrating because I don't know how to get around it. Other than that, the desktop app works fine. If I could render that WebViewHost as something that Window-Eyes could read, like a regular webpage (so I could use html-esque navigation hotkeys), then we'd really be getting somewhere.
  4. Hi. Could you PLEASE implement keyboard shortcuts into the next release of EN Web Beta? As a totally blind computer user, I can't use the Windows desktop version fully and the Ios version won't let me edit a note with Voiceover once I've created it. And the current web version has no shortcuts. This has been brought up before on the forum, and if you put the shortcuts in, I might be able to use the application fully. It's admittedly frustrating to have to devise hacks that are sketchy at best to use a program that is so widely used and convenient. I see so much potential and ways to improve accessibility, I really want to help in that arena. But I feel like I have to beg for keyboard shortcuts, when I know that others who are keyboard-based users could benefit from them as well.
  5. Hi. I would like to use emails to send to Evernote for a journal, but I want to put a date into the subject line. If I do that, I'd like to Not create a reminder, just to title the note with the date. Is this possible? can I put a - before the date or something so EN doesn't recognize it as a reminder?
  6. Great! I will definitely look at these. Yes, please, if anyone has suggestions either to the suggestion of a new web interface or the original post about rendering of notes, that would be much appreciated.
  7. Hey Rob, just saw your reply to this. I had forgotten about the copy note link option from the desktop client. However, the web clients (both beta and classic) are not very accessible in any browser. Internet Explorer shows me a bunch of script that my reader just spits out pointlessly. Firefox is just...a mess with the clients, that's about all I can say. If they would implement keyboard shortcuts in the new beta, then it Might, just might, get better. But as of now, that seems to be on the back burner for some strange reason.
  8. I am working both avenues of asking Evernote about their accessibility aspirations (or, sadly, lack thereof) and trying to work with some screen reader scripting developers on making Evernote more accessible. I'd do it myself, I just don't know any code and have no idea what to look for when it comes to making it accessible. I just know what works and what doesn't. Hence, my reason for starting this particular thread. I think that if I can get the answer to how a note is rendered (if that's even close to the popular term) in a new window, how it is portrayed and what sort of background language, I can start asking developers how to go about making it somehow accessible. I've looked at the API documentation for the windows cloud api, but I have no idea what I'm reading, it's way over my head. So, yes, any insight is greatly appreciated. What I wish to impart to the Evernote developers is that they are missing out on a pretty large market of people who are blind who could use their service if they would redesign it to make it more accessible. It would probably also allow for more bugs to be worked out in the long run. Just my thoughts. Thanks, Dave
  9. 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
  10. Nothing officially announced, but I did notice that some formatting shortcuts now work (Ctrl-B for Bold, Ctrl-I for Italics, Ctrl+1 through 9 for header styles, etc.) I couldn't find a way to display them all though (i.e. quick help window/overlay). Yeah, it would be really nice to see those keyboard shortcuts, as it is the web and desktop clients are becoming less and less accessible to screen reader users, it makes me sad.
  11. apologies, I've been away from this discussion, but have the keyboard shortcuts been implemented yet? If so, where can i get a list of them?
  12. still no keyboard functionality? I can't use the beta and test it for accessibility until that's implemented, but I will give this week's release a shot, maybe a bug was fixed that I need fixed. As it stands, when I go to find a notebook, the page somehow refreshes and shoots me to the top of it. I'll test with a few different screen readers and see if it's just window-eyes. I'm sorry, I don't want to be a nag, I just think that this beta could really work well if accessibility isaddressed right off the bat.
  13. yep, I agree, put in those keyboard shortcuts ASAP. There really aren't ones for the current web app. I actually have figured out that I can't even beta test the new web ap without having keyboard shortcuts of some kind. My screen reader gets really confused even just trying to find a notebook. So, I'd love to help with accessibility but I can't even access the interface.
  14. Yes, I agree, this would make the new beta accessible to screen reader users. the desktop app is not accessible, nor is the ios app. The old web app is kind of accessible. please see my other post on this issue. There is a setting to use global keyboard shortcuts in the new beta, but the latest release notes say that they are not implemented. For me, that defeats the purpose of testing the new beta since I can't really get around it with my screen reader. It's a catch22. I think I will indeed have to put in a support ticket.
  15. A mobile site is a blessing and a curse. The amazon.com site used to be really nice and easy to navigate. However, they have changed the site now and actually have neglected to label the images on there properly. So much for being accessible. On the other hand, the evernote mobile site is fairly useful. At least, for adding a single note. Other than that, can't do much with it, so I'm back to using the desktop client for making notebooks and deleting notes, and the web app (preferably mobile) for writing them. But that shouldn't be necessary . the interfaces of both programs/apps should be accessible. I wonder how I could get this noticed more by the developers?
  16. 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
×
×
  • Create New...