Usability : the default metacity theme must be accessible.

Bug #19549 reported by Lionel Dricot on 2005-08-09
Affects Status Importance Assigned to Milestone
Mantas Kriaučiūnas
human-theme (Ubuntu)
Ubuntu Artwork Team

Bug Description

The current default metacity theme has two big flaws regarding accessibility :

- buttons are too thin
- you must have really good eyes to catch difference between buttons.

I suggest that the default theme is turned into something like this :

1) Buttons are wide ! So even people with disabilities can click. At the
moment, closing a window is, for a few people, like aiming and pray. (it's
really difficult to point the mouse on a so little place and click, without
moving the mouse. We, computer geeks, forget often how difficult it is)

2) Buttons have different colors. No need to have good eyes to guess what the
little picture is. It's also far easier to help someone on the phone : "Click on
the red button" instead of "Do you see the cross ? There's a cross in a box.
That's the button ! Click on it".

3) also, another idea would be to place all "window operation" buttons on one
side and the "close this window" on the other side. So you don't close
accidentaly the window. ( example : ).

The related ubuntuforums thread :

Created an attachment (id=3194)
A suggestion about the metacity default theme

This is just to have an idea.

Created an attachment (id=3195)
Buttons order suggestion

Just to make sure this is not forgotten...

I am totally with Lionel on this one. Just to clear things out a 100%, we are
talking about the Pilgrim theme, which can be found here: .

I've been using it for about a month now and I still enjoy it.

Window manager usability: the default metacity theme must be accessible and have more space between buttons - now people can accidently click on a wrong button, because buttons (minimize, maximize, close) are too close to each other.

Daniel Robitaille (robitaille) wrote :

The current human theme in Dapper seems to be a good step in the direction of solving this bug report. It has wider buttons than the version in Breezy. But they are all the same colour still.

I agree that the current theme is way better. Maybe slightly change the color of the close button would be enough ?

Bug #8100 is related too.

Alexandre Otto Strube (surak) wrote :

Is malone the correct place for discuss acessibility issues? The bug #8100 is a duplicate from this, or heavily related. Perhaps a discussion on the correct place (a mailing list) would be more fruitful than this.

Daniel Holbach (dholbach) wrote :

This should be reevaluated for Feisty.

Changed in ubuntu-artwork:
assignee: jdub → ubuntu-art

The bug reporting issue regarding design is getting a tad silly.

We have no target audience for the design -- which is ultimately the problem. The aesthetic, whatever it ends up being, _will_ not and _can_ not please everyone.

Also, permitting "bug" reports to be filed against any aspect is truly the path of folly. Most of the "bugs" should be marked "by design" by our lead designer. Of course, our lead designer is sabdfl and he is probably too busy.

It is completely impossible to even _consider_ 98% of these bugs.

Accessibility should be very high on Ubuntu's list, but it is similar to language. We need _SPECIFIC_ design patterns for _SPECIFIC_ accessibility issues, and provide a look / feel for each.

Changed in human-gtk-theme:
status: Unconfirmed → Confirmed

Can we close this?

Specific sets of disabilities require very specific and real design features. It is simply impossible to address specific sets of disabilities with a single theme.

PS: We should probably establish a 'target audience' for the default Human look at some point to address these sorts of complaints.

Daniel Holbach (dholbach) wrote :

Henrik and the Accessibility team: what do you think about addressing the bug in the accessibility themes or a new theme?

Vish (vish) wrote :

Closing this bug as the human theme is no longer the default theme.

Changed in human-theme (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.