18 Matching Annotations
  1. May 2020
  2. Apr 2020
    1. The “universal” label that has been slapped on to it is superfluous, but it does have its merits. Now that we have a commonly known term to refer to environment agnostic JavaScript code, it allows library authors to list it as a feature and be fashionable doing it. I’m happy with the term “universal” being fashionable because it makes developers think about their dependencies on the runtime environment. In the end this will help the JavaScript ecosystem mature and allow libraries to be used everywhere.
    2. The “universal” label that has been slapped on to it is superfluous
  3. Nov 2019
    1. or semantic value, is crucial to the production of information visualization. But any sense that “data” has an inherent “visual form” is an illusion.

      Eye grabbing word: Semantic Value and the statement "But any sense that data has an inherent visual for is an illusion" is a very interesting statement.

  4. Jul 2019
    1. a label will inform the program “this is a cat,” and not a cheeseburger - despite some visual similarity and the former perhaps having the latter.

      This is the label you were hoping someone would put on this right?

      Image courtesy of icanhascheeseburger.

  5. Apr 2019
  6. Oct 2018
    1. It seems like everyday you wake up something has changed … Do you say Jew? Or Jewish? Is it a black guy? African-American? … You are on your toes because you never know what to say. So political correctness in that sense is scary.
  7. Feb 2018
  8. Dec 2017
    1. For example, if there are multiple "Submit" buttons on a screen, the Name for each must be unique

      This seems questionable. If there are "edit" buttons beside each element in a list of elements, must they all have different names, or can their function be inferred from context? I don't think WCAG requires this.

    2. Check each input form field for an ID and a corresponding LABEL or a descriptive TITLE. Fieldset and Legend may be used for grouping and associating two instructions to one input field.

      Does this mean wrapping an edit field with a label is not sufficient? Do such labels need a for attribute pointing to the id of the field?

    3. A web page that has multiple form controls (e.g. buttons) with the same visual label must include unique identifiers that describe their unique purpose.

      This seems questionable. If there are "Add" buttons beside each element in a list of elements, must they all have different names, or can their function be inferred from context? I don't think WCAG requires this.