On Wed, 2020-09-16 at 19:17 -0500, Michael Catanzaro wrote:
> On Wed, Sep 16, 2020 at 10:55 pm, majid hussain <mhussaincov93(a)gmx.com>
> > 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  and we only
> noticed by coincidence, since it doesn't get tested much.
> Unfortunately right now the login screen is not accessible (regression,
> ). 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.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
Just a quick heads up that the 3.37.92 megaupdate is all lined up and
queued to F33 updates-testing:
This is likely not going to be pushed through the beta freeze, so next
week I'll prepare a final .0 release to replace/obsolete the .92 bodhi
I'll talk to QA and see how they feel about pulling the .92 update
through the beta freeze now that the beta is delayed anyway, but I think
the base scenario is that we ship beta without this.
The megaupdate also includes new parallel installable tracker3 and
tracker3-miners packages. The naming here was difficult but in the end
we ended up keeping tracker 2 in the existing 'tracker' package and
creating a new 'tracker3' package that's parallel installable with the
old one. This makes it easy to port packages over one by one. In F34
perhaps we can drop tracker 2 and get rid of the separate tracker3
package; let's see how fast app porting goes.
In default Fedora Workstation, we'll have both 'tracker' and 'tracker3'
installed by default, but only tracker3 FS miners are going to be
started at session login; tracker 2 miners are autostarted when an app
requires them. Everything in the default install is ported to tracker3,
with the exception of gnome-photos where the upstream port didn't get
ready in time.
(I've cross posted this to devel and desktop lists both.)