Jump to content

dcbahr

Level 2
  • Content Count

    31
  • Joined

  • Last visited

Community Reputation

14 Neutral

About dcbahr

Profile Information

  • Subscription
    BASIC

Recent Profile Visitors

2,494 profile views
  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
  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
  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
  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 ac
  5. 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.
  6. 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?
  7. 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.
  8. 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.
×
×
  • Create New...