axbom’s avataraxbom’s Twitter Archive—№ 26,274

                1. What would be a good way to make one-panel sketches/cartoons with dialogue accessible to users of screen readers? To be used on a website. Have you seen good examples of this? Attached images of the types of cartoons I'm talking about. #a11y #accessibility
                  oh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their API
                  Permalink On twitter.com Twitter logo axbom’s avatar ♻️ 2 Retweets ❤️ 5 Favorites 2018 Sep 25 Mood +7 🙂
              1. …in reply to @axbom
                I wanted to go with the longdesc attribute for my cartoons. I was at first worried I would have to create one html document per cartoon but the longdesc attribute accepts anchor links which means all the descriptions can go into one document. 👍 #a11y
                Permalink On twitter.com Twitter logo axbom’s avatar 2018 Sep 26 Mood 0
            1. …in reply to @axbom
              But realizing now that longdesc is not supported by all screen readers and I've come to understand that Apple is against it for reasons outlined here... lists.w3.org/Archives/Public/public-html-admin/2014Aug/0028.html #a11y
              Permalink On twitter.com Twitter logo axbom’s avatar 2018 Sep 26 Mood -2 🙁
          1. …in reply to @axbom
            The suggestion seems to be to go with the details attribute of the figure tag, and here is a proof-of-concept for this technique: cookiecrook.com/longdesc/details/ #a11y
            Permalink On twitter.com Twitter logo axbom’s avatar 2018 Sep 26 Mood 0
        1. …in reply to @axbom
          More alternatives to longdesc are outlined here: cookiecrook.com/longdesc/ #a11y Based on this I'm leaning towards a standard link in the figure caption.
          Permalink On twitter.com Twitter logo axbom’s avatar 2018 Sep 26 Mood 0
      1. …in reply to @axbom
        Also: read this: ""Longdesc affords authors the native capability to provide information that is essential for blind and visually impaired users but would be redundant for sighted users and unacceptable to visual designers' aesthetics." Unacceptable in this context made me jump.
        Permalink On twitter.com Twitter logo axbom’s avatar ❤️ 1 Favorite 2018 Sep 26 Mood -6 🙁
    1. …in reply to @axbom
      That's an actual quote from the W3C HTML Accessibility Task Force wiki on Verbose desc reqs (Verbose Descriptor Requirements). w3.org/WAI/PF/HTML/wiki/Verbose_desc_reqs
      Permalink On twitter.com Twitter logo axbom’s avatar 2018 Sep 26 Mood 0
  1. …in reply to @axbom
    And now I'm trying to truly grasp accessible modal windows once and for all (which by no means is an easy problem to solve): marcozehe.de/2015/02/05/advanced-aria-tip-2-accessible-modal-dialogs/ I'm a bit saddened by how much of hassle this is to get right. Once I'm confident about a solution I'll do a write-up.
    On twitter.com Twitter logo axbom’s avatar ❤️ 1 Favorite 2018 Sep 26 Mood +1 🙂
    1. …in reply to @axbom
      Just adding the wonderful HTML5 outliner to this thread for easy reference by myself. gsnedders.html5.org/outliner/
      Permalink On twitter.com Twitter logo axbom’s avatar 2018 Sep 26 Mood +5 🙂