- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Tue, 22 Jun 2021 08:06:29 -0500
- To: "Patrick H. Lauke" <redux@splintered.co.uk>
- Cc: w3c-wai-gl@w3.org
Hi Patrick, For those situations, Steve Faulkner had a solution in his "HTML5: Techniques for providing useful text alternatives" document for when a text alternative is not available at the time of publication. http://web.archive.org/web/20200420131928/https://www.w3.org/TR/2014/WD-html-alt-techniques-20141023/#when-a-text-alternative-is-not-available-at-the-time-of-publication-1 Kind Regards, Laura On 6/22/21, Patrick H. Lauke <redux@splintered.co.uk> wrote: > On 22/06/2021 13:20, Laura Carlson wrote: >> IMHO it comes down to training users to enter appropriate text >> alternatives. We have been doing that with content management software >> (e.g. Drupal) and learning management software (e.g. Canvas). Our >> instances have required alt fields. It helps educate users and >> provides a teachable moment that helps make accessibility practices >> more ubiquitous. > > This is a different proposition to user-generated content, where your > users aren't internal users in the organisation that need to use your > CMS, but rather...the general public. Think Flickr, Instagram, TikTok, > etc. Unless you're suggesting those sites should train all their > general public users before allowing them to post something... > > P > -- > Patrick H. Lauke > > https://www.splintered.co.uk/ | https://github.com/patrickhlauke > https://flickr.com/photos/redux/ | https://www.deviantart.com/redux > twitter: @patrick_h_lauke | skype: patrick_h_lauke > > -- Laura L. Carlson
Received on Tuesday, 22 June 2021 13:08:10 UTC