Summary for March 1st 2011 UI Chat

Limbo chat! Getting ready for 3.2 and figuring out what’s what and who has interest in working on specific projects for 3.2.

  • andewryno – looking at outputting semantic markup through WP settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. – working directly with Nacin on this
  • Chexee / saracannon – focusing on visual design tasks (TBC)
  • JohnONolan – will continue his CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. crusade, mostly
  • TECannon – accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) design / docs
  • jsternberg (new member) – interested in some design / CSS tasks

Short review of Chexee’s “Press This” bookmarklet button – concensus leaning heavily towards the left (lighter) buttons and generally towards the top of the list to match browsers and avoid confusion with rounded action-buttons. Some concerns raised over UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. behind the literal meaning of the words “Press This” on a button. Suggestion was also raised for cursor hove state to be a 4-way grabber instead of a pointer to better indicate intended use.

Aiming to have a 3.2 UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. roadmap for next week’s meeting.

#summary