Specification BetterDefaults Gridhandling
Specification Status | |
Author | Christoph Lukasiak (Clu) |
Last Change | 31. May 2010 |
Status (Help) | Preliminary |
Abstract
<START TYPING HERE>Contents
References
Reference Document | Check | Location (URL) |
Prerequisites | [passed/failed] | n/a |
Product Requirement, RFE, Issue ID (required) | [available/not available] | <PLEASE ENTER LOCATION HERE> |
Accessibility Check (required) | See accessibility section for check list | |
Test case specification (required) | [available/not available] | <PLEASE ENTER LOCATION HERE> |
IDL Specification | [available/not available] | <PLEASE ENTER LOCATION HERE> |
Software Specification Rules | n/a | n/a |
Better Defaults: Gridhandling Suggestion list | available | Gridhandling Workout |
Better Defaults: OOo Suggestion list | available | Improving OOo Default Settings |
Project Renaissance | available | Thinning out |
Contacts
Role | Name | E-Mail Address |
Developer | Christian Lippka | Christian.Lippka@sun.com |
Quality Assurance | Wolfram Garten | Wolfram.Garten@sun.com |
Documentation | Uwe Fischer | Uwe.Fischer@sun.com |
User Experience | Christoph Lukasiak | Christoph.Lukasiak@sun.com |
Elizabeth Matthis | Elizabeth.Matthis@sun.COM |
Acronyms and Abbreviations
Acronym / Abbreviation | Definition |
<WYSIWYG> | <What You See Is What You Get> |
Detailed Specification
Snap to Guides: 'off' by default => should be 'on' by default
Snap to Object Border: 'off' by default => should be 'on' by default
Large Handles: 'off' by default => should be 'on' by default
Allow Quick Editing: 'on' by default => should be 'off' by default
(!attention: in the layouts you have currently following text in textboxes 'click to add title' -> must be changed in 'doubleclick')
Rotation Mode: 'off' by default => should be 'on' by default
- Change rotate button (drawing toolbar) in rotate mode button (on/off)
- Fit rotation point to every selected object
More fine Grid:
Accessibility
Accessibility is the responsibility of the I-Team, beginning with UX, DEV and QA, to ensure that the following requirements are fulfilled:
- Is the feature fully keyboard accessible?
(Ex: "I can go everywhere and use every function using the keyboard only"
<START TYPING HERE> - Have I specified visual alternatives for the case that the specified feature includes audio as output?
<START TYPING HERE> - Are text alternatives for all icons and graphics available?
<Start typing here> - Don't provide important information in colors alone
(Ex: marking important information hard coded in red)
<START TYPING HERE> - Does the specified feature respect system settings for font, size, and color for all windows and user interface elements?
<START TYPING HERE> - Have I ensured that flash rates do not exceed 2 hertz for blinking text, objects, or other elements? In any case, try to avoid flashing UI elements
<START TYPING HERE> - Ensure that assistive technology (AT) (like ZoomText or Orca) is able to read everything.
<START TYPING HERE>
QUESTIONS?
If you need help while designing, implementing or testing the accessibility of the UI, ask/visit:
- The accessibility check list at the OpenOffice.org Wiki
- accessibility@ui.openoffice.org (The accessibility mailing lists, preferred)
- For specific implementation details, architecture: mt@openoffice.org (Malte Timmermann)
- For specific UX and testing questions: es@openoffice.org (Éric Savary)
Migration
<START TYPING HERE --- If this part is irrelevant state a reason for its absence.>
Configuration
<START TYPING HERE --- If this part is irrelevant state a reason for its absence.>
Help | Configuration Table Template
File Format
<START TYPING HERE --- If this part is irrelevant state a reason for its absence.> Help
Help | File Format Table Template
Open Issues
<State a bulleted list of issues Issue here>