Recent Forum Posts
From categories:
test post
cliffscliffs 24 Mar 2009 00:51
in discussion Hidden / Per page discussions » Ghana Pilot

test

test post by cliffscliffs, 24 Mar 2009 00:51

My apologies in advance if this does not come through correctly; the Wiki has some accessibility issues for me that cannot be resolved easily.

I agree that the column layout might confuse some people, but instead of reducing the entire interface to something that will not be scalable beyond a very small number of files, I suggest we re-define the Home Location as Column C instead of A. that way users are taken to Content Module titles as soon as the device is turned on or as soon as they press Home.

I disagree with the desire to drop entirely the columns-based interface. These devices are not going to be used in complete isolation from any type of orientation; and a basic columns format, i.e. 2-D grid, is something anyone can draw with a few lines on the dirt. It does not require sophisticated concepts or 3-D analogies.

I just noticed this discussion link so sorry for being late to the party. I agree with wlai that this is might not be very intuitive to an illiterate user (it's not even that intuitive to me as I read it).
I think wlai's idea in the last sentence of just one column using date-time stamp is a good one.
I think I also agree with transposing the table but I would really like to see a diagram/flowchart of this whole thing.

Mozilla Accessibility Project
Link:
http://www.mozilla.org/access/

This community is awesome in what they have accomplished. To me this is very similar to the Eclipse community that rallys around the free development tool. At the same time I look at that community as fast succumbing to the encroching Netbeans development tool and its ever increasing community.

This is the momentum I see behind Opera and its plugin community. What would be great is if the browser wars were set aside and the APIs behind the plugins were abstracted away from browser functionality enough that plugins could be made for any browser with plugin architecture.

All things aside if/when we do look at browser support for our applied software this, to me anyway, is the one aspect that keeps Firefox balanced on its upside down pyramid of design and development and why we will more than likely look to support Firefox first and other browsers second.

While Opera can be a bit of a memory hog when run in standard mode, the browser down right destroys anything available off the shelf especially in the case of accessibility. What I mean by off the shelf is that no plugins are needed. The problem with Opera is that they are hardliners when it comes to web standards. If you take short cuts when designing your Web content, you run the risk of it not appearing as you think it should. This approach has both helped and hurt Opera's development. Sticking to the standards has allowed the browser to develop features that other browsers are just not making available but forced incompabilities with certain web content. As of late though, Opera has become the dominant browser on mobile, embedded, gaming and other devices. It is slowly but forcibly staking its claim on the desktop environment. Following the milestones Opera is now starting to be more lenient with web content which will help its march forward immensely. What really interests me in Opera for this project is its Java support, Accessibility features, and the capability to run in Kiosk mode.

And, it does not hurt at all that Opera is basically being bank rolled by Google :)

Links:
http://www.opera.com/products/desktop/access/
http://www.webaim.org/resources/opera/
http://www.cew.wisc.edu/accessibility/evaluation/manualchecksopera.htm

Always a little behind but still a good reference as to the state of things -> http://en.wikipedia.org/wiki/Comparison_of_web_browsers

Browser Comparisons by Nate AveryheartNate Averyheart, 22 Mar 2008 18:13

My issue with Firefox is its poor Java and Javascript support. They actually have their own JVM plugin that is less than stellar. I have been pretty dissapointed with Mozilla for a while now. This could change with the release of the next major version and or could possibly be circumvented altogether by writing a Jfx or Java Webstart (jnlp) application which would be capable of running both in the browser or on the customized desktop as an application. I realize that third party plugins have support for a large number of features but out of the box I have never been impressed with what this browser can do.

Another place to search, not meaning to self promote, is the open source online community http://swik.net
Searches on linux accessibility and java accessibility do yield some good results.

I will start seperate Java API and Linux package pages to become a growing resource/reference for us.

Let me first state my assumption, to make sure I'm understanding the proposed design correctly. Contents are organized as if they are in a list view with multiple columns and multiple rows. Each content segment/module (I'm hedging because I'm not sure what is the unit of navigation) is represented by one row. Each "attribute" of the segment/module is represented by one column, with column A being months, column B being days and so on, as described in the design.

My first question is regarding putting these "attributes" into a column. This means that if I want to select contents from a different month, then I will first click the right button to go to the next month, and then presses up and down to navigate all segments/modules within that month. I am not sure whether using left-right to go from one attribute to another makes sense to me. Left-right will be the most commonly used nav buttons on the device, and it seems to me that it should map to the most simple concept in terms of navigation, reserving the up-down for more advanced concept such as going from by-month navigation, to by-day, etc. In other words, I'm wondering if transposing the table representation is easier for the user to understand? I don't know the answer, but field usability testing should tell us a lot.

My second question, more of an assertion, is that for most users they should have a way to navigate simply without having to understand the two-dimensional table proposed. Assuming the typical users are illiterate and may not even have the concept of a table, this up-down-left-right business may be challenging. My daughter is in second grade, studying basically third grade math, and I think she just covered tables and rows and columns earlier this year. Perhaps there's just a column which is the date-time stamp column, and you can just go up-down to nav between ALL the segment/modules, without knowing that you can also switches abstraction and get to the desired segment/module quicker by navigating by another mean.

Left-Right vs. Up-Down by wlaiwlai, 21 Mar 2008 23:04

Hey - doesn't Cliff need a day to relax when in Ghana?

testing this comment thing by cliffscliffs, 15 Mar 2008 09:29