Afrikaans
Akan
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranรฎ)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
Hi, I'm shabby.
I'm an interaction designer at Google.
I designed digital experiences for people just like you, by understanding
your needs and people with disabilities.
Because I work in design systems, I work at the component level.
So I really have to understand how people with disabilities interact with buttons
and other features within your interface.
And in order to do that, you really have to understand the assistive technologies
that they're using and actually engage with people who have disabilities.
Assistive technology really helps augment one's ability by creating.
In interaction between your interface and then the technology that they're using.
So to ground this a bit, there's something called a screen reader, which typically
helps someone who has limited vision.
And what it will do is read aloud the content on the screen.
And this could be also reading aloud, the different types of interactive.
When someone is using a screen reader, they might hear cancel button and
that'll help them understand the purpose or role of that interactive element.
The advice I'd give someone who's interested in designing for accessibility.
To reach out to your local communities.
There are tons of independent living facilities.
You have friends and family who may or may not have a disability.
And it's really about getting the conversation going in, showing that
you care by putting yourself out there.
And that's exactly what I did when I was still learning and trying to create my
own projects for people with disability.
I think some of the frustrations that I experienced when designing for
accessibility, especially when this is a collaborative effort is oftentimes
accessibility is a patchwork solution.
You might think of it at the end because your product needs to launch.
And therefore you want to meet certain guidelines that are expected.
However, it shouldn't be that way.
You should be considering people with disabilities upfront because oftentimes
when you design with them first, you extend that solution to a lot more people.
Accessibility is important because it creates an equitable experience for
one who would normally not have one.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.