Conversation

Notices

1. Embed this notice
   Emma (emmadawsondev@a11y.info)'s status on Thursday, 07-Nov-2024 04:52:43 JST Emma

   How do you make accessibility annotations at all useful without designers and developers needing in depth knowledge of html and aria?

   • Embed this notice
     Evil Jim O’Donnell (eatyourgreens@mastodon.social)'s status on Thursday, 07-Nov-2024 04:52:33 JST Evil Jim O’Donnell

     in reply to

     • Sara Joy :happy_pepper:
     • Steve Faulkner

     @sarajw @emmaDawsonDev Doug Abrams wrote about this recently. There’s a generation of developers that know components, not HTML elements.

     I think the link is originally via the mighty @SteveFaulkner

     https://www.tpgi.com/mind-the-remediation-gap/

   • Embed this notice
     Sara Joy :happy_pepper: (sarajw@front-end.social)'s status on Thursday, 07-Nov-2024 04:52:34 JST Sara Joy :happy_pepper:

     in reply to

     @emmaDawsonDev I would be very annoyed by that!

     alcinnz repeated this.
   • Embed this notice
     Emma (emmadawsondev@a11y.info)'s status on Thursday, 07-Nov-2024 04:52:40 JST Emma

     in reply to

     • Sara Joy :happy_pepper:

     @sarajw hmm, it’s a very hard thing to balance. I understand things can’t be too technical but a certain level of technicality is needed or the annotations are just meaningless. I may also just be annoyed being told that my feedback was too technical when I said a radio group needs a label

   • Embed this notice
     Sara Joy :happy_pepper: (sarajw@front-end.social)'s status on Thursday, 07-Nov-2024 04:52:41 JST Sara Joy :happy_pepper:

     in reply to

     @emmaDawsonDev good question. Arguably developers should be able to go change html and aria attributes without it being a large problem.

     Lots of links to explainers? MDN? 😬