►
From YouTube: CHAOSS.D&I.April.29.2020
Description
CHAOSS.D&I.April.29.2020
A
A
A
A
E
A
B
E
D
E
They
got
the
platform
up
and
running,
I
mean
I.
Think
our
most
major
complaints
are
the
inability
to
link
from
one
section
of
the
system
to
another
to
be
able
to
have
links
to
pass
out
to
people,
but
you
know
we're
learning.
You
know
the
platforms,
didn't
you
know
what
we
needed
it
to
do
and
they
didn't
move
the
date
simply
switched.
So
they
had
very
short
time
to
find
a
platform
in
doing
everything
in
our
events,
team
has
done
a
really
great
job.
A
E
A
B
A
E
E
A
E
Didn't
get
very
far
because
I
started
on
a
tangent
that
the
description
for
documentation
utility
made
a
lot
of
sense,
but
the
wording
using
utility
as
a
word,
didn't
really
work.
So
we
changed
it
to
documentation,
discoverability
and
realistically,
that's
as
far
as
we
got
because
I
squirreled
on
us
all.
E
E
A
So,
okay,
documentation,
discoverability,
is
critical
due
to
the
role
it
plays
in
open
source
projects.
You're
their
self
documentation
have
different
ways
of
accessing
documentation
requiring
it
to
be
offered
in
different
formats
to
be
equally
empowering
for
these
different
users:
documentation,
utility
country,
ok,.
A
You
I
think
this
is
where
we
still
need
to
okay
yeah,
just
a
change
of
word.
Yeah
documentation.
Discoverability,
contains
issues
of
technical
accessibility
with
the
goal
to
ensure
reach
ability,
editability,
search
ability
and
overall
access
to
avoid
audience
of
contributors
to
the
project,
and
then
hasta
has
a
comment
here.
This
can
be
reverted.
I
don't
have
a
particular
suggestion.
A
A
A
A
E
E
C
F
E
F
A
D
Because
this
area
really
relates
more
to
HCI
the
Yuma
computer
interaction
and
the
way
they
can
interpret.
This
can
really
differ,
based
on
different
perspective,
like
vision
in
visual
impaired
people
with
different
kind
of
colorblindness,
and
things
like
that,
so
user
friendly
sometimes
can
really
become
too
general,
too
abstract
to
understand.
From
this
perspective,
it's
a
good
word
I'm,
not
saying
it's
bad
measures
that
we
should
keep
in
mind
that
it's
a
little
bit
because
at
this
level,
because
you.
E
E
F
This
actually
reminds
me
of
the
problem
with
UX
mindset
is
that
we
always
talk
about
this
user.
That
user
is
generally,
you
know,
I
put
myself
in
the
users
true,
if
I
was
a
user
very,
very
vastly
different
from
what
a
real
user
is.
Actually,
there
is
no
such
user,
but
we
look
at
it
as
there's
one
user
and
and
I
think
I.
Think
the
the
point
of
wanting
to
to
articulate
here
is
that
you
know.
F
E
That
makes
sense,
I
know
at
Oh
a
tea.
We
had
the
ability
for
the
students
to
change
the
color
contrast
to
what
worked
for
them,
but
let's
be
real
in
github
or
somewhere
you're.
Not
gonna.
Have
that
ability
you
might
have
that
ability
once
this
is
on.
You
know
someone's
website
they
might
have
the
ability
to
change
colors.
You
know
with
a
drop-down
or
something,
but
are
we
talking
about
in
github?
Are
we
talking
about
in
the
next
level
up
where
it's
their
website
and.
F
So
so
colors
on
the
web,
it
funny
enough.
There's
a
w3c
or
they're
part
of
the
CSS
spec
is
that
you
can
overload
it
with
user
style
sheets,
but
you
know
funny
enough:
2018,
Google,
Chrome
dropped
support
for
user
style
sheets
and
they
say
small
percentage
of
the
users
go
get
a
plug-in.
So
so
you
know
I
think
I.
F
Think
the
the
whole
point
is
that
if
documentation
is
being
authored
on
github
that
you
know,
inclusion
of
people
of
difference
is
that
they
would
be
able
to
use
it
on
github.
They
wouldn't
need.
They
wouldn't
need
a
oh
here's.
The
special
room
for
you
to
you
know
feel
comfortable.
You
know
this
is
not
inclusion.
This
really
again
it's
going
to
be
exclusion.
F
E
F
Think
I
think
the
way
is
to
say
if
open-source
lives
on
github,
then
open-source
should
make
the
case
that
github
needs
to
afford
them
the
tools
to
be
inclusive
because
or
or
choose
not
to
be
on
github
but
I
mean
let's
be
realistic.
Most
people
would
rather
be
on
github
and
hope
that
the
problem
gets
solved
one
day,
but
that
doesn't
solve
the
problem
right.
So.
F
They
actually
say
on
an
accessibility
declaration
to
the
government
on
github
com.
They
are
accessible
contact
us
if
you
want
us
to
help
you
if
you're
struggling
with
accessibility
and
I
tried.
Obviously
so
so
they
have
all
these
like
pro-forma
things,
to
make
sure
that
if
I
tell
a
friend
github
is
not
accessible,
they
would
Google
quickly.
They
would
find
that
page
and
they
were
like
oh
look
and
I'm
like
yeah.
Well
that
works
with
the
government.
Obviously,
who
doesn't.
F
E
F
Features
are
being
dropped
because
people
say
it's
open
source
and
you
don't
time
to
develop
important
and
I
mean
yeah
sure
we
can
do
this
popularity
game.
Thank
God.
Most
people
are
not
disabled.
You
know
we
should
be
happy
with
that,
but
we
shouldn't
say
you
know.
Well
then,
it's
not
popular
because
yeah,
that's
not
inclusion,
that's
actually
the
opposite.
Yeah.
E
F
E
E
And
that's
basically,
we
thought
it
was
a
great
idea
to
write
an
updated
article
and
no
it's
depressing
and
don't
do
it.
Okay,
so
back
to
this,
so
we
have
do.
We
have
tools
to
access
for
visually
impaired.
Is
there
a
tool
that
will
do
that?
I
mean
it's
one
thing
to
see
if
the
screen
reader
can
read
it,
but
is
there
a
tool
available
that
can
do
what
we're
hoping
I
can
do
here.
F
Markdown
is
not
tagged
for
accessibility,
that's
how
it's
designed
it's
designed
to
actually
be
sense,
attributes
and
spin.
So
what
we're
doing
a
node
is
we're
considering
of
how
we
can
use
semantic
semantic
templates
of
structure
to
to
try
to
render
the
markdown
as
well
define
Dom
nodes
that
have
Aria
nodes.
So
you
know
when
two
headings
are
on
the
same
level:
they
define
sections
and
some
articles,
and
so
forth,
I
mean
markdown
and
its
current
specs
does
not
have
a
one-to-one
translation
to
screen
readers.
F
A
E
A
C
E
F
So
so
I
guess
there's
a
concern
here
of
relativity
and,
and
you
know,
clarity
out
that
or
the
you
know,
stipulations
in
definition,
because
when
you
say
visually
impaired
I
mean
it's
politically
correct.
That's
fine,
but
you
know
we're
kind
of
like
omitting
whether
you
know
the
form
of
difficulty
or
difference
of
their
vision.
Compared
to
you
know
the
majority
in
you
know
who
would
be
considered,
not
visually
impaired.
F
We're
basically
people
say
well,
we
have
people
who
have
like
visual
difficulties,
but
they
don't
consider
well
someone
who
is
completely.
You
know
unable
to
see
as
falling
in
that
stipulative
terminology
right
like
like
how
would
they
be
on
github,
or
you
know,
like
some
questions
like
that
I
get
asked
sometimes,
like
you
know,
I
understand
if
you
have
difficulty
and
you
have
to
use
contrast
or
whatever
and
I'm
like
yeah.
No,
no,
like
that's
not
what
this
is
meant.
It's
not
meant
that
you
could
relatively
consider
someone
able
and
visually
impaired
and
the
other.
F
C
C
A
F
I
think
III
didn't
mean
it
that,
like
an
absolute
I,
just
meant
it
that
if
two
people,
if
two
were
projects,
were
to
give
results
that
are
very
comparable
to
the
data
collection
here
and
in
terms
of
data
collection
to
those
questions,
and
then
we
asked
okay.
So
what
what
does
visually
impaired
the
mean
in
project
a
versus
B
and
we're
shocked
to
find
that
in
project
a
we're
just
talking
about,
like
you
know,
difficulty
where
envy
we
are
talking
about?
F
No,
no,
we
are
including
people
who
are,
you
know
completely
unable
to
rely
on
vision
and
and
so
so
to
compare
both
data.
You
know
if
both
data
are
comparable
and
the
that
the
you
know
the
way
the
data
relates
in
real
life
is
very,
very
different
between
the
two
projects,
then
the
results
we're
collecting
here
are
misleading.
E
E
E
Maybe
that
would
be
a
nice
bridge
between
the
two
points
but
yeah,
because
you
know
you,
you
get
different
data
I
mean
even
when
one
group
uses
one
list
to
determine
gender
and
another
group
uses
another
list
to
determine
gender.
It's
very
hard
to
compare
the
two
so
I
understand
where
you're
going
sigh.
F
F
E
Spend
all
our
time
changing
the
word
utility
to
discoverability
like
I,
am
NOT
gonna,
say
a
word
and,
as
they
pointed
out
to
me,
these
are
important
conversations
and
they
do
end
up
values.
So
we're
not
wasting
time
necessarily,
it
gives
us
a
talking
point
for
later
and
you
know
maybe
you
log
off
this
call
and
two
minutes
later
you
find
the
word
you
wanted.
There.
C
And
I
think
something
I've
heard
from
that.
Probably
a
million
times
at
this
point,
I'm
gonna
just
say
for
him-
is
that
we
with
the
metrics
that
we
create.
We
try
our
best
not
to
make
determinations
on
things
like
I,
wouldn't
call
it
a
value
judgment
believe
steering
away
from
fighters
in
the
past,
also
telling
people
on
just
how
to
measure
things
in
their
own
perspective.
This
is
a
big
part
of
it.
I
don't
know
you
could
know.
E
F
This
may
be
very
inappropriate,
but
if
we,
if
we
said
okay
yeah
after
you
give
us
those
you
know
after
you
collect
the
data,
can
you
also
give
us
some
sort
of
a
statistical
breakdown
of
you
know
the
differences
in
your
near
project,
like
like
kind
of
a
survey
approach
like
we
try
to
do
in
nodejs
a
survey
this
year
just
to
qualify?
You
know
when
you
say
you
address
this:
how
how
big
of
a
percentage
in
your
project
is
benefiting
from
this?
A
That's
a
valid
question
to
ask,
especially
as
we
are
asking
later:
how
do
you
actually
use
this
metric?
How
do
you
operationalize
it?
How
do
you
measure
it?
What
strategy
works,
what
doesn't
work?
What
tweaks
did
you
have
to
make
and
then
we
can
get
take
that
feedback
to
improve
our
metric
definition
later
yeah.
E
F
A
I
think
the
big
challenge
we
will
be
facing
is
to
take
these
conversations
outwards
so,
just
like,
we
have
different
understandings
and
use
different
terminology
to
describe
sometimes
the
same
thing.
I
think
there
will
be
a
challenge
ahead
of
us
to
explain
what
we
mean
to
others
who
are
not
part
of
these
conversations
but
I'm
thinking
ahead.
This
is
that's,
let's
focus
on
writing
down
what
we
mean
and
then
we
can
cross
the
bridge
of
how
we
communicate
that
out
later.
I
think.
B
B
B
F
D
A
D
F
E
B
F
Think
I'm,
sorry,
good
yeah
I
was
gonna,
say
that
you
know
it
came
up
and
and
and
I
think
we
just
want
to
think
about
it
or
you
know
falling
over
or
whatever
the
word
is.
It
likely
is
already
effects
in
our
thoughts
here.
So
just.