►
From YouTube: Jenkins UX SIG Meeting 7 Dec 2022
Description
Jenkins UX SIG meeting 7 Dec 2022
00:50 - Security review status
02:25 - User feature flags status
03:19 - Web components in Jenkins user experience
04:12 - YahooUI removal from Jenkins core
05:35 - UX improvements
06:00 - Reporting accessibility issues
A
A
A
B
A
A
A
The
next
Point
are
web
components
and
Jenkins
your
ex
from
to
Austin,
but
he
isn't
here
today,
so
yeah
I,
don't
think
we
can
add
a
lot
to
that.
He
submitted
a
PR
to
Jenkins,
but
the
happened.
They
didn't
have
much
a
lot
with
the
pr.
Currently
the
build
is
failing
and
there
is
no
there's
no
proof
of
concept
or
something
that
we
could
take
a
look
at
right
now,
just
on
the
pr
itself.
He
basically
added
everything
he
was
talking
about
in
last
meeting,
but
that's
basically,
it
I
think.
A
Yeah,
adding
to
the
who
you
are
removal,
I,
think
that
was
this
week's
release,
yesterday's
release,
where
we
fixed
at
least
the
unfixed
civil
regression
from
the
initial
PR
that
caused
load
that
cost
regression
with
loading
Pages
taking
at
least
10
or
more
seconds
caused
by
the
tpj
spr
outs.
This
has
been
fixed
by
now,
so
we
can
move
on
from
there
on
Jack's
improvements
by
Jan
and
Tim.
B
C
Basically,
this
kind
of
a
quick
addition
around
accessibility,
I,
don't
know
if
the
ux
special
interest
group
is
the
appropriate
place
for
that
or
if
you
have
a
separate
accessibility,
sorrentia
I'm
I,
don't
remember
which
client
provided
it,
but
we
had
a
list
of
of
accessibility
issues
for
wcagaa
compliance
and
she
wasn't
sure
the
status
I
went
through
and
she
directed
me
to
use
kind
of
the
ci.jenkins.io
since
that
was
presumably
I.
Think
the
Baseline
for
for
what's
recent.
C
Outlook
wasn't
great:
there
were
a
lot
of
issues.
How
what's
the
best
way
to
kind
of
get
that
those
issues
back
into
the
community,
or
is
there
a
effort
on
going
kind
of
the
major
ones,
the
ones
that
I
see
is
kind
of
the
most
the
biggest
roadblocks?
To
someone
who
would
be
trying
to
navigate
with
accessibility
issues?
Is
you
know
the
new
the
new
breadcrumb
menu?
C
So
if
you
were
to
navigate
me
toward
keyboard
down
into
select
one
of
those,
you
know
you
know
what
you
want
to
call
them
the
menus
within
each
breadcrumb
layer.
If
you
navigate
down
a
keyboard
through
them.
My
keyboard
to
the
last
input,
where
I
would
typically
expect
that
you
know
I
keep
tabbing,
it
would
close
that
menu
and
bring
me
up
to
the
next
item
in
the
tab
order
the
breadcrumb
bar.
C
C
I
think
into
on
there's
always
this
impulse
to
just
use
kind
of
the
browser,
extensions
or
automated
tools
for
the
accessibility
checks,
and
they
don't
find
a
lot
of
the
major
navigational
issues.
You
know
they're
good
for
identifying,
like
that.
All
of
your
alt
tags
are
there
that
the
color
contrast
is
okay,
but
they
kind
of
those
tools
fall
apart
when
it
comes
to
auditing,
like
the
keyboard
navigation,
which
is
kind
of
one
of
the
more
important
pieces
of
of
a
site
being
accessible
that
someone
can
navigate
through
it.
B
It
really
needs
someone
to
just
review
and
raise
labeled
appropriately,
maybe
even
adding
it
to
the
ux
dashboard
in
the
so
there's
the
well,
maybe
a
new
dashboard
for
it
that
shows
them.
The
ones
I've
got
favorite
City,
ux,
regressions
and
ux
newbie
friendly,
which
some
of
these
might
show
up
on
there,
but
I'm
just
saying:
maybe
is
there
excess
I,
don't
know
from
Jerry
Bailey
loads?
For
me,
so
I
can't
I
can't
really
contribute
much
and
anything
to
do
with
Jerry,
which
has
not
been
helping
for
me.
B
B
Yeah
I'm
in
a
dashboards,
probably
I
mean
there's.
Probably
people
don't
have
a
ux
overall
dashboard.
This
is
just
a
like
a
kind
of
that's
a
bug,
dashboard,
which
I
mean
the
accessibility
might
fit
into,
but
I
probably
want
to
label
it
separately
as
well.
Okay,
so
I've
sent
a
link
and
a
couple
links
in
the
chat,
so
the
first
one.
B
B
C
B
B
C
A
C
B
B
B
C
Yeah
I
mean
this
is
the
core
of
what
I
would
probably
yeah.
No
I
agree
that
these
are
poor.
I
would
probably
add
it
with
kind
of
some.
It
also
add
some
there's
not
how
to
word
it
nicely.
There's
not
always
a
great
understanding
about
what
exactly
this
the
requirements
are
for
each
level
of
accessibility,
compliance,
so
I
think
it
would
probably
be
helpful
if,
in
the
bug
report,
I
include
some
kind
of
where
it's
happening
and
what
it
would
look
like
examples
of
what
it
would
look
like
resolved.
C
C
C
C
C
Similarly,
when
you
first
start
tapping
age,
keep
them
from
having
to
go
through
that
whole
top
area
do
like
a
skip
to
navigate,
skip
to
content
area
cue,
but
I'll
make
some
tickets
and
just
include
some
examples
that
may
be
helpful
and
then
I
assume
people
can
post
questions
and
comments
in
in
the
thread.
Do
they
do
they
tag
the
original
bug
poster.
B
A
C
Navigate
fixing
the
keyboard
navigation,
like
all
of
the
like,
there's
a
hierarchy
of
what's
most
important
as
far
as
accessibility
goes
and
and
the
nav
keyboard
navigation
part
is
one
of
the
biggest
like
alt
tags
on
spacers
things
like
that.
Those
are
nice
to
halves.
But
if
you
don't
have
the
kind
of
the
underpinnings
of
the
navigation
resolved,
then
it's
kind
of.
C
A
B
C
B
A
Yeah
support
should
probably
go
through
all
these
old
issues
and
probably
close
them
all
if
they're
no
longer
actually
affect
anything
given
so
much
change
from
basically
2020
to
now
yeah,
so
I
don't
think
that
these
epics
or
these
issues
are
much
of
use
anymore
unless
they
actually
refer
to
them
refer
to
something
that
is
still
in
use.
Well,.