Web Content Accessibility Guidelines (WCAG 2.1) Crash Course

Подписаться 1,2 тыс.

Просмотров 15 тыс.

50% 1

WCAG explained in plain language.
This is a replay of a live stream on web accessibility. Watch if you'd like to go through all the sections of the Web Content Accessibility Guidelines!
This is a casual stream, with examples of what to look for when assessing web pages for accessibility defects.
Perfect for web developers and UX/UI designers who would like to learn more about what to consider when making their web applications inclusive and usable for those with disabilities.
#a11y #accessibility #webaccessibility #wcag1 #manualtesting #automatedtesting #wcag #webdevelopment #frontend #fullstack #softwareengineer #softwaredeveloper

Наука

Опубликовано:

16 апр 2023

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 32

@silvadacunha692 6 месяцев назад

This was so much fun! Thank you, I learned a lot :)

@toms4 8 месяцев назад

Amazing, super helpful :) thank you!!

@user-oi8ut4ln8r Год назад

Thank you sooooo much for this! I will definitely share on LinkedIn 💖

@kinoslay Год назад

Im 15 mins in! Very informative so far.

@moonsun3658 Год назад

thank you very much for sharing your knowledge about Accessibility

@ct11002000 Год назад

Thank you so much!

@narisap.1038 6 месяцев назад

Thank you so much for your videos

@911sareforever 5 месяцев назад

Thank you so much, loved it you made this boring topic fun

@temiloluwajikiemi1733 Год назад

looking forward to future videos

@afrohopradio 2 месяца назад

Thank you so much for this!!!

@nkanmuoverachioma8078 7 месяцев назад

This is so concise and clear, thank you so much.

@africakenyah 7 месяцев назад

Glad it was helpful!

@tema_skakun 2 месяца назад

thank you, great job, very accessible and to the point) I'm doing a test assignment for an accessibility improvement project in my humble opinion, the section of answers to questions should be placed at the end of the video

@QuantumLegal 5 месяцев назад

Very informative and helpful. As much as experts stress the need for a mix o automated and manual testing, this is often unhelpful counsel when you have over 5,000 pages (and zero budget for "consultants"). I have yet to solve that vexing equation.

@africakenyah 3 месяца назад

Sounds tough. I'm sure all 5000 pages aren't unique and there is a way to audit the site to capture a large amount of the issuesthat you'd find on each page. I guess the reality is if you have 5000 pages and care about accessibility you have to pay more for someone to look at it. If these 5000 are a profitable business you may have a budget for a consult to see how you can improve it.

@JennieReads 6 месяцев назад

This course was amazing. I used the knowledge I gained from this training video to secure my dream role! Thank you so much for posting this, I’m forever grateful ❤

@africakenyah 6 месяцев назад

Wow that’s amazing congrats on the new role!

@KL-ii6dt 4 месяца назад

Love this very helpful video. I am confused though, you list critical, high, medium, and low level rules but you only indicate the critical ones....

@miket5980 5 месяцев назад

thanks for the great video! a couple questions: any change you're going to make another video on WCAG 2.2 (or a supplementary video to go with this one that has the updated information)? also, can you share more information on the color contrast tool you use? I'm unable to find it. thank you!

@africakenyah 3 месяца назад

Yes I will be doing an updated one in the next few months

@torireed5051 7 месяцев назад

Thank you for this content! Out of curiosity, what prompted you to make the switch from Occupational Therapist to Developer?

@africakenyah 7 месяцев назад

I talk about it in detail here ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-IwyyKlABpTE.htmlsi=aVr8wdOLHx-sF1KU

@nh-vb8ij 3 месяца назад

For Keyboard Trap, is it true you WANT to have a keyboard trap for some modal dialogs, so the user is caught in the modal before closing it, same with a non AT user?

@africakenyah 3 месяца назад

You never want a keyboard trap, the user needs a way to escape the modal by hitting escape or another button like "ok/ accept" that closes it. The focus should stay in the modal until one of those actions take place which wouldn't make it a keyboard trap.