View · Index

Weblog Page

Filtered by category Zen Project, 1 - 8 of 8 Postings (all, summary)

.LRN Zen Project

Created by Carl Robert Blesius, last modified by Gustaf Neumann 26 Sep 2019, at 08:36 PM

  1. Accessible and semantic layout/design (first priority)
  2. Layout for screen reader readability
  3. Consistent  CSS for all packages with inheritance where possible
  4. Package specific CSS only where absolutely necessary
  5. Remove as many images as possible
  6. Totally simplified CSS scheme
  7. Consistent deprecation
  8. Support for 4 font sizes without UI breakup
  9. File path re-factoring so designers can easily skin a local installation and upload zip file with local styles for sharing accross installations
  10. A theme page that includes as many existing adp chunks and form templates as possible.
  11. Theme manager that allows a designer to upload a css file and immediately test it against the theme page.
  12. One style for screen, one for print, and one for mobile

 Discussion

     0. Why not OpenACS Zen? I think this needs to apply across the toolkit for any package, not just .LRN ones, or there will forever be problems as new applications come out for OpenACS, and are later adopted for .LRN. DaveB, we are going to start with .LRN b/c it contains a limited number of packages and also because there is an accessibility push in the project. A big portion of this will also be defining best practices. CarlB

    1. I agree with Carl.  I have been working through some of this on our own generic OpenACS installs here but would love to co-ordinate with others.  Robert.

    2. I also will help out. I have several tools available and will look at what is redundant and post soon. Jon Griffin

   3. Please consider expanding the scope of the guidelines to include OpenACS and similar efforts underway at Interface / CSS Coding Guidelines. Accessibility etc. is important for the entire toolkit and long overdue. -Torben

References to this Page: en:Interface___CSS_Coding_Guidelines, en:.LRN_2.3 Categories: Zen Project (OpenACS.org)

.LRN Zen Project: YEF grant

Created by Avni Khatri, last modified by Benjamin Brink 30 Jun 2017, at 05:55 AM

Overview

This page is being used to track the work done for the .LRN Zen Project Phase Two with money received from the YEF grant. The grant will cover work to make the latest forums package conform to WCAG 2.0 AA accessibility standards. The goal is to finish the project in time to apply for a large YEF grant in the next cycle - June 2011.

Team Members

  • Dave Bauer
  • Avni Khatri
  • Carl Blesius
  • Emmanuelle Raffenne
  • Michael Steigman

Regular Meetings

  • Wednesdays 6:10pm PT / 9:10pm ET
  • Ask Avni for the dial-in if you want to attend

Current Status

  • Overall status
    • Dave reviewed all of the WCAG 2.0 Guidelines document to get a better understanding of the scope of this project.
      The good news is that since we use consistent templates, forms, etc most of the code is automatically generated and we can make the code generators compliant and just check the output. 
      He's modified the spreadsheet list to combine the checklist and functional steps because it was recommended to go straight to the WCAG documents.
  • Action items
    • (Dave) Try out the proposed process on one of the forum pages - 2/16
    • (Avni) Work with Emmanuelle (if she has time) to come up with simplified WCAG 2.0 AA checklist we will use - 2/16
      • http://webaim.org/standards/wcag/checklist 
    • Send Emmanuelle a finalized project plan with estimates and have her review - 2/23

Estimated LOE

  • https://spreadsheets.google.com/ccc?key=0Ai-_Aw_13c7ddGFvNHRiaS1zZElfSGdJZTNwLTB1b1E
  • Current estimate for the work is 74.25 not counting meetings

Relevant Links

Hour Tracking

  • Try out proposed process (Dave) = .5 hour
  • Come up with simplified checklist (Avni, Emmanuelle) = ? 
  • Meeting 2/9 - 0.5 * 2 (Dave, Avni) = 1 hour
  • Create project tracking page (Avni) = 1 hour
  • Meeting 2/2 - 0.5 * 3 (Dave, Carl, Avni) = 1.5 hours
  • Determine LOE - (Dave) = 1 hour
  • Meeting 1/26 - 0.5 * 3 (Dave, Carl, Avni) = 1.5 hours
  • Discuss scope of project, package (Dave, Michael) = ?
  • Meeting 1/19 - 0.5 * 3 (Dave, Carl, Avni) = 1.5 hours

Categories: Zen Project (OpenACS.org)

.LRN Zen Project: Standards

Created by Avni Khatri, last modified by Gustaf Neumann 22 Jun 2017, at 09:44 AM

Administration

  • Goal: WAI-AA compliance

Steps to Cleanup (Zenify) a Package Page

  1. View Page in a browser and view source of page
  2. Check Doctype
  3. Check Title (optional)
  4. Check for H1-Hn and make sure they are in order. If not, make them so.
  5. Close all HTML tags
  6. Make sure there is no inline CSS
  7. Add an ALT attribute for IMG tags
  8. Add a TITLE attribute for A tags as necessary
  9. Check all user visible text and make sure it is using message keys instead of text
  10. If page has a form, make sure it is using formbuilder
  11. If page has data in tabular format, make sure it is using listbuilder
  12. Run accessibility tests

Doctype

  1. First target: Validated HTML 4.01 Strict
  2. Code:
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
  3. Background: Choosing a DOCTYPE. Why not XHTML? See http://www.hixie.ch/advocacy/xhtml

Basic Page Requirements

  1. Title: should be in title tag, breadcrumbs, and h1 at top of page.
    1. To accomplish that, ADP pages using the <master> tag should pass the following properties.

      <property name="title">Page Title</property>
      <property name="context">{ { breadcrumb_url link_title } .. last_breadcrumb_element, title unless there is a good reason for it to be something else}</property>

      You don't need to manually build the context bar UNLESS you want to include a URL that is not part of the site map. In other words, the context for 99% of pages should just be a one element list containing the page title or other text you want as the last element of the context bar.  (DAVEB)

      Title and context variables are set in the Tcl file so the property call looks like this
      <property name="title">@title;literal@</property>
      <property name="context">@context;literal@</property>
  2. Use message keys instead of text. https://openacs.org/doc/i18n-convert.html

Applying new CSS and HTML clean-up 

  • Close HTML tags (LI, P, etc.)
  • ID attributes must start with a letter
  • Styles should be in CSS (no inline styles)
  • Provide an ALT attribute for IMG tags (chekpoint 1.1 - priority 1 - A). The ALT text should be localized. When the image is used for layout only, set an empty string for ALT (ALT="").
  • Clearly identify the target of each link (A tag) by providing an TITLE attribute (checkpoint 13.1 - priority 2 - AA). The text should be meaningful and localized. More Info: https://www.nngroup.com/articles/title-attribute/
  • For data tables, identify row and column headers (checkpoint 5.1 - priority 1 - A). The best is to use list template when it's possible. Otherwise, make sure:
    • your table has a summary tag
    • you use <caption><thead> <tfooot><tbody> where appropriate.
    • you give column and row headers a scope: <thead> <th id=""> <tbody> <td headers="">
    • If you headers are really long you give them abbr.       
      <table class="list-table" cellpadding="3" cellspacing="1" summary="Data for folders">
 <thead>
  <tr class="list-header">
   <th class="list-table" id="folders_name">Name</th>
   <th class="list-table" id="folders_type">Type</th>
   <th class="list-table" id="folders_size">Size</th>
  </tr>
 </thead>
 <tbody>
  <tr class="odd">
   <td class="list-table" headers="folders_name"><a href="#">Course 2 Files</a></td>
   <td class="list-table" headers="folders_type">folder</td>
   <td class="list-table" headers="folders_size">2 items</td>
  </tr>
  <tr class="even">
   <td class="list-table" headers="folders_name"><a href="#">Course 1 Files</a></td>
   <td class="list-table" headers="folders_type">folder</td>
   <td class="list-table" headers="folders_size">2 items</td>
  </tr>
 </tbody>
</table>

Form Builder and Template

  1. All forms will use the default form template (standard.adp) now. 
    1. Therefore, there is no longer a need to have  the "style" attribute in the formtemplate tag.  (i.e. <formtemplate id=zen style=inline>). We can get rid of this attribute on all forms that currently use it.
    2. Instead, there are different CSS classes that can be applied to all forms to get the same effect of inline.adp, plainest.adp, and other form templates while actually using the zen-ified standard.adp.  The form class to be used is passed in the "html" parameter of the ad_form proc.                                                                     
      • Example:
        • ad_form -name "zen" -method post -html {class vertical-form}..... -form {....}
        • This will render: <form name="zen" method="post" class="vertical-form">
  2. List of form classes available and example URLs.
    • Note: Example forms are checked into the 5.3 branch. Example files are listed below.
    • margin-form : This is the default form class if none is passed to the ad_form proc
      • /packages/theme-zen/doc/forms/index*
    • vertical-form
      • /packages/theme-zen/doc/forms/form-vertical*
    • inline-form : Replaces inline.adp
      • /packages/theme-zen/doc/forms/form-inline*
  3. Example:
    • Change:
      • <formtemplate id=zen style=inline>
    • To:
      • <formtemplate id=zen>
      • And modify the tcl ad_form call to pass a class to the form, so it will be like this:
        • ad_form -name "zen" ... -html {... class inline-form}.... -form {...}
  4. If the form you working on started out as <formtemplate id="zen">, then you probably don't need to change the formtemplate or the form class. The defaults will  most likely work fine. Look at the page in a browser and see how it is rendered.  If you have any questions about which formtemplate to use, ask Mark Wylie.
  5. Fieldsets and Fieldset Legends
    1. Legends need to be short, there is no line wrapping for legends
    2. more fieldset and legend info coming soon
  6. If you have to hand code a form, it should look something like this:
<form class="margin-form">
 <fieldset>
  <legend>Short Legend</legend>
  <div class="form-item-wrapper">
   <div class="form-label">
    <label for="first_name">First Name</label>
     <div class="form-required-mark">(required)</div>
   </div>
   <div class="form-widget">
    <input type="text" name="first_name" id="first_name" size="30" />
   </div>
   <div class="form-help-text">
    <img src="images/icons/info.png" alt="info" width="16" height="16" /> Some info text
   </div>
   <div class="form-error">
    <img src="images/icons/exclamation.png" alt="error" width="16" height="16" /> This field was in error
   </div>
  </div>
  <div class="form-button">
   <input type="submit" name="formbutton:submit" value="submit" />
  </div>
 </fieldset>
</form>

Using sections in ad_form

The "section" element property is not longer supported. See Web_Forms for an example of how to use sections in ad-form.

List Builder and Template

When creating a list template that contains links, provide a title attribute (with a meaningful and localized text) for each of them (checkpoint 13.1 - priority 2 - AA). Example:

template::list::create \
    -name messages \
    -html [list summary "Summary title"] \
    -caption "Optional caption" \
    -multirow messages \
    -page_size $page_size \
    -page_query_name messages_select_paginate \
    -pass_properties { moderate_p } \
    -actions $actions \
    -elements {
        subject {
            label "[_ forums.Subject]"
            link_url_col message_url
            link_html {title "[_ forums.goto_thread_subject]" class "myclass"}
        }
    }

This is also true for actions list. Example:

lappend actions [_ forums.Post_a_New_Message]\
	[export_vars -base "${base_url}message-post" { forum_id }]\
	[_ forums.Post_a_New_Message]

New Parameters

  • caption - optional
  • summary - required for AA. There is a default in place: "Data for %list_name%" 

 W3C Web Content Accessibility Checkpoints

Zen aims at being Level AA compliant (priority 2 checkpoints):

 

Tools for Checking Accessibility

Accessibility Evaluation Toolbar (Firefox):

  • Disable javascript: alternatives should be provided to js actions
  • Disable styles (CSS): to verify the render for text only browsers
  • Disable images: ALT texts should appear for each image
  • Display title attribute: a meaningful title should be provided for each link
  • Linearize page: tables should linearize well
  • Validate local HTML
  • Validate local CSS
  • Validate local accessibility
  • Validate package and inline (if you're using the new inline class) CSS.

Colour Contrast Analyser ( Firefox):

  • Use the "Luminosity Contrast Ratio" option.
  • For the default CSS, the page should pass at level 2
  • For the HC (High Contrast) CSS, the page should pass at level 3

Fangs, the Screen Reader Emulator (Firefox)

Hera (automatic and manual reports)

WebXact (if HERA is not working)

Others tips

  • Use Opera's View/Small Screen mode to test the handheld.css.

Important Checkpoints

  • WCAG - Checkpoint 3.5: Use header elements to convey document structure
    and use them according to specification.
  • WCAG - Checkpoint 5.3: Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent. Documents with two columns or more use tables to give structure. Layers should be used, instead.

 

References to this Page: en:docs-dev-tutorial, en:coding-standards-index, en:dotlrn-zen-bugbash Categories: Zen Project (OpenACS.org), Coding Standards (OpenACS.org), Accessibility (OpenACS.org)

.LRN Zen Project: Package Completion Checklist

Created by Red Wylie, last modified by Gustaf Neumann 17 Jun 2017, at 10:19 AM

 Package  File 508 AA Con HTML Notes UNED
               
news www/index.adp            
  www/item.adp            
www item-create.adp         FORM BUILDER  
www preview.adp            
               
               
news-portlet              
www news-admin-portlet x x x      
www news-portlet.adp x x x      
www summary.adp x x x      
               
file-storage              
www folder-create            
www file-add            
www simple-add            
fs-portlet              
www fs-portlet            
dotlrn              
www applets-chunk.adp x 13.1 x   AA caused by breadcrumbs and tabs having same name  
www communities.adp x x x      
www communities-chunk.adp         uses listbuilder already  
www community-member.adp x x x      
www community-member2.adp            
www community-edit.adp x          
www community-edit-2.adp            
www community-type.adp x x x      
www community-types-chunk.adp         converted to list builder  
www control-panel.adp x x x      
www courses.adp x x x   no content  
www deregister-confirm.adp            
www dotlrn-group-admin-faq.adp         Needs to be I18N  
www dotlrn-main-portlet.adp x x x      
www dotlrn-user-faq.adp         Needs to be I18N  
www element-list.adp         converted to use list builder  
www element-rename.adp            
www help.adp         Need to be i18n  
www manage-memberships.adp         converted to use list builder  
www member-add.adp x x x      
www member-add-2.adp         FORM-BUILDER - INLINE  
www member-confirm.adp            
www member-email.adp         Needs to be I18N  
www member-email-confirm.adp         Needs to be I18N  
www members.adp         LIST BUILDER  
www members-chunk.adp            
www members-chunk-table.adp         LIST-BUILDER  
www my-communities.adp         LIST-BUILDER  
www spam-2.adp         FORM BUILDER  
www spam-recipients.adp         LIST BUILDER/ FORM BUILDER  
www spam-variables.adp         LIST BUILDER  
www user-add.adp            
www user-add-2.adp         FORM BUILDER  
www weblog-control-panel.adp            
lib bio.adp x x x      
               
               
               
  dotlrn-admins         FORM-BUILDER - INLINE  
               
notifications all user visible files x x x   DONE  
               
dotlrn-portlet              
www dotlrn-admin-portlet.adp x x x      
www dotlrn-members-portlet.adp x x x      
www dotlrn-members-staff-portlet x x x      
www dotlrn-portlet.adp x x x      

 

              
calendar + portlet              
www view (day/week/month/list) x   x x

no HC

problem with form

  
calendar-portlet/ww all portlets x   x x no HC  
               
faq   508 AA Con HTML    
www one-faq x x x x

table used for layout needs to be change

- ah found the table.  looking into it.

  
www one-question x x x x    
www cat*     x   needs lots of work  
www index x x x x    
               
www/admin index x x x x    
www/admin faq-add-edit     x      
www/admin configure x x x x    
www/admin one-faq     x      
www/admin q-and-a-add-edit     x      
www/admin one-question     x      
www/admin faq-disable x x x x    
www/admin faq-delete     x      
www/admin swap     x      
               
Assessment              
www index.adp            
www instructions.adp            
               
               

Categories: Zen Project (OpenACS.org)

WCAG 1.0 Checkpoints

Created by Emmanuelle Raffenne, last modified by Gustaf Neumann 02 Jun 2017, at 09:06 AM

Status at 21 october 2008 (OpenACS 5.4.3 and .LRN 2.4.1)

A summary for US Section 508 is available at LINK_TO_WIKIPAGE 

See Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0 for details

How to read this document

Accessibility Compliance Level

  • Level A means that all the priority 1 checkpoints are in state "Y" or "n/a".
  • Level AA means that level A has been reached + all the priority 2 checkpoints are in state "Y" or "n/a"
  • Level AAA means that level AA has been reached + all the priority 3 checkpoints are in state "Y" or "n/a"

Checkpoint Status

  • Y: 100% of the pages comply with the checkpoint or the exceptions are clearly identified and listed in the accessibility statement.
  • N: NOT 100% of the pages comply with the checkpoint, exceptions are NOT identified.
  • n/a: the situation described in the checkpoint is not applicable in ANY of the pages

OpenACS-specific Techniques for Checkpoints

Each checkpoint is identified with a number which links to the OpenACS-specific techniques to apply it.

 

Note: the  links are dead right now, but will point to OpenACS-specific techniques to implement them.

Priority 1 checkpoints

In General (Priority 1) Yes No N/A
1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.  Y    
2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup.  Y    
4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).  Y    
6.1 Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document.  Y    
6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes.      n/a
7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker.  Y    
14.1 Use the clearest and simplest language appropriate for a site's content.  

 N

e.g.: portlet

  
And if you use images and image maps (Priority 1) Yes No N/A
1.2 Provide redundant text links for each active region of a server-side image map.      n/a
9.1 Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.      n/a
And if you use tables (Priority 1) Yes No N/A
5.1 For data tables, identify row and column headers. Y     
5.2 For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells.  Y    
And if you use frames (Priority 1) Yes No N/A
12.1 Title each frame to facilitate frame identification and navigation.  Y    
And if you use applets and scripts (Priority 1) Yes No N/A
6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.  

 N

lorsm

  
And if you use multimedia (Priority 1) Yes No N/A
1.3 Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation.      n/a
1.4 For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation.      n/a
And if all else fails (Priority 1) Yes No N/A
11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page.  

N

lorsm

  

Priority 2 checkpoints

In General (Priority 2) Yes No N/A
2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. [Priority 2 for images, Priority 3 for text].  Y    
3.1 When an appropriate markup language exists, use markup rather than images to convey information.  Y    
3.2 Create documents that validate to published formal grammars.  Y    
3.3 Use style sheets to control layout and presentation.  Y    
3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values.  

  N

calendar

  
3.5 Use header elements to convey document structure and use them according to specification.  Y    
3.6 Mark up lists and list items properly.  Y    
3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation.  Y    
6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page.      n/a
7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off).  Y    
7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.  Y    
7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects.  Y    
10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user.  Y    
11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.  Y    
11.2 Avoid deprecated features of W3C technologies.  Y    
12.3 Divide large blocks of information into more manageable groups where natural and appropriate.      n/a
13.1 Clearly identify the target of each link.  Y    
13.2 Provide metadata to add semantic information to pages and sites.  Y    
13.3 Provide information about the general layout of a site (e.g., a site map or table of contents). Y    
13.4 Use navigation mechanisms in a consistent manner.  Y    
And if you use tables (Priority 2) Yes No N/A
5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version).  Y    
5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting.  Y    
And if you use frames (Priority 2) Yes No N/A
12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone.  Y    
And if you use forms (Priority 2) Yes No N/A
10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned.   Y    
12.4 Associate labels explicitly with their controls.  Y    
And if you use applets and scripts (Priority 2) Yes No N/A
6.4 For scripts and applets, ensure that event handlers are input device-independent.   Y    
7.3 Until user agents allow users to freeze moving content, avoid movement in pages.      n/a
8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]   Y    
9.2 Ensure that any element that has its own interface can be operated in a device-independent manner.      n/a
9.3 For scripts, specify logical event handlers rather than device-dependent event handlers.   Y    

Priority 3 checkpoints

In General (Priority 3) Yes No N/A
4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs.    N  
4.3 Identify the primary natural language of a document.  Y    
9.4 Create a logical tab order through links, form controls, and objects.    N   
9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls.    N   
10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.  Y    
11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.)  Y    
13.5 Provide navigation bars to highlight and give access to the navigation mechanism.  Y    
13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group.    N    
13.7 If search functions are provided, enable different types of searches for different skill levels and preferences.    N   
13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc.      n/a
13.9 Provide information about document collections (i.e., documents comprising multiple pages.).  Y    
13.10 Provide a means to skip over multi-line ASCII art.      n/a
14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.      n/a
14.3 Create a style of presentation that is consistent across pages.    N  
And if you use images and image maps (Priority 3) Yes No N/A
1.5 Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map.      n/a
And if you use tables (Priority 3) Yes No N/A
5.5 Provide summaries for tables.    N   
5.6 Provide abbreviations for header labels.    N   
10.3 Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns.    N   
And if you use forms (Priority 3) Yes No N/A
10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas.    N   

References to this Page: en:coding-standards-index Categories: Zen Project (OpenACS.org), Coding Standards (OpenACS.org), Accessibility (OpenACS.org)

.LRN Zen Project: Packages HTML clean-up

Created by Emmanuelle Raffenne, last modified by Carl Robert Blesius 20 Mar 2007, at 05:25 AM

Project Zen Deadline / Goal: March, 2007

OpenACS packages

 Package Who's in charge Comments
acs-subsite  Lee
acs-templating (this includes the form and list builder templates)
  Avni, Emma
 DONE!!!
acs-tcl  
acs-lang  
search

acs-admin


.LRN packages

 Package Who's in charge Comments
new-portal
 Don
 Emma: "customize layout" page cleaned. HTML validation OK.
dotlrn + dotlrn-portlet
 Mark, Carl
 First pass done, need to review again after list builder additions
forums + forums-portlet
  Mark, Carl
notifications  Carl
 DONE - Carl is just going to double check
calendar + calendar-portlet

 Avni, Mark

Emma: HTML cleanup

 Mark is done with this package
file-storage + fs-portlet
 Mark 
assessment + assessment-portlet
  Carl, Mark
lorsm + lorsm-portlet
  Emma
 Form sections fixed.
news + news-portlet
  Mark, Carl
faq + faq-portlet
  Cynthia, Avni, Jeff, Rob

making slow progress
static-portlet

attachments

general-comments

bm-portlet
 Rob

evaluation + evaluation-portlet

chat + chat-portlet
 Rob

lars-blogger + weblogger-portlet

random-photo-portlet

dotlrn-homework

dotlrn-syllabus

photo-album + photo-album-portlet
 Avni, Carl
survey + survey-portlet

categories

Categories: Zen Project (OpenACS.org)

.LRN Zen Project: Bug Bash Signup

Created by Avni Khatri, last modified by Avni Khatri 16 Mar 2007, at 07:06 AM

.LRN/OpenACS Zen Bug Bash Signup

Please signup for any day you can.
 

17 March 2007 (Saturday)

Name Location Hours Available (GMT) Role(s)
 Avni Khatri
 Los Angeles
 After 1PM PDT (20GMT)
  
 Mark Wylie
 Boston

 
 Cynthia Kiser
 Los Angeles

 
   
 
   
 
   
 
   
 
   
 
 

18 March 2007 (Sunday)

Name Location Hours Available (GMT) Role(s)
 Avni Khatri
 Los Angeles
10AM-6PM PDT (17-1GMT)
  
 Mark Wylie
 Boston

 
 Emmanuelle Raffenne
 Madrid (CET)

 
 Carl Blesius
 Boston (15 Claremon 1st Floor, Somerville, MA)
10:30AM to 7:00PM Local Time (14:30 - 23 GMT)
 Local Organizer  
 Cynthia Kiser
 Los Angeles

 
   
 
   
 
   
 
   
 
   
 
 

 

 

 

10 March 2007 (Saturday)

Name Location Hours Available (GMT) Role
 Avni Khatri
 Los Angeles

 
 Mark Wylie
 Boston

 
 Emmanuelle Raffenne
 Madrid (CET)

 
 Malte Sussdorff
 Hamburg (CET)

Learn about ZEN and the changes
 Jeff Wang
 LA/San Diego
10am-2 pm (PST)
  
 Carl Blesius  Boston (15 Claremon 1st Floor, Somerville, MA, 02144)
 10:30AM to 7:00PM Local Time (15:30 - Midnight GMT)  Local Organizer
   
 
   
 
   
 
   
 
 

 

11 March 2007 (Sunday)

Name Location Hours Available (GMT) Role
 Avni Khatri
 Los Angeles

 
 Mark Wylie (absent for a few hours)
  Boston
 
 Emmanuelle Raffenne
 Madrid (CET)

 
 Malte Sussdorff
 Hamburg (CET)

try to upgrade openacs.org to 5.3.1 with ZEN
 Carl Blesius
  Boston (15 Claremon 1st Floor, Somerville, MA, 02144) 10:30AM to 7:00PM Local Time (15:30 - Midnight GMT)  Local Organizer
 Michael Aram
Christoph Haberberger
  Vienna University of Economics

12:00 to 17:00 GMT
(13-18 CET)

  
 Michael Totschnig  Vienna University of Economics
 19:30 to 21:00 GMT
(20:30-22 CET)
  
   
 
   
 
   
 
 

3 March 2007 (Saturday)

Name Location Hours Available (GMT) Role(s)
 Avni Khatri
 Los Angeles

 
 Mark Wylie
 Boston

 
 Emmanuelle Raffenne
 Madrid (CET)

 
 Carl Blesius
 Boston (15 Claremon 1st Floor, Somerville, MA)
10:30AM to 7:00PM Local Time (15:30 - Midnight GMT)
 Local Organizer  
 Cynthia Kiser
 Los Angeles
after 4pm PST
  
   
 
   
 
   
 
   
 
   
 
 

 

4 March 2007 (Sunday)

Name Location Hours Available (GMT) Role
Raúl Morales Madrid
 
 Mark Wylie
 Boston

 
 Emmanuelle Raffenne
 Madrid (CET)

 
 Carl Blesius
  Boston (15 Claremon 1st Floor, Somerville, MA, 02144) 10:30AM to 7:00PM Local Time (15:30 - Midnight GMT)  Local Organizer 
 Nima Mazloumi & Co.  Mannheim (CET) 12:00 AM - 6:00 PM
  
   
 
   
 
   
 
   
 
   
 
 

 

 

Categories: Zen Project (OpenACS.org)

.LRN Zen Project: Bug Bash

Created by Avni Khatri, last modified by Nima Mazloumi 03 Mar 2007, at 10:12 PM

.LRN/OpenACS Zen Bug Bash

We are planning on having 2 weekend bug bashes. The goal of these bug bashes is to facilitate the OpenACS core and dotLRN package cleanups in order to meet the Zen Project goals and deadline (12 March 2007).  Please signup for any of the four days you can help.  We can use people at all skill levels. You only need to have basic HTML knowledge.  (i.e. you don't have to be an OpenACS expert)

Please try to signup atleast 2 days before the scheduled bash. Once people have signed up, we will assign packages / pages and roles to people.

Dates & Signup

  1. 3 March 2007
  2. 4 March 2007
  3. 10 March 2007
  4. 11 March 2007

Locations and Coordinators

  1. Boston/Somerville, MA - Carl Robert Blesius & Mark Wylie
  2. Madrid - Emmanuelle Raffenne
  3. Portland, OR - Don Baccus
  4. Los Angeles - Avni M. Khatri
  5. Virtual World - IRC at the #openacs channel
  6. Mannheim - Nima Mazloumi, Sven Schmitt, Stefan Wurdack, Ke Zhang
  7. please add your city and name if you can help coordinate

Guidelines

  1. Goals of the Zen Project
  2. Zen Standards (Go here to get details on how to make OpenACS Zen)
  3. Package & Page Assignment
  4. Package & Page Completion

Bug Bash Jobs and Directions

Before you start, join the online bug bash space by logging into the openacs chat: https://openacs.org/irc/ 

Bug Tester

Job description: test, resolve, close, reopen, comment, add info below to tickets 

Bug Sorter

Job description: check, sort, assign, set priority, add info below to tickets

Bug Basher

  1. Check Zen and 2.3 Bugs
  2. Grab bug (assign it to yourself)
  3. Make sure it is correctly prioritized (1 and 2 will be fixed for 2.3 release)
  4. Make sure it is labeled for the 2.3 and/or Zen
  5. Paste the following info into the ticket: 
    		Key: [+]=done/yes/selected, [-]=does not apply, [?]=I have no idea

    		[ ] Filename: packages/
    		[ ] URL: 
    		[ ] HTML 4.01 Transitional
    		[ ] 508 Bug
    		[ ] Level A Bug
    		[ ] Level AA Bug
    		[ ] Level AAA Bug
    		[ ] Contrast
    		
    		Comment/Details:
  6. Follow the pathway to Zen as outlined on the Zen Standards Page
  7. Close or reassign as you complete steps outlined on that page (make sure and check items off in the list above and categorize bugs as you make progress)

Categories: Zen Project (OpenACS.org)
previous November 2024
Sun Mon Tue Wed Thu Fri Sat
27 28 29 30 31 1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30

Popular tags

17 , 5.10 , 5.10.0 , 5.10.1 , 5.9.0 , 5.9.1 , ad_form , ADP , ajax , aolserver , asynchronous , bgdelivery , bootstrap , bugtracker , CentOS , COMET , compatibility , CSP , CSRF , cvs , debian , docker , docker-compose , emacs , engineering-standards , exec , fedora , FreeBSD , guidelines , host-node-map
No registered users in community xowiki
in last 30 minutes
Contributors

OpenACS.org