15 Matching Annotations
  1. Jul 2019
    1. Web Accessibility Focus pursues this purpose through four main activities:

      This describes four main activities.

  2. Feb 2019
  3. Nov 2018
  4. Apr 2018
    1. Robust It is this flirty declarative nature makes HTML so incredibly robust. Just look at this video. It shows me pulling chunks out of the Amazon homepage as I browse it, while the page continues to run. Let’s just stop and think about that, because we take it for granted. I’m pulling chunks of code out of a running computer application, AND IT IS STILL WORKING. Jut how… INCREDIBLE is that? Can you imagine pulling random chunks of code out of the memory of your iPhone or Windows laptop, and still expecting it to work? Of course not! But with HTML, it’s a given.
  5. Jan 2018
  6. inclusive-components.design inclusive-components.design
    1. For a consistent experience between users, we need to be deliberate and focus() an appropriate element

      Deliberate decisions about the next action with focus, provide a nicer UX

    2. <use xlink:href="#bin-icon">

      Ah… so THAT's what the hidden SVG at the beginning of the piece was fore

    3. Many kinds of users often feel the need to scale/zoom interfaces, including the short-sighted and those with motor impairments who are looking to create larger touch or click targets.

      Nice argument for leveling up in SVG

    4. In this example, &times; is used to represent a cross symbol. Were it not for the aria-label overriding it, the label would be announced as “times” or “multiplication” depending on the screen reader in question.

      So aria labels overrule clever submit typography. Userful to know

    5. In my version, I just add a minor enhancement: a line-through style for checked items. This is applied to the <label> via the :checked state using an adjacent sibling combinator.

      Clever CSS tricks abound in this piece

    6. It’s quite valid in HTML to provide an <input> control outside of a <form> element. The <input> will not succeed in providing data to the server without the help of JavaScript, but that’s not a problem in an application using XHR.

      Did not know this.

    7. all the state information we need is actually already in the DOM, meaning all we need in order to switch between showing the list and showing the empty-state is CSS.

      Wow. - never thought of this. It's not as obvious as the approach above though if you were working on the code base - how expensive is a check for todos.length?

    8. If you do use a <section> element, you still need to provide a heading to it, otherwise it is an unlabeled section.

      unexpected accessibility gotcha!

  7. Aug 2017
    1. The Ethereum Foundation also notes another issue – the impediment to legitimate use; the benefits to media owners pale in comparison to the detrimental effect the DRM would have on users. According to the Foundation, the DRM will hinder commenting and modification of videos, whether for artistic purposes or to make them accessible to disabled individuals. "All of these uses, normally held in high regard in the W3C Recommendation process, are blocked by DRM.

      Anything that would get in the way of #a11y access is a problem to me.

  8. Dec 2015
    1. The EDUPUB Initiative VitalSource regularly collaborates with independent consultants and industry experts including the National Federation of the Blind (NFB), American Foundation for the Blind (AFB), Tech For All, JISC, Alternative Media Access Center (AMAC), and others. With the help of these experts, VitalSource strives to ensure its platform conforms to applicable accessibility standards including Section 508 of the Rehabilitation Act and the Accessibility Guidelines established by the Worldwide Web Consortium known as WCAG 2.0. The state of the platform's conformance with Section 508 at any point in time is made available through publication of Voluntary Product Accessibility Templates (VPATs).  VitalSource continues to support industry standards for accessibility by conducting conformance testing on all Bookshelf platforms – offline on Windows and Macs; online on Windows and Macs using standard browsers (e.g., Internet Explorer, Mozilla Firefox, Safari); and on mobile devices for iOS and Android. All Bookshelf platforms are evaluated using industry-leading screen reading programs available for the platform including JAWS and NVDA for Windows, VoiceOver for Mac and iOS, and TalkBack for Android. To ensure a comprehensive reading experience, all Bookshelf platforms have been evaluated using EPUB® and enhanced PDF books.

      Could see a lot of potential for Open Standards, including annotations. What’s not so clear is how they can manage to produce such ePub while maintaining their DRM-focused practice. Heard about LCP (Lightweight Content Protection). But have yet to get a fully-accessible ePub which is also DRMed in such a way.

  9. Feb 2014
    1. Host W3C gratefully acknowledges Hypothes.is for hosting this workshop.

      There is an image of the Hypothes.is logo included with this text.