►
From YouTube: Grafana UX Feedback Session 2021-09-01
Description
In this session we talked about gauge panel colors and accessibility concerns. We also touched upon our beloved navigation sidebar. If you have feedback, drop us a comment and we'll get back to you!
B
I
also
am
like
running
on
not
a
lot
of
sleep
right
now,
because
someone
decided
to
I
want
someone
who
shall
remain
nameless
decided
to
have
a
party
at
like
4
30
in
the
morning,
so
just
throwing
that
out
there
as
well
my
fifth
16
month
old.
So
anyway,
I
just
I
had
a
question,
and
this
is
really
kind
of
less
kind
of
a
design
workshop
question
then
just
trying
to
get
clarity
around
how
we
address
color
and
accessibility
in
the
dashboards.
B
It's
working
on
a
dashboard
project
or
kind
of
like
helping
the
enterprise
team
with
a
little
bit
of
kind
of
dashboard
design
and
configuration,
and
something
that
came
up
is
kind
of
in
the
accessibility
guidelines
for
ux,
something
that
that
we
we
should
do,
especially
when
we
think
about
kind
of
like
line
line,
graphs
etc,
is
to,
and
we
think
about
kind
of,
like
assigning
value
to
something
kind
of
like
good,
bad
right
like
red,
green
right.
We
think
about
this
like
red,
green.
B
Something
that's
recommended
in
the
accessibility
guidelines
is
to
change
the
green
to
blue,
because
when
you
think
about
color
blindness,
I
think-
and
I
wanna
like
if
I
butcher
this-
please
correct
me,
but
the
most
common
form
of
color
blindness
is
that
people
can't
necessarily
distinguish
between
green,
green
and
red.
That's
that's
a
bit
of
a
challenge
for
people
and
the
recommendation
is
to
change
the
colors
to
blue
and
red.
B
If
we
would
want
to
take
the
same
approach
and
if
the
same
kind
of
challenge
exists,
that
you
wouldn't
necessarily
be
able
to
see
the
difference
between
the
green
and
red,
so
I
know
we
discussed
it
a
little
bit
on
slack,
but
I
just
wanted
to
kind
of
bring
it
up
to
the
team
in
this
forum
and
see
kind
of
if
this
is
something
we
want
to
address
moving
forward.
If
there's
any
kind
of
like
research,
that
needs
to
be
done
and
if
this
is
something
that
we
would
want
to
prioritize.
So
I'll.
D
Yeah
cool,
I
think
it
makes
sense.
I
mean
this
is
just
default.
The
user
can
then
do
change
it
to
whatever
they
prefer
so,
but
these
diff,
the
only
thing
to
consider
is
that
these
defaults
are
for
all
panels,
not
the
gauge
panel.
So
the
new
threshold
system
is
used
by
everything,
but
I'm
I
think
it
could
make
sense
to
change
the
default
to
to
be
blue
instead
of
green
at
the
base
base.
Okay,.
D
Can
just
hit
the
double
t
and
then
refer
just
hit
double
t
on
your
keyboard.
It's
a
shortcut
to
switch
to
live
theme,
and
then
you
have
to
do
a
refresh
or
reload
the
dashboard,
because
the
rendering
doesn't
really
actually
okay,
you're
you're,
an
anonymous
user,
just
open
the
dashboard
again,
but
but
just
navigate
not
really
I'll
load.
It
then
you
should
it
should.
D
D
E
The
question
is,
if
it's
inaccessible
by
accessibility,
standards,
contrast
but
sort
of
on
the
big
topic.
I
would
say
that
this
is
something
we
should
research
and
actually
get
listen
to
actually
people
who
have
these
issues
to
sort
of
figure
out
their
experience
of
it,
because
it's
so
easy
to
sort
of
sit
in
your
in
figma
or
using
one
of
these
accessibility
plugins
and
run
things.
But
you
don't
really
get
the
experience
of
the
user
to
see
what
their
actual
issues
are.
B
Okay,
are
there
any
other
comments
on
this
or
ideas?
I
can
kind
of
take
this
information
and
I'll
circle
back.
I
know
I'm
on
enterprise,
so
I
don't
know
if,
if
we
did
kind
of
want
to
want
to
look
at
this
like
how
we
would
approach
it
as
a
team,
but
I'm
happy
to
really
kind
of
help
in
any
way
that
I
can.
C
E
D
F
F
I
think
the
only
place
I
could
think
of.
Where
are
the
only
kinds
of
places
I
can
think
of
were
just
having
blue
as
like
the
good
default
color,
the
okay
things
are
okay,
a
default
color
would
be
if
it
is
like
completely
context-less.
So,
like
think
about
a
metric
that
says
like
32
and
it's
blue,
but
like
we
don't
provide
anything
and.
B
A
I
think
the
question
here
is
also
kind
of
like
when
and
how
much
time
do
we
want
to
invest
in
this
because
it
shouldn't
be
probably
only
for
gorge
panels
but
general
colors
for
graphs
and
maybe
create
a
different
palette
that
the
user
can
switch
from.
I'm
also
thinking.
I
know
there
is
a
chance
to
still
be
able
to
use
color
traffic
light
colors,
but
as
long
as
we
have
different
hues
or
different
luminosity
in
the
color,
so
it
will
still
be
visible.
A
A
H
H
Okay,
so
I've
been
doing
some
explorations
of
the
hover
focus
and
activated
states
of
the
nav
bar,
and
mostly
that's
because
this
is
the
current
state.
This
is
the
hover
state
for
menu
items,
and
this
is
the
active
state
they
are
kind
of
similar.
They
both
share
this
gradient
border
and
I
was
hoping
to
kind
of
visually
distinguish
between
them
as
much
as
possible.
H
H
This
is
where
I
basically
just
stripped
down
the
border
and
made
it
a
super
simple
version
for
the
hover
estate.
This
is
using
our
hover
overlay
and
nothing
else
changes.
Then
this
one
has
a
bit
more
pronounced
color
then
I
played
around
with
the
shapes
and
the
borders
and
the
fills,
and
I
also
tried
some
of
these
color
versions
using
our
brand
colors
and
our
link
colors,
which
makes
sense
to
me.
The
only
problem
with
these
last
two
is
that
they
are
not
a
hundred
percent
accessible.
H
H
H
H
H
G
It's
it's
a
massive
exploration
fastener.
You
went
through
a
lot
of
options.
I
think
that
that
there
are
a
couple
of
things
that
come
to
my
mind.
First,
so
one
if
something
is
not
fully
accessible,
I
don't
think
we
should
go
for
it
like
those
things
are
not
fully
accessible,
should
be
dropped
as
a
first.
B
G
Other
than
that,
that's
not
gonna
be
very
helpful,
but
dropping
what's
not
accessible
and
having
maybe
it
doesn't.
I
don't
think
it
makes
that
much
of
a
difference
which
other
option
will
choose.
Definitely
those
colorful
ones
like
making
an
icon,
orange
or
blue,
maybe
a
bit
much
given
there.
Next
to
it.
G
There
will
be
a
dashboard
a
lot
of
time,
so
I
would
also
check
how
this
navigation
will
look
with
dashboards
that
are
super
colorful
and
how
that
goes
hand
in
hand
really,
because
here
it
is
in
isolation,
it's
a
great
exploration,
but
it's
also
how
it
will
look
with
more
colorful
edition.
That
dashboard
is
right.
I
A
I
Teddy
yeah
baby,
oh
yeah,
okay,
I
have
a
couple
of
things
so
for
the
hover
state.
I
think
it
would
be
helpful
to
mock
up
some
options
where
there's
like
a
pop
out
menu
that
might
help
inform
which
options
look
best,
especially
with
the
pop
out
menu
in
context,
and
then
in
general.
I
really
like
the
options
where
there
is
like
a
colored
background,
plus
more
of
the
max
contrast,
white
colored
icon.
I
think
other
options
are
a
little
too
subtle.
I
I
think
in
the
product
we
have
cover
states
that
are
too
subtle
today,
so
they're
not
much
different
from
just
like
a
normal
state.
So
I
like
the
contrasted
states
and
then
agree
with
everyone,
obviously
that,
like
if
something's
not
accessible,
we
shouldn't
pursue
it.
That
does
beg
the
question
of
these
orange
and
like
brand
color
icons,
because
we
have
a
couple
of
those
today
in
the
product
for
synthetic
monitoring
and
machine
learning
and
just
like
a
couple
other
apps,
they
have
randomly
have
colored
icons
by
default.
A
A
I
I
like
the
version
with
that
is
similar
to
our
tabs.
It
really
helps
with
the
consistencies
of
having
that
on
active
state
having
a
colored
border
on
the
left
and
having
a
background
when
you
hover,
and
it's
the
one
that
also
has
paddings
around
so
yeah
that
one,
not
the
one,
the
two,
this
one
yeah
that
one
the
only
thing
that
we
need
to
try,
so
active
states
can
also
actually
have
focus
on
them.
So
an
element
can
also
be
active
and
in
focus
at
the
same
time.
A
H
B
I
I
think
it
was
kind
of
going
back
to
the
idea
of
some
of
the
the
icons
like
say,
for
example,
that
we
have
for
machine
learning
or
I'm
thinking
of
of
gem
microphone
enterprise
metrics,
the
colored
icons.
I'm
just
wondering
I.
I
think
it
would
be
useful
to
have
those
within
your
exploration,
because
what
would
happen
there?
What
would
the
the
states
be
like
for
those
icons,
in
particular
our
menu
item,
icons,
those
special
ones?
I
would
just
add
that
in,
but
I
did
just
want
to
say.
B
F
H
C
H
H
J
Yeah
yeah,
sorry,
my
microphone
was
off.
The
problem
with
the
colored
icons
is
that
we
will
never
have
full
control
over
what
lands
on
a
navbar,
because
some
plugin
developers
from
the
community
basically
can
also
pick
a
color
colored
icons.
So
when
we
define
rules
for
the
current
slash
active
state,
however,
we
call
it
and
the
hover
state,
then
we
should
also,
as
a
next
step,
consider
what
happens
if
somebody
puts
basically
a
colorful
icon
there.
J
Maybe
then
we
need
some
additional
background
or
or
something
like
that,
or
something
with
opacity
to
balance
that
out,
but
we
cannot
assume
that
we
can
just
create
guidelines
to
follow
and
they
will
be
followed
because
the
community
might
just
ignore
them,
but
we
should
assure
that
we
can
also
display
the
color
for
colorful
icons.
There.
J
That's
probably
one
thing,
and
the
second
thing
I
I
think
vesna
may
be
a
suggestion
to
use
more
of
a
current
state
explorations
than
active
state,
because
active
state
is
something
yet
different
than
hover
or
current,
and
I
think
it
might
introduce
a
bit
of
a
confusion,
especially
when
discussing
accessibility
things.
So,
like
those
two
remarks,
only.
E
Yeah,
so
I
also
like
the
exploration,
I've
sort
of
explored
this
before
myself.
So
I'm
glad
some
must
pick
this
up
because
it
really
needs
to
be
done.
But
my
only
thought
was
that
it's
good
also
to
look
at
the
light
theme,
because
some
things
here
might
look
good
in
the
dark
theme.
But
then
you,
when
you
switch
to
the
lighting,
it
will
might
almost
break,
especially
with
the
colored
icons,
and
I
do
think
in
that
discussion
with
colored
icons.
It's
such
sort
of
unfortunate
that
we're
using
those
in
some
of
our
own
plugins.