Talk Proposal: Fixing Accessibility Issues (Live Coding)

[alexclaes]

Fixing Accessibility Issues (Live Coding)

Abstract

I will bring some examples of flawed implementations. This is a very interactive format. We will discuss the problems and possible solutions in the group. I will fix the code and demonstrate how to test the result.

I did a long version of this at another meetup. I can condense it to fewer examples to fill less time.

https://slides.claes.tech/2024-09-26-dev-design-meetup-accessibility-examples/

Your name (and pronouns)

Alex Claes (he/him)

Contact Details

Github @alexclaes

Mastodon: @alex@claes.social

Code of Conduct

• [x] I've read and agree to the HHTML Code of Conduct

[learosema]

Hello @alexclaes, thank you for your submission :) we would love to accept the talk for our upcoming meetup on November 5 at raumF/Factorial in Hamburg. Can you make it?

Best regards, Lea

[alexclaes]

Hi @learosema, yes sure! I can present on 5th of November at Factorial.

I might squeeze it to fit in 25 minutes, but in the end it is hard to tell. The format is very interactive and packed with questions and discussions. The required time depends largely on the audience. Taking the time for questions and discussions is very valuable for the audience. However, I can easily fill one hour :D

My suggestion: I bring fewer examples. My talk is scheduled to be the last talk of the evening. Everyone is happy when my topic requires around 45 instead of 25 minutes.

How do you feel about that? Is this okay from your perspective? Do you have concerns?

[learosema]

Hello @alexclaes, sorry for the late reply. I think up to 45 minutes should be just fine 👍🏻

[alexclaes]

Hi @learosema , okay - great 👍

[learosema]

Would you be fine with the 3rd slot on November 5? https://github.com/hhtml-de/website/pull/8

[alexclaes]

Yes, of course 👍