TiddlyWiki / TiddlyWiki5

A self-contained JavaScript wiki for the browser, Node.js, AWS Lambda etc.
https://tiddlywiki.com/
Other
8.02k stars 1.19k forks source link

Improve usability for visually impaired users #1682

Open Jermolene opened 9 years ago

Jermolene commented 9 years ago

As raised in this thread, it would be desirable to improve the usability of TiddlyWiki for visually impaired users by introducing the following features:

In order to make these changes effective we'll need to work closely with visually impaired users who can try it out and give us feedback. There are many issues that it would be helpful to understand:

roma0104 commented 9 years ago

Here is some quick reading for anyone interested in this: Much is about actual text design but there are some some about machine/human interface:

What I have learn from a couple hours of reading, on your last two points @Jermolene:

Action like:

sukima commented 9 years ago

Pressing space will make TW5 listen, followed by a x will close the topmost tiddler.

Oh this just made my little Vim :heart: flutter with joy. The make TW5 listen part practically described a keyboard based modal interface just like with Vi / Vim's philosophy. One could reword it to fit the same:

Press Esc to return to normal mode, followed by an x to delete the current character.

The connection is uncanny!

Jermolene commented 9 years ago

Hi @sukima I'm very keen to have a really decent keyboard interface (I reposted some early sketches to the group - https://github.com/Jermolene/TiddlyWiki5/commit/c2e99647d02f0bc8d16feac6039b49afb445bc14#diff-12b7f28a28eef72270ce72ba360bfa9c).

Also, thanks for reminding me of the <kbd> element:

https://github.com/Jermolene/TiddlyWiki5/commit/6942efa6289c9f1d99ea9f63972aa314ac06a8b1

tobibeer commented 9 years ago

I think there's plenty room, especially for improving the usability of the editing experience ...via keyboard rather than mouse. The add-this-popups have their ways of impinging on usability. In, I think GotoPlugin for TW2 the search results popup was not only accessed by pressing the DOWN key, but also got focus that way so that one could select an option and hit ENTER, let alone ESC out of the popup to go back to the input while hitting TAB would move on to the next element away from the input.

cary-rowen commented 2 years ago

Hi @Jermolene

I'm a visually impaired user of TW and I'm amazed and excited about TW's Accessibility, Thank you, this is great! Currently I want to know, as a visually impaired user using NVDA, how to add plugins, is there any other option for visually impaired users besides drag and drop?

Grateful

abesamma commented 2 years ago

Hi @cary-rowen, it's good to hear that TiddlyWiki is accessible to you! It's a credit to the developers. There is still more we can do as a community I'm sure and I'm interesting in hearing more in this regard.

With respect to your question: Like ordinary tiddlers, plugins can be imported via the import button as json files or tid files. If the plugin contains JavaScript files, then after importing, TiddlyWiki will ask you to save the wiki and reload it in the usual manner. Otherwise, the plugin may work immediately without prompting you for a refresh.

Hope that helps. Let us know if you have any other questions or concerns.

On Sun, Apr 3, 2022, 08:26 Rowen @.***> wrote:

Hi @Jermolene https://github.com/Jermolene

I'm a visually impaired user of TW and I'm amazed and excited about TW's Accessibility, Thank you, this is great! Currently I want to know, as a visually impaired user using NVDA, how to add plugins, is there any other option for visually impaired users besides drag and drop?

Grateful

— Reply to this email directly, view it on GitHub https://github.com/Jermolene/TiddlyWiki5/issues/1682#issuecomment-1086779703, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB6NVYXF56BOBXJ2SPCWVN3VDETYLANCNFSM4BBGMBRA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

AllenChen-Xingan commented 2 years ago

As a screen reader user as well, it’s a great news to hear that we can import plug-ins via no drag and drop. however for most plug-ins from Github or other tid projects, how to translate plug-in links to JSON /tid files

abesamma commented 2 years ago

@AllenChen-Xingan if the project has a demo tiddlywiki (and that is usually the case) that shows the plugin in action, exporting the plugin tiddler should do the trick, since all the necessary shadow tiddlers composing the plugin is packed into this one plugin tiddler. So you can simply export them as json files, then import them into your tiddler.

I recommend visiting TiddlyLinks for links to these tiddlywiki demo pages.

AllenChen-Xingan commented 2 years ago

@abesamma great thanks for your response. i was trying to import this relink plugin. i clicked on the "drag&drop" link then clicked more and select export as Json file. next importing to my own tiddly file but i still did not see the plug-in in the plugins list.

pmario commented 2 years ago

@AllenChen-Xingan ... Just to be sure: The relink plugin requires a "save" and "browser reload" after you did install it.

cary-rowen commented 2 years ago

thanks @pmario @abesamma

As Allen said, I tried importing 'tiddlers.json' and after clicking the "save" button my Chrome browser downloaded another html file, unfortunately I didn't find the plugin I just installed in this new file. Of course, no new plugins were found in the previous HTML. btw, as a screen reader user, The way I would prefer might be to copy the plugin's URL and paste it in my TW to install the plugin.

All the best

Cary

pmario commented 2 years ago

btw, as a screen reader user, The way I would prefer might be to copy the plugin's URL and paste it in my TW to install the plugin.

@cary-rowen ... Thanks for the info.

But I think the URLs for plugins are hard to understand, if read by a screen reader. For example https://tiddlywiki.com/#%24%3A%2Fplugins%2Ftiddlywiki%2Finternals

Or do you have an other URL in mind?

cary-rowen commented 2 years ago

Hi @pmario I should be very clear about the source of the URL, so there is no need to judge what plugin this is by the URL. I'm not sure I fully understand your doubt.

Best