Date: Wed, 19 Apr 2023 22:42:44 +0000 From: Pau Amma <pauamma@gundo.com> To: accessibility@freebsd.org Subject: Re: Terminal Reader and Text User Interface utilities Message-ID: <b31da042eab05384cae245e50dab0083@gundo.com> In-Reply-To: <CAPJrGM1G-3_p3KYEnzPZ%2BLbLapOd47PSOzZOzC1VE9t12uDb0g@mail.gmail.com> References: <CAPJrGM0PX31JoGQ5v65LTE2kXEtraz-0wL_8KSA5sEKnT10beg@mail.gmail.com> <f0819fae07433528ad0e05a02862fe67@gundo.com> <CAPJrGM1G-3_p3KYEnzPZ%2BLbLapOd47PSOzZOzC1VE9t12uDb0g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2023-04-19 21:50, Alfonso Sabato Siciliano wrote: > On Wed, 19 Apr 2023 at 23:30, Pau Amma <pauamma@gundo.com> wrote: > >> Just popping up to say I'll happily be a sounding board and help >> explain >> or formalize requirements if needed, but I'm not going to take a more >> active role in that discussion since I'm not a screenreader user >> myself. > > I'm not a screenreader user myself, too. So I asked for suggestions. > However to understand the problem is sufficient to run a simple: > $ dialog --infobox "test" 0 0 | espeak > or > $ bsddialog --infobox "test" 0 0 | espeak Oh, I understand the problem. (Or at least, I think I do.) What I know I *don't* understand is usability or UX flaws in proposed solutions that would be obvious to a screenreader user. Hence, I need to take a backseat unless and until it looks like I'm needed for something. > Our installer (bsdinstall) is built on TUI dialogs, so to find a > solution > for a simple > TUI utilityfor the PORTS options can be the first step to provide an > accessible > (speech) installer. I got that, yes. -- #BlackLivesMatter #TransWomenAreWomen #AccessibilityMatters #StandWithUkrainians English: he/him/his (singular they/them/their/theirs OK) French: il/le/lui (iel/iel and ielle/ielle OK) Tagalog: siya/niya/kaniya (please avoid sila/nila/kanila)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b31da042eab05384cae245e50dab0083>