Project Updates

Lessons Learned – Usability Testing

Participants

  • Nick Hoyt
  • Dena Strong
  • JaEun Jemma Ku

Discussion Topic

  1. Review/analyze three usability testing sessions – result patterns
  2. UX lunch club idea/feedback regarding UI design
  3. Block format discussion regarding Library requirements

Resolution

  • Change/improve vague ” remove format” to specific ones such as “remove heading” or “remove style”
  • Change in tool bar configuration in the second row as the order of
    •  Bold button, Italic button, Inline style menu, remove format button, divider, Special character button, language button (see the attached image below)
  • Gather info about “review format/normal” from other editors such as google doc, MS word, Box) -> comparative analysis by Dena Strong
  • Next “lessons learned meeting from the rest of usability testing” will be on the week of August 14, in which all the usability testings are done.

Discussion and Suggestions from Usability testing

  • Users are confused how to remove “block quotation” style ->redundancy of ” “remove format” function throughout User interface such as “remove format button”, “T” with underline and x mark
  • “inline style” can become “menu” button” not “richcombo” button in CK source function for the consistency
  • Feedback to CKsource -> Language menu button is icon only label, which appears to be kanji character, user thinks that the icon
    • will translate the existing language, not tagging it
    • will add special characters
  • Discussed adding “Normal” menu option under “heading” menu. “Normal” menu is the same function as “remove format” under heading menu
  • Adding font size options such as ” larger” or “smaller” rather than pixel size would help to prevent the users using heading level as a visual style. -> need to confirm its implementation with the rest of group members
  • Trying to find a way to give users ability to remove specific formats in consistet and intuitive way

Project Check-in Meeting

Participants

  • Nick Hoyt
  • Dena Strong
  • JaEun Jemma Ku
  • Jon Gunderson

Agenda

  1. Review/Updates on plugins
  2. Updating public version of a11yfirst editor
    • Merging feature branches or not
  3. Usability testing results
    • Review results of current testing
    • Planned usability testing sessions
  4. Design changes based on user testing
  5. Budget: Conferences
  6. Final project report submission
  7. Team members’ summer vacation schedule

Resolution

  • Keep feature branches separate from master branch
  • JaEun Ku will write up the final project report and share it with the group for the review (Report deadline is Aug 20, 2017)

Action Items

  1. Schedule the separate usability testing result review session by Nick, Dena and JaEun
  2. Schedule the discussion session with the library regarding block format feedback

Development Updates and Usability Testing Dates

Plugin Updates

  • Form validation for link plugin is in progress
  • All the git repo updates regarding heading plugin is done
  • JaEun needs to update a11yfirst server with most up to date a11yfirst editor version

Usability Testing

Dena Strong, Technology Services will administer the usability testing for mileston 1.0 (heading, blockformat, inline style) on July. Six usability testing sessions are being planned.

Usability Testing Dates

  • July 5, 2017
  • July 12, 2017
  • July 19, 2017
  • July 26, 2017
  • August 2, 2017
  • August 9, 2017

 

 

A11yfirst Editor Milestone 1.0

  1. Block Format plugin discussion
    • block format toggle issue
    • “remove format” menu consistency
    • “help” contents for a11yfirst block format plugin – plugin “feature” documentation – Jon was assigned
  2. Milestone 1.0 release schedule: July 15
    • More features were integrated in a11yfirst heading plugin 
    • final code update for a11yfirst block format plugin
    • Offer to test the a11yfirst plugin to University library
  3. Project schedule coordination
    • Team member’s vacation schedule
  4. Student worker hire – 40 hours for 8 weeks

Milestone Discussion

Strategic direction for first milestone

  • using CKeditor checker functionality from CKsource
  • Submit heading plugin as add-on to CKeditor – minimum viable product
  • links – you have headings as anchor link target
  • use existing CKeditor checker for now(categories of checking (filter by object such as heading or images) vs CK editor checker is like laundry list)
  • enhance existing CKeditor UI

Milestone definition

A11yfirst editor 1.0

  • heading + code management
  • inline style
  • block format(include block quotation)
  • toolbar configuration (documentation re a11y)

    Project Milestone 1.0

A11yfirst editor 1.1

  • dialog: empty link text with summary/detail help
  • dialog: non-descriptive link text with summary/detail help
  • help tab in link dialog
  • a11yfirst editor links include warning (see the picture)

A11yfirst editor 1.2

  • a11yfirst image plugin specification:
    • revision of CKeditor image plugin to create a11yfirst image plugin
    • integration of a11yfirst image plugin to WordPress

      Project milestone 1.1 and 1.2

    A11yfirst editor 1.3

    • a11yfirst tables plugin specification

    A11yfirst editor 2.0

    • Enhance heading toc, list of headings, revisiting the link dialog process, adding context for links (ie. adding title)

    A11yfirst editor 2.X

    • “paste from word”: how this works with accessible authoring (paste from pdf, google doc) – Jemma

    Action Item

    Development spec needs to be updated – prototypes and guidance

Milestone / Heading Plugin

Meeting Agenda

  1. Role assignment for project
  2. Proposal for A11yFirst presentation at Accessing Higher ground Conference
  3. Logo update – https://github.com/a11yfirst/ckeditor-plugins/wiki (Project branding should be written as “a11yfirst” everywhere. )
  4. Project milestone by end of May
    • heading
    • block format
    • inline style
  5. Heading checker functionality discussion
    • Is Checker functionality part of a11yfirst heading plugin or A11yfirst checker plugin?
    • Just in time checking – Ckeditor balloon panel (hightlight the block and check/edit heading) – http://ckeditor.com/addon/balloonpanel

Attendants:

Mike, Nick, Jon , JaEun and Tim

Review of Plugin Updates

Project Updates

  • Completed: Inline Style
  • Some or most work has been done: Heading
  • Work in progress, still need some requirements decisions: Block Format
  • Not yet started, need requirements, designs: Link, Image, Table, A11y Checker

Discussion Topic

  • Logistics, details re. how to clone and checkout a tagged version, such as the one mentioned above, so that it could be placed on the Library server.
  • Where we stand with our plugins and what is needed for moving forward:

Action Items

  • A11yfirst plugin license info and where to add copyright issues/ language(ex: JS file)
  • Meeting agenda next week – A11yfirst server setup, requirement documentation/workflow for links, Image and Allycheker