CommonATConfig

Differences between revisions 19 and 20
Revision 19 as of 2006-11-29 04:17:47
Size: 3817
Editor: 121-72-132-184
Comment: much better design
Revision 20 as of 2006-11-29 15:07:23
Size: 3969
Editor: 82-69-40-219
Comment: typos; reply to comment
Deletions are marked like this. Additions are marked like this.
Line 30: Line 30:
 * From the AT-prefs page link to Keyboard, Mouse, Fonts and Themes settings and to the new Preffered Applications tab  * From the AT-prefs page link to Keyboard, Mouse, Fonts and Themes settings and to the new Preferred Applications tab
Line 42: Line 42:
 * Add link buttons the at-prefs dialog.  * Add link buttons to the at-prefs dialog.
Line 50: Line 50:
  * Non-blocking password prompts should only be enabled if you need input assistance; they should not be enabled if you only need a screen reader.

Summary

Clarify the assistive technology settings in gnome. Identify where each options belongs, whether it is a general desktop setting with accessibility implications (such as font size) or a specialised assistive technology feature. Restructure the items to make navigating the options intuitive for groups with different perspectives.

Rationale

The assistive technology (AT) settings in gnome are currently spread out over several locations, making the features difficult to find. Several new assistive technology applications are currently appearing like Orca, onBoard and LSR, some of which have overlapping features. It is important to present the option to the user in a clear way.

Use cases

  • Gustav has slightly reduced vision so he likes to increase the font size on his system and select a suitable icon set. It would not occur to him to look for these items under 'Assistive Technology', but expects to find it with the fonts and theme settings.
  • Joanna has less vision than Gustav and uses a high contrast theme with large fonts and occasionally a magnifier. She knows she needs these features to use the computer. When a friends shows here Ubuntu she asks him to open the accessibility settings to look for them. They are pleased to finds all these features available in one place.

Scope

Upstream Gnome is currently redesigning the AT-preferences window by moving the AT-applications selection to 'Preferred Applications' and making it more general so that users can select from different ATs (assistive technologies) to start by default with Gnome. The individual AT tools will continue to have their separate configuration dialogs, linked to from the AT preferences (as is currently done with Orca and onBoard in Ubuntu).

In addition, we will introduce link buttons to common user settings related to accessibility.

Design

  • [:Accessibility/Projects/GnomeATconf:Chart] the existing accessibility settings (and related settings).

    • Divide the setting into better categories, taking special note of which can be considered general desktop settings and which are pure a11y items.
    • Result: The current divisions are generally suitable, better links should be made.
  • From the AT-prefs page link to Keyboard, Mouse, Fonts and Themes settings and to the new Preferred Applications tab
  • Link back to accessibility from the Mouse dialog

attachment:at-prefs-no-tabs.png BRBR

Caption: Proposed Assistive Technology Preferences layout, with launch buttons for related gnome settings.

Implementation

Unresolved issues

  • Upstream is discussing implementing a configuration option for the ATs to be started by default (see [http://bugzilla.gnome.org/show_bug.cgi?id=350263 bug 350263]) and improving the theme dialog to reduce the number of (rather similar) a11y themes. Upstream choices should be tracked here.

  • This is a big improvement on the previous design, but "Enable assistive technology infrastructure" and "Use non-blocking password prompts" still don't mean anything. These probably should be turned on automatically whenever you're using a screenreader or other accessibility tool, rather than being options in themselves. -- MatthewPaulThomas

    • Non-blocking password prompts should only be enabled if you need input assistance; they should not be enabled if you only need a screen reader.


CategorySpec

Accessibility/Specs/CommonATConfig (last edited 2008-08-06 16:39:48 by localhost)