Accessify your Blazor apps - Hot accessibility techniques for Blazor apps

preview_player
Показать описание
Avoid the DIV button!

|| Subscribe for more content from SSW TV ||

|| Press like and leave a comment below to let us know how we're doing ||

00:00 - Quick Intro
1:52 - A Brief Recap On Accessibility
4:23 - Frankenstein's Monster, The DIV Button.
10:02 - The Difficulty With 3rd Party Control Suites
14:15 - Using WCAG 2.1 Alert Roles
18:19 - Managing Accessibility In Large Teams
22:24 - Manage Screen Focus Using Javascript Interop

Twitter ↴

Facebook ↴

------------------------------------------------------------------------------

Accessibility can be a jungle to navigate for regular websites and it becomes impenetrable for complex web applications. It doesn't need to be this way. Ross will show three core techniques that move beyond the basics to really address how to start strong and begin to make your Blazor apps accessible.

Ross will explain why you should avoid the DIV button, the 'Frankenstein's monster' of non-semantic HTML which makes things that much difficult for a screen reader user. How to manage on-screen focus using Javascript Interop and show how accessibility can be maintained in large development teams by creating reusable components.

About the speaker:

Ross Mullen is Director of CANAXESS a web and digital accessibility company. He works with a range of organizations from charities and start-ups to governments making their digital services and platforms inclusive and accessible using best practice web accessibility techniques.

Transcript available on GitHub:

------------------------------------------------------------------------------

Created by SSW TV | Videos By Developers, For Developers

Рекомендации по теме
Комментарии
Автор

Thanks for having me, I really enjoyed it! These are the timestamps for each section:

1:52 A brief recap on accessibility, and the legal cases involving the websites of Beyonce, Dominos and Coles Australia
4:23 Frankenstein's monster, the DIV button. Going it alone and building your own control means adding back accessibility support which exists natively when using default HTML elements
10:02 The difficulty with 3rd party control suites. Vendor accessibility statements are so narrowly defined the controls provide extremely limited to non-existent accessibility support
14:15 Alerting the user audibly and building an AudibleAlert Blazor component using WCAG 2.1 alert roles
18:19 Managing accessibility in large teams using reusable components to ensure consistency
22:24 Manage screen focus using Javascript Interop ensuring screen focus is always in synch and following changes in displayed content

MrRossmullen