Successfully reported this slideshow.

Designing court websites for the 21st century

764 views

Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Designing court websites for the 21st century

  1. 1. Designing Court Websites for the 21st Century<br />Pierre-Paul Lemyre, LexUM<br />May 12, 2010<br />
  2. 2. The Process<br />
  3. 3. CCCT (2007)<br />The Process<br />
  4. 4. CCCT (2007)<br />Intellaction Working Groups (2009)<br />The Process<br />
  5. 5. CCCT (2007)<br />Intellaction Working Groups (2009)<br />Court websites working group (09/2009)<br />The Process<br />
  6. 6. The Members<br />
  7. 7. The Members<br />Practitioners<br />Alexandre-Philippe Avard (Qc Bar)<br />Patrick Cormier (Qc Bar)<br />John McMunagle (On Bar)<br />
  8. 8. The Members<br />Judiciary<br />Yves-Marie Morisette (QCCA)<br />Alan Ritchie (CAS)<br />Louis Vincent d’Auteuil (Martial Court)<br />
  9. 9. The Members<br />Government officials<br />Louise Hamel (On)<br />Chris Walpole (On)<br />David Williams (On)<br />
  10. 10. The Members<br />Academics<br />Simon Fodden (Osgoode Hall, SLAW)<br />Daniel Poulin (U. de Montréal)<br />Raphael Papicio (Student, U. of Ottawa)<br />
  11. 11. The Members<br />Private Sector<br />Michelle Blanc (Yulbiz – AnalyWeb)<br />Yves Boisvert (La Presse)<br />Pierre-Paul Lemyre (LexUM)<br />Steve Matthews (Stem Legal Web Ent.)<br />Jean-Philippe Ricard (LexUM)<br />
  12. 12. The Mandate<br />
  13. 13. To produce “Canadian Court Website Guidelines”<br />The Mandate<br />
  14. 14. To produce “Canadian Court Website Guidelines”<br />Work plan adopted (10/2009)<br />The Mandate<br />
  15. 15. To produce “Canadian Court Website Guidelines”<br />Work plan adopted (10/2009)<br />Profiles of court websites (12/2009)<br />The Mandate<br />
  16. 16. To produce “Canadian Court Website Guidelines”<br />Work plan adopted (10/2009)<br />Profiles of court websites (12/2009)<br />1st draft circulating (01/2010)<br />The Mandate<br />
  17. 17. To produce “Canadian Court Website Guidelines”<br />Work plan adopted (10/2009)<br />Profiles of court websites (12/2009)<br />1st draft circulating (01/2010)<br />Complete version (in progress)<br />The Mandate<br />
  18. 18. Profiling Court Websites<br />
  19. 19. Profiling Court Websites<br />
  20. 20. About 30 court websites being profiled<br />Profiling Court Websites<br />
  21. 21. About 30 court websites being profiled<br />Canada: federal and provincial (24)<br />Profiling Court Websites<br />
  22. 22. About 30 court websites being profiled<br />Canada: federal and provincial (24)<br />US (5)<br />Profiling Court Websites<br />
  23. 23. About 35 court websites being profiled<br />Canada: federal and provincial (24)<br />US (5)<br />International (7)<br />Profiling Court Websites<br />
  24. 24. Guidelines<br />
  25. 25. Explain typical features<br />Guidelines<br />
  26. 26. Explain typical features<br />Discuss major issues<br />Guidelines<br />
  27. 27. Explain typical features<br />Discuss major issues<br />Offer guidance on structure and content<br />Guidelines<br />
  28. 28. Explain typical features<br />Discuss major issues<br />Offer guidance on structure and content<br />Suggest evaluation criteria for platforms, hosting<br />Guidelines<br />
  29. 29. What are the principles that should guide the design of court websites?<br />
  30. 30. Principle 1: The Right Information for the Right Audience<br />
  31. 31. Principle 1: The Right Information for the Right Audience<br />Which audience?<br />
  32. 32. Principle 1: The Right Information for the Right Audience<br />Which audience?<br />Cost/benefit analysis<br />
  33. 33. Principle 1: The Right Information for the Right Audience<br />Which audience?<br />Cost/benefit analysis<br />Taking responsibility for access to decisions<br />
  34. 34. Principle 2: Empowerment<br />
  35. 35. Consumers<br />Can self-identify with a user category<br />Can choose content subscription options<br />Principle 2: Empowerment<br />
  36. 36. Consumers<br />Can self-identify with a user category<br />Can choose content subscription options<br />Creators<br />Can publish without involving technical staff<br />Know the best practices<br />Principle 2: Empowerment<br />
  37. 37. Custodians (sys admin)<br />Access to 2nd and 3rd lines of support<br />Access to GUI to administer the website<br />Provided with a modular framework<br />Principle 2: Empowerment<br />
  38. 38. Principle 3: Timeliness<br />
  39. 39. Reducing the delays for<br />Information to be ready for publication<br />Information to be made accessible on the website<br />Principle 3: Timeliness<br />
  40. 40. Reducing the delays for<br />Information to be ready for publication<br />Information to be made accessible on the website<br />Eliminating intermediaries<br />Principle 3: Timeliness<br />
  41. 41. Principle 4: Notification<br />
  42. 42. Provide the option between<br />Mailing lists<br />RSS feeds<br />Principle 4: Notification<br />
  43. 43. Provide the option between<br />Mailing lists<br />RSS feeds<br />Integrate taxonomy, fields of law, if available<br />Principle 4: Notification<br />
  44. 44. Principle 5: Content Organization & Search<br />
  45. 45. Principle 5: Content Organization & Search<br />Menu Navigation<br />Do some usability testing<br />
  46. 46. Principle 5: Content Organization & Search<br />Menu Navigation<br />Do some usability testing<br />Taxonomies<br />Classify, organize by categories whenever possible<br />
  47. 47. Principle 5: Content Organization & Search<br />Menu Navigation<br />Do some usability testing<br />Taxonomies<br />Classify, organize by categories whenever possible<br />Free Tagging<br />Users can assign personal on-the-fly terms<br />
  48. 48. Principle 5: Content Organization & Search<br />Search<br />Full-text faceted search is affordable<br />Natural language search is still expansive<br />
  49. 49. Principle 6: Security<br />
  50. 50. Confidentiality<br />Try not to put confidential information on the site<br />If unavoidable: security audit and testing<br />Principle 6: Security<br />
  51. 51. Integrity<br />Views and permissions management<br />Public/private key systems (not there yet)<br />Principle 6: Security<br />
  52. 52. Availability<br />Uptime vs downtime<br />Choose a reliable platform<br />Choose a reliable hosting provider<br />Principle 6: Security<br />
  53. 53. Principle 7: Bilingualism<br />
  54. 54. All Canadian court websites should be bilingual at a minimum<br />Interface<br />Content<br />Principle 7: Bilingualism<br />
  55. 55. All Canadian court websites should be bilingual at a minimum<br />Interface<br />Content<br />The platform can facilitate the revision of translations<br />Principle 7: Bilingualism<br />
  56. 56. Principle 8: Accessibility<br />
  57. 57. Web Content Accessibility Guidelines of the W3C, v. 2.0<br />Textual equivalents of images, underline on links, …<br />Grade A, AA, AAA<br />Principle 8: Accessibility<br />
  58. 58. Web Content Accessibility Guidelines of the W3C, v. 2.0<br />Textual equivalents of images, underline on links, …<br />Grade A, AA, AAA<br />All Canadian court websites should be Grade A at a minimum<br />Principle 8: Accessibility<br />
  59. 59. Where not possible, put a notice<br />Principle 8: Accessibility<br />
  60. 60. Principle 9: Interactivity<br />
  61. 61. Commenting<br />For each type of content, should comments be allowed?<br />Principle 9: Interactivity<br />
  62. 62. Commenting<br />For each type of content, should comments be allowed?<br />Form filling<br />For each court form, should online submission by parties be allowed?<br />Principle 9: Interactivity<br />
  63. 63. E-filling<br />Should the online submission of courts documents by lawyers be allowed?<br />See available information from the E-filling CCCT Working Group<br />Principle 9: Interactivity<br />
  64. 64. Principle 10: Viability<br />
  65. 65. Cost effectiveness (TCO)<br />Principle 10: Viability<br />
  66. 66. Cost effectiveness (TCO)<br />Effectiveness of the platform<br />Principle 10: Viability<br />
  67. 67. Cost effectiveness (TCO)<br />Effectiveness of the platform<br />Efficiency of the platform<br />Principle 10: Viability<br />
  68. 68. Cost effectiveness (TCO)<br />Effectiveness of the platform<br />Efficiency of the platform<br />Sustainability (maintenance and updates, user base)<br />Principle 10: Viability<br />
  69. 69. Cost effectiveness (TCO)<br />Effectiveness of the platform<br />Efficiency of the platform<br />Sustainability (maintenance and updates, user base)<br />Flexibility (ease to customize)<br />Principle 10: Viability<br />
  70. 70. Principle 11: Simplicity<br />
  71. 71. Of the CMS<br />Principle 11: Simplicity<br />
  72. 72. Of the CMS<br />In customizing<br />Principle 11: Simplicity<br />
  73. 73. Of the CMS<br />In customizing<br />In integration with legacy systems<br />Principle 11: Simplicity<br />
  74. 74. Of the CMS<br />In customizing<br />In integration with legacy systems<br />Build step-by-step instead of over-engineering from the start<br />Principle 11: Simplicity<br />
  75. 75. Enough for Now<br />
  76. 76. Final guidelines<br />To be completed this summer<br />To be launched around the Forum on Court Technology, Sept 22-23, Ottawa <br />Enough for Now<br />
  77. 77. Thank you!<br />Pierre-Paul Lemyre, LexUM<br />lemyrep@lexum.com<br />

×