Return to Video

IT Accessibility: What Web Developers Have to Say

  • Not Synced
    The web is about information accessibility
  • Not Synced
    It's really a basic human freedom that we
  • Not Synced
    are just really beginning to talk about in
  • Not Synced
    the last decade. It's important
  • Not Synced
    therefore that everybody have this freedom
  • Not Synced
    any freedom that's only allocated to a few
  • Not Synced
    is not really a freedom.
  • Not Synced
    The web is about information and it's
  • Not Synced
    important that people can access the
  • Not Synced
    information that they need in order to
  • Not Synced
    complete a workflow or get their job done
  • Not Synced
    finish a task.
  • Not Synced
    I think the web should be accessible to
  • Not Synced
    everyone all the time. I grew up with it
  • Not Synced
    being easily accessible to me. It's how
  • Not Synced
    I learnt information easily. I can't
  • Not Synced
    imagine someone not being able to just
  • Not Synced
    google something instantly, and getting
  • Not Synced
    what they need.
  • Not Synced
    I think websites should be accessible
  • Not Synced
    because...the web is founded kinda on this
  • Not Synced
    idea of sharing information and if you
  • Not Synced
    can't share information or if some people
  • Not Synced
    can't see it , then it's not truly being shared.
  • Not Synced
  • Not Synced
    We all have different abilities and
  • Not Synced
    disabilities, and if we're all going to be
  • Not Synced
    able to get the same content and interpret
  • Not Synced
    it in a somewhat similar fashion, it has
  • Not Synced
    to be given to us in that way and
  • Not Synced
    accessible so that we can actually reach
  • Not Synced
    it
  • Not Synced
    Accessibility is important for a number of
  • Not Synced
    reasons. For one, there are laws that
  • Not Synced
    apply.Another is, it can relate to our
  • Not Synced
    reputation. And a third is thatby paying
  • Not Synced
    attention to it, we create a more
  • Not Synced
    inclusive educational environment.
  • Not Synced
    I think we are really good as developers
  • Not Synced
    at being...focusing on the 80% case.
  • Not Synced
    Focusing on how do we make every 4 out of
  • Not Synced
    every 5 of our users happy. How do we
  • Not Synced
    build things for those group of people,
  • Not Synced
    because the last 20% is always hard. But I
  • Not Synced
    say that the web is for 100%. It's for
  • Not Synced
    everybody, which is what Tim Burners-Lee
  • Not Synced
    said.
  • Not Synced
    I'm definitely am very moved by this
  • Not Synced
    notion of inclusiveness. I mean I think
  • Not Synced
    that, for me it's a part of who I...
  • Not Synced
    this is important to me. But there's
  • Not Synced
    also just the sort of, the notion of
  • Not Synced
    of having everybody's contributions to the
  • Not Synced
    sort of...the knowledge.
  • Not Synced
    Big challenge is, to escape your own
  • Not Synced
    viewpoint. And to not make the assumption
  • Not Synced
    that everyone sees the web the way you see
  • Not Synced
    it, on the device you see, the way
  • Not Synced
    you use it. And so when you're creating
  • Not Synced
    web pages, that's the biggest challenge,
  • Not Synced
    is getting outside of where you're sitting.
  • Not Synced
    The biggest obstacle to accessibility,
  • Not Synced
    I think is...is pure knowledge.
  • Not Synced
    It's really about putting yourself in the
  • Not Synced
    mind of a person with disabilities.
  • Not Synced
    A person who has, who has no motor skills
  • Not Synced
    has no hands, has a lack of vision, has a
  • Not Synced
    lack of hearing. May have a
  • Not Synced
    cognitive disability. To be able to put
  • Not Synced
    yourselves in their shoes and understand
  • Not Synced
    how are they working with the thing that
  • Not Synced
    I'm building or designing right now,
  • Not Synced
    can they use it?
  • Not Synced
    The alternative is, you build something
  • Not Synced
    someone says "oh no it's not accessible!"
  • Not Synced
    and so you go back and try to fix it but
  • Not Synced
    you probably have been doing the wrong
  • Not Synced
    thing at many places you know you may
  • Not Synced
    have hundreds of images with no alt text,
  • Not Synced
    you may have navigation that's very confused
  • Not Synced
    or you are relying on libraries that...
  • Not Synced
    open internet explorer
  • Not Synced
    it's just that the technologies aren't
  • Not Synced
    going to figure out. And so that's
  • Not Synced
    when someone says, it's too much, too
  • Not Synced
    expensive, too much work. Well just do it
  • Not Synced
    from the beginning and it'll...it'll probably
  • Not Synced
    get a quality product with less work.
  • Not Synced
    Accessibility is important to incorporate
  • Not Synced
    earlier on because if you don't
  • Not Synced
    incorporate it early on, you will
  • Not Synced
    incorporate it later at greater expense,
  • Not Synced
    with a certain amount of time you don't
  • Not Synced
    have, with a certain amount of money you
  • Not Synced
    don't have, to try to make it better.
  • Not Synced
    Accessibility, unfortunately like
  • Not Synced
    everything else in design and web design
  • Not Synced
    has to be done from the very beginning.
  • Not Synced
    So whether you're designing for different
  • Not Synced
    devices, whether doing for different kinds
  • Not Synced
    of human abilities, all those things have
  • Not Synced
    to be thought of from the very beginning
  • Not Synced
    and built into your concept of what your
  • Not Synced
    your plan is. Of course nobody wants to
  • Not Synced
    take time at the end. We're almost there,
  • Not Synced
    we just want to get it out, and that's the
  • Not Synced
    mistake many of us make. It's like
  • Not Synced
    "I'll just get it out, then I'll go back and fix it."
  • Not Synced
    No. Doesn't ever happen. There's always
  • Not Synced
    a next project.
  • Not Synced
    The first step in getting an accessible
  • Not Synced
    site, is to work with the management, so
  • Not Synced
    they understand the value of making it
  • Not Synced
    accessible, and also helping them
  • Not Synced
    understand that we can do pretty
  • Not Synced
    much anything they want and be accesible.
  • Not Synced
    If you just talk about accessibility, it
  • Not Synced
    may not be immediately appreciated as
  • Not Synced
    something important to do. But if you
  • Not Synced
    start talking about quality and the
  • Not Synced
    overlap of search engine optimisation and
  • Not Synced
    accessibility and things of that nature
  • Not Synced
    that...that will tend to get people's
  • Not Synced
    attention more.
  • Not Synced
    When I started, I was a designer and I
  • Not Synced
    wanted to make things pretty. And you
  • Not Synced
    don't think about anything besides the
  • Not Synced
    aesthetics. And what I soon realised was
  • Not Synced
    that when you have something that works
Title:
IT Accessibility: What Web Developers Have to Say
Description:

more » « less
Video Language:
English
Team:
DO-IT
Duration:
10:44

English subtitles

Revisions Compare revisions