SaraSoueidan,
@SaraSoueidan@front-end.social avatar

I haven't blogged regularly in a long while (in about 2 years, actually, since the course).

I'm now slowly getting into the flow of things, and I have a lot of ideas for topics to write about. Too many.

So I'm wondering: what kind of topics do you wish I'd write more about?

tomayac,
@tomayac@toot.cafe avatar

@SaraSoueidan I would love to read and learn from you about making rich web apps accessible. How and when to use live regions, how to announce new state in SPAs, etc. I reckon this is a super complex topic and probably part of your course. But since you were asking for ideas…

SaraSoueidan,
@SaraSoueidan@front-end.social avatar

@tomayac I think these two course chapters that I recently published on my blog might answer a lot of those questions:

https://www.sarasoueidan.com/blog/accessible-notifications-with-aria-live-regions-part-1/

https://www.sarasoueidan.com/blog/accessible-notifications-with-aria-live-regions-part-2/

I have a draft to elaborate on one of the examples in the chapters with a working demo, and I guess I could elaborate more on other more specific ones. The course also contains chapters on form validation that also tackle dynamic message announcements using focus management.

tomayac,
@tomayac@toot.cafe avatar

@SaraSoueidan Thanks a lot for the reply, and pardon for the long silence; I wanted to make sure I fully understand the two linked posts.

So I guess what I propose you could write about would be changes of content as defined in https://www.sarasoueidan.com/blog/accessible-notifications-with-aria-live-regions-part-1/#status-messages-in-wcag. The linked posts talk about things that are not changes of content.

Examples of things that are changes of content are (IIUC) games like https://flip.withgoogle.com/ or single-page app blogs like https://philipwalton.com/. These aren't live regions!?

sarajw,
@sarajw@front-end.social avatar

@SaraSoueidan I'm struggling to answer this with any specific topics, because if you already have ideas I'd love to hear them!

Maybe we need a poll 😅

SaraSoueidan,
@SaraSoueidan@front-end.social avatar

@sarajw I have CSS, HTML, a11y topics, and a wide range of each category 😅

sarajw,
@sarajw@front-end.social avatar

@SaraSoueidan Oooh I have had one idea - the situations where HTML alone isn't accessible?

SaraSoueidan,
@SaraSoueidan@front-end.social avatar

@sarajw Hmm I have one for when HTML alone is accessible; could you elaborate more? You mean components that require additional JS to become accessible?

sarajw,
@sarajw@front-end.social avatar

@SaraSoueidan yes, those! I mean, most HTML is grand the way it is, and shouldn't functionally be disturbed too much - but I know there are exceptions where a bit of JS makes them more accessible, yes. I always forget which they are!

alvaromontoro,
@alvaromontoro@front-end.social avatar

@sarajw @SaraSoueidan the most recent <dialog> element won't work accessibly unless you use JS. And it's "new".

SaraSoueidan,
@SaraSoueidan@front-end.social avatar

@sarajw noted! These are actually some of my favoritw topics to write about, so I appreciate the vote ☺️

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • tacticalgear
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • khanakhh
  • Youngstown
  • ngwrru68w68
  • slotface
  • everett
  • rosin
  • thenastyranch
  • kavyap
  • GTA5RPClips
  • cisconetworking
  • JUstTest
  • normalnudes
  • osvaldo12
  • ethstaker
  • mdbf
  • modclub
  • Durango
  • tester
  • provamag3
  • cubers
  • Leos
  • anitta
  • megavids
  • lostlight
  • All magazines