26 Matching Annotations
  1. Apr 2021
  2. Mar 2021
    1. You don’t need to do any tricky cursor stuff, because it’s all semantically wired up already.
    2. I’d say if the form is short and an obvious pattern (like sign up or log in), you could use the placeholder visual pattern, but use real labels instead.
    3. If they click the area taken up by the label, it will activate the input. If they click the input, it will activate the input. Both correct.
  3. Nov 2020
    1. I like to keep the ‘verb’ + ‘noun’ structure when writing button labels — this makes the action more prescriptive, e.g. ‘Save post’, ‘Next step’, etc, as opposed to ‘Save’, ‘Next’
  4. Oct 2020
    1. first sighting: use of superscripts like this

      I like it. Nice and concise and understandable.

      • s¹  critical
      • s²  important
      • s³  nice to have
      • s⁴  low
      • s⁵  inconvenient

      But in other cases, the abbreviation is quite unclear and ambiguity:

      Like, what does "pr" mean in these cases?

      priority? Doubt it.

      • pr¹  chore
      • pr²  docs
      • pr³  feature
      • pr⁴  fix
      • pr⁵  performance
      • pr⁶  refactor
      • pr⁷  style

      Pull Request? Doubt it. But maybe?


      For axes that are quantifiable, like severity, using a number makes sense. But what benefit is there in including a number in these (platform?) labels?:

      • p¹ ⋅ browser
      • p² ⋅ linux
      • p³ ⋅ mac
      • p⁴ ⋅ windows

      I think this would have been better and clearer (in that fewer people would be like huh? and wonder what it means):

      • platform: browser
      • platform: linux
      • platform: mac
      • platform: windows
  5. May 2020
  6. 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
  7. 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.

  8. 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.

  9. 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.
  10. Feb 2018
  11. 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.