search

asb / raspi-config

Configuration tool for the Raspberry Pi. Now maintained at https://github.com/RPi-Distro/raspi-config
Other
264 stars 332 forks source link

Raspi-config is not approachable by the blind... #11

Open rpural opened 11 years ago

rpural commented 11 years ago

I was approached by a blind user who'd purchased a Raspberry Pi, and was very pleased with it, except for the initial set-up, which he was unable to successfully perform on Wheezy. This, in large part, was due to the fact that his "screen" did not discern any color differences for him, so that in raspi-config, he cannot tell what line is highlighted.

Could there be a way to make the menu more handicap-friendly? Such as placing an arrow (-->) on the currently selected line, or some other indicator? Or, could there be a way to start it, or drop out into a non-curses, text-only version, that would be more friendly to mechanical readers?

He has tried to go through it several times, with very little success. I'm hoping that someone at your end might be able to more easily address the issue than me trying to learn the logic being performed and modifying it for him.

mircea-vutcovici commented 11 years ago

I think it is possible to show the cursor in whiptail by changing the TERM to vt100.

Could you please test if the following command is accessible? TERM=vt100 whiptail --yesno "asd" 20 70 1 It would be interesting to know which screen reader the person is using.

On Tue, Jan 15, 2013 at 4:51 PM, rpural notifications@github.com wrote:

I was approached by a blind user who'd purchased a Raspberry Pi, and was very pleased with it, except for the initial set-up, which he was unable to successfully perform on Wheezy. This, in large part, was due to the fact that his "screen" did not discern any color differences for him, so that in raspi-config, he cannot tell what line is highlighted.

Could there be a way to make the menu more handicap-friendly? Such as placing an arrow (-->) on the currently selected line, or some other indicator? Or, could there be a way to start it, or drop out into a non-curses, text-only version, that would be more friendly to mechanical readers?

He has tried to go through it several times, with very little success. I'm hoping that someone at your end might be able to more easily address the issue than me trying to learn the logic being performed and modifying it for him.

— Reply to this email directly or view it on GitHubhttps://github.com/asb/raspi-config/issues/11.

rpural commented 11 years ago

I'll talk to him and see if we can test this, but I don't think it will help during the initial boot of the system, will it?

Sent from my iPhone

On Jan 18, 2013, at 1:34 PM, Mircea Vutcovici notifications@github.com wrote:

Sorry, the command is: TERM=vt100 whiptail --yesno "asd" 20 70 1

On Fri, Jan 18, 2013 at 2:32 PM, Mircea Vutcovici <mirceavutcovici@gmail.com

wrote:

I think it is possible to show the cursor in whiptail by changing the TERM to vt100.

Could you please test if the following command is accessible? https://ajax.googleapis.com/ajax/libs/jquery/1.9.0/jquery.min.js It would be interesting to know which screen reader the person is using.

On Tue, Jan 15, 2013 at 4:51 PM, rpural notifications@github.com wrote:

I was approached by a blind user who'd purchased a Raspberry Pi, and was very pleased with it, except for the initial set-up, which he was unable to successfully perform on Wheezy. This, in large part, was due to the fact that his "screen" did not discern any color differences for him, so that in raspi-config, he cannot tell what line is highlighted.

Could there be a way to make the menu more handicap-friendly? Such as placing an arrow (-->) on the currently selected line, or some other indicator? Or, could there be a way to start it, or drop out into a non-curses, text-only version, that would be more friendly to mechanical readers?

He has tried to go through it several times, with very little success. I'm hoping that someone at your end might be able to more easily address the issue than me trying to learn the logic being performed and modifying it for him.

— Reply to this email directly or view it on GitHubhttps://github.com/asb/raspi-config/issues/11.

— Reply to this email directly or view it on GitHub.

mircea-vutcovici commented 11 years ago

If it will work, we can determine if the problem is with the terminal cursor. This will isolate the problem further. On Jan 19, 2013 8:21 AM, "rpural" notifications@github.com wrote:

I'll talk to him and see if we can test this, but I don't think it will help during the initial boot of the system, will it?

Sent from my iPhone

On Jan 18, 2013, at 1:34 PM, Mircea Vutcovici notifications@github.com wrote:

Sorry, the command is: TERM=vt100 whiptail --yesno "asd" 20 70 1

On Fri, Jan 18, 2013 at 2:32 PM, Mircea Vutcovici < mirceavutcovici@gmail.com

wrote:

I think it is possible to show the cursor in whiptail by changing the TERM to vt100.

Could you please test if the following command is accessible? https://ajax.googleapis.com/ajax/libs/jquery/1.9.0/jquery.min.js It would be interesting to know which screen reader the person is using.

On Tue, Jan 15, 2013 at 4:51 PM, rpural notifications@github.com wrote:

I was approached by a blind user who'd purchased a Raspberry Pi, and was very pleased with it, except for the initial set-up, which he was unable to successfully perform on Wheezy. This, in large part, was due to the fact that his "screen" did not discern any color differences for him, so that in raspi-config, he cannot tell what line is highlighted.

Could there be a way to make the menu more handicap-friendly? Such as placing an arrow (-->) on the currently selected line, or some other indicator? Or, could there be a way to start it, or drop out into a non-curses, text-only version, that would be more friendly to mechanical readers?

He has tried to go through it several times, with very little success. I'm hoping that someone at your end might be able to more easily address the issue than me trying to learn the logic being performed and modifying it for him.

— Reply to this email directly or view it on GitHub< https://github.com/asb/raspi-config/issues/11>.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/asb/raspi-config/issues/11#issuecomment-12454826.