On Wed, 2020-09-16 at 19:17 -0500, Michael Catanzaro wrote:
On Wed, Sep 16, 2020 at 10:55 pm, majid hussain mhussaincov93@gmx.com wrote:
hi,
i'm no dev but
i'm blind would functional include being accessible to orca the screen reader?
after all to a blind person like me having an accessible setup experience is a requirement?
or after I install the system, I would be in the dark?
Majid
I think it makes sense to have a criterion to ensure, at minimum, that the screen reader is working throughout the initial setup process, yes. orca was completely broken in F33 until last week [1] and we only noticed by coincidence, since it doesn't get tested much.
Unfortunately right now the login screen is not accessible (regression, [2]). gnome-initial-setup is pretty hard to use with just a screen reader. And anaconda doesn't seem to be accessible at all (at least, I don't know how to get orca to read anything in anaconda). So things would probably need to first be in better shape before we can actually start enforcing a blocker criterion to ensure it stays working....
Right, I pretty much agree with Michael.
The way I'd want it to work in the criteria, ideally, is we'd say something like "all desktop requirements must be met for blind users with assistive technology, e.g. screen reading" - i.e. rather than this being a criterion exactly, we'd expect sufficient a11y support to be in place that *all* the desktop criteria would be met for blind users. But as Michael says, it sounds like we haven't really got things in good enough shape yet that we'd be able to enforce such a requirement right now, so that should be fixed first.
On Wed, Sep 16, 2020, 20:42 Adam Williamson adamwill@fedoraproject.org wrote:
On Wed, 2020-09-16 at 19:17 -0500, Michael Catanzaro wrote:
On Wed, Sep 16, 2020 at 10:55 pm, majid hussain mhussaincov93@gmx.com wrote:
hi,
i'm no dev but
i'm blind would functional include being accessible to orca the screen reader?
after all to a blind person like me having an accessible setup experience is a requirement?
or after I install the system, I would be in the dark?
Majid
I think it makes sense to have a criterion to ensure, at minimum, that the screen reader is working throughout the initial setup process, yes. orca was completely broken in F33 until last week [1] and we only noticed by coincidence, since it doesn't get tested much.
Unfortunately right now the login screen is not accessible (regression, [2]). gnome-initial-setup is pretty hard to use with just a screen reader. And anaconda doesn't seem to be accessible at all (at least, I don't know how to get orca to read anything in anaconda). So things would probably need to first be in better shape before we can actually start enforcing a blocker criterion to ensure it stays working....
Right, I pretty much agree with Michael.
The way I'd want it to work in the criteria, ideally, is we'd say something like "all desktop requirements must be met for blind users with assistive technology, e.g. screen reading" - i.e. rather than this being a criterion exactly, we'd expect sufficient a11y support to be in place that *all* the desktop criteria would be met for blind users. But as Michael says, it sounds like we haven't really got things in good enough shape yet that we'd be able to enforce such a requirement right now, so that should be fixed first. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ desktop mailing list -- desktop@lists.fedoraproject.org To unsubscribe send an email to desktop-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject.or...
desktop@lists.stg.fedoraproject.org
-
Adam Williamson -
Robert 'Bob' Jensen