Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 59709 invoked from network); 26 Sep 2008 01:50:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Sep 2008 01:50:45 -0000 Received: (qmail 62092 invoked by uid 500); 26 Sep 2008 01:50:42 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 62047 invoked by uid 500); 26 Sep 2008 01:50:41 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 62036 invoked by uid 99); 26 Sep 2008 01:50:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Sep 2008 18:50:41 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xhhsld@gmail.com designates 209.85.200.173 as permitted sender) Received: from [209.85.200.173] (HELO wf-out-1314.google.com) (209.85.200.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Sep 2008 01:49:42 +0000 Received: by wf-out-1314.google.com with SMTP id 28so914731wfa.25 for ; Thu, 25 Sep 2008 18:50:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=jMpRRI4LQKKGLJmPdsE+FkVs8960He8zQuLjAE4oIrc=; b=Jfg2ipnsorkyEpD0e4tamk6/LDQef/m8hmp+MPL4whng7O7W/ohvZ3lL8CAs/XR0z6 Exzvj10VmvIOcY8gp+/IYmMIlb+fWG6tbx9BUejsNniOMF+HmMKwsZegFrQO+yvIeCu/ O0domjVNmeBcnnXoSVmKnksYppTHdfb43CaUU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=sz8Uc2TohM9Fm2bjQM/6T81eF+C9kdMVEoPMW4Xu3gZHBIMBqfQ20/kCtXZiZzaQpo KKqZsQkRBmTDC7FyUfZpprmA0xoeJ9RTnK+pispURqDqr+hRVU6mMlvW9IEeBBg+9neB 6yUuxaDFHx7UTUK8ayuAXcUIVYHunPyCr8Yl0= Received: by 10.142.178.13 with SMTP id a13mr247374wff.251.1222393806245; Thu, 25 Sep 2008 18:50:06 -0700 (PDT) Received: by 10.142.110.7 with HTTP; Thu, 25 Sep 2008 18:50:06 -0700 (PDT) Message-ID: <45f744e40809251850m3ba00e48i1d2e50c868073947@mail.gmail.com> Date: Fri, 26 Sep 2008 09:50:06 +0800 From: Ivan To: dev@geronimo.apache.org Subject: Re: Fixing usability/accessibility issues in Admin Console In-Reply-To: <48DBA894.7010200@apache.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2325_9823016.1222393806220" References: <5e7fd1eb0807022353w11505feelff46ad6d989c193b@mail.gmail.com> <48DBA894.7010200@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_2325_9823016.1222393806220 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi: I will re-search the newest codes, and if no similiar issues exists, I think we could close it. Thanks ! Ivan 2008/9/25 Donald Woods > All of the patches from Ivan in G4081 have been applied to trunk. > Are there anymore patches needed or can we close G4081 and open another > JIRA in the future if new problems are found before we release 2.2? > > > -Donald > > > Jack wrote: > >> Hi all! >> >> A newbie here - Cai Jun Jie. You can also call me Jack! >> >> My teammates and I have been looking at accessibility of Geronimo's Admin >> Console. Most people would think that accessibility only matters for the >> disabled. Yet some people argue - which I also mostly agree - that if we >> make software easily accessible, then it benefits all the users! >> >> There are already some JIRAs openned against Admin Console's accessiblity, >> e.g., GERONIMO-4081 , >> GERONIMO-4080 . >> After a quick analysis, the top 3 problems we see include - >> 1. No error messages shown when invalid form data are submitted. This is a >> usability issue for all users. >> 2. No label element defined for form elements. This prevents some screen >> reader software from reading HTML forms in a meaningful way. Screen reader >> software is a key assisting tools for low-vision people. >> 3. No ALT attributes defined for images. Similar to Problem 2. >> >> We will be submitting patches to fix Problem 2 & 3. Since there are so >> many occurrences, we will divide the patches based on page groups. We will >> leave the problems that exist in DOJO though, hoping that more recent DOJO >> releases will have most of their problems resolved. >> >> As to Problem 1, I believe we should define a unified way to present error >> messages. For example, for invalid form data, stay on the same page and >> present the error message near each form element that has the invalid input; >> and for other error (like system error), stay on the same page and present >> the error message at the top of the main content. Or, simply present all >> kinds of error message at the top of the main content... >> >> Would be very interested in knowing the community's opinions... >> >> Regards, >> >> Jack Cai >> >> >> -- Ivan ------=_Part_2325_9823016.1222393806220 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Hi:
    I will re-search the newest codes, and if no similiar issues exists, I think we could close it.
    Thanks !
               Ivan

2008/9/25 Donald Woods <dwoods@apache.org>
All of the patches from Ivan in G4081 have been applied to trunk.
Are there anymore patches needed or can we close G4081 and open another JIRA in the future if new problems are found before we release 2.2?


-Donald


Jack wrote:
Hi all!

A newbie here - Cai Jun Jie. You can also call me Jack!

My teammates and I have been looking at accessibility of Geronimo's Admin Console. Most people would think that accessibility only matters for the disabled. Yet some people argue - which I also mostly agree - that if we make software easily accessible, then it benefits all the users!

There are already some JIRAs openned against Admin Console's accessiblity, e.g., GERONIMO-4081 <https://issues.apache.org/jira/browse/GERONIMO-4081>, GERONIMO-4080 <https://issues.apache.org/jira/browse/GERONIMO-4080>. After a quick analysis, the top 3 problems we see include -
1. No error messages shown when invalid form data are submitted. This is a usability issue for all users.
2. No label element defined for form elements. This prevents some screen reader software from reading HTML forms in a meaningful way. Screen reader software is a key assisting tools for low-vision people.
3. No ALT attributes defined for images. Similar to Problem 2.

We will be submitting patches to fix Problem 2 & 3. Since there are so many occurrences, we will divide the patches based on page groups. We will leave the problems that exist in DOJO though, hoping that more recent DOJO releases will have most of their problems resolved.

As to Problem 1, I believe we should define a unified way to present error messages. For example, for invalid form data, stay on the same page and present the error message near each form element that has the invalid input; and for other error (like system error), stay on the same page and present the error message at the top of the main content. Or, simply present all kinds of error message at the top of the main content...

Would be very interested in knowing the community's opinions...

Regards,

Jack Cai





--
Ivan
------=_Part_2325_9823016.1222393806220--