Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Core Text Renderer Accessible in VoiceOver #1491

Open
kolanos opened this issue Jun 19, 2024 · 2 comments
Open

Make Core Text Renderer Accessible in VoiceOver #1491

kolanos opened this issue Jun 19, 2024 · 2 comments
Labels
Renderer Text rendering issues, including CoreText renderer

Comments

@kolanos
Copy link

kolanos commented Jun 19, 2024

Is your feature request about something that is currently impossible or hard to do? Please describe the problem.

Under the Advanced menu in settings for the checkbox Use Core Text renderer appears the message:

(Deprecated) Deselect this option to use the legacy renderer, which is unsupported and will be removed in a future version.

However, at present, the Core Text renderer is not accessible in VoiceOver.

Describe the solution you'd like

Make Core Text renderer accessible in VoiceOver prior to the removal of the legacy renderer.

Describe alternatives you've considered

If the legacy renderer is removed prior to making Core Text accessible then I won't be able to use MacVim anymore as a blind user. And MacVim is great, so this would be a sad day indeed.

I'd have to use gasp emacs? Or use vim in a terminal full time? Yuck.

@kolanos kolanos changed the title Core Text Renderer Not Accessible in VoiceOver Make Core Text Renderer Accessible in VoiceOver Jun 19, 2024
@ychin
Copy link
Member

ychin commented Jun 19, 2024

This is certainly something I would like to support. Thanks for tagging this so I will keep this in mind.

Can you explain a little more about your use case? Are you completely relying on solely the macOS accessibility features to use MacVim? Do you use other text editors and how do they compare (e.g. I know VSCode has a list of accessibility features). Do you use terminal Vim (if so, what terminal emulators)?

Just trying to understand more how you usually use MacVim here.

@ychin ychin added the Renderer Text rendering issues, including CoreText renderer label Jun 19, 2024
@kolanos
Copy link
Author

kolanos commented Jun 23, 2024

@ychin I have used VS Code but have found many gaps in its accessibility. I know it has a Vim mode but everything around it gets in the way. Mac's built-in text editor, TextEdit, is a good example of what a text editor can be in VoiceOver. But it is not well suited for coding. Plus I have been a vim user going on 15 years, so old habits die hard.

As for terminals, Mac's built-in terminal in my experience has been more accessible than alternatives like iterm. I have used vim and neovim in a terminal emulator, and as a fallback this is adequate. I have tried neovim GUIs like neoviee and they are completely inaccessible by VoiceOver. Similar to the Core Text renderer today.

I just recently upgraded to Sonoma and there is (sadly) a new (what I presume to be a) VoiceOver bug in MacVim with Core Text renderer disabled. When I try to type in the command line VoiceOver reads the first : character and then just says `"space" for every character after that. I need to read the entire line to see what is there (VO+L). So even VoiceOver itself sees regressions in this regard.

This feature is likely a big ask. So a possible alternative is a legacy version of MacVim with the legacy renderer intact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Renderer Text rendering issues, including CoreText renderer
Projects
None yet
Development

No branches or pull requests

2 participants