Specification BetterDefaults GraphicsFontsSettings

Specification Status
Author	Christoph Lukasiak (Clu)
Last Change	8. December 2010
Status (Help)	Preliminary

Abstract

"Better Defaults", as this effort is called for short, aims to collect suggestions for better default settings in OOo. Impress was first (in accordance with the present focus of project Renaissance) . This is a subproject of Project Renaissance and 'Gridhandling' is the first outcome of it. Now also the second part 'Bullets/Colors/Shortcuts' is added.

References

Reference Document	Check	Location (URL)
Prerequisites	[passed/failed]	n/a
Product Requirement, RFE, Issue ID (required)	available	gfs: ixxxxxx,iyyyyyy all issue query
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	Graphics Fonts Settings 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
Renaissance i-Team		Renaissance i-Team

Acronyms and Abbreviations

Acronym / Abbreviation	Definition
<WYSIWYG>	<What You See Is What You Get>

Detailed Specification

Graphics d&d from application:

done (fixed in between)

Paste pics from web:

if you d&d a pic from web you get an HTML code instead of the pic
# pasting from web pics from URL (Insert > Picture > From file> URL) causes "Unknow graphics format" error
# url placeholder look really ugly and trashes the view:

Accessibility

Accessibility is the responsibility of the I-Team, beginning with UX, DEV and QA, to ensure that the following requirements are fulfilled:

1. Is the feature fully keyboard accessible?
   (Ex: "I can go everywhere and use every function using the keyboard only"
   <START TYPING HERE>
2. Have I specified visual alternatives for the case that the specified feature includes audio as output?
   <START TYPING HERE>
3. Are text alternatives for all icons and graphics available?
   <Start typing here>
4. Don't provide important information in colors alone
   (Ex: marking important information hard coded in red)
   <START TYPING HERE>
5. Does the specified feature respect system settings for font, size, and color for all windows and user interface elements?
   <START TYPING HERE>
6. 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>
7. 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:

1. The accessibility check list at the OpenOffice.org Wiki
2. accessibility@ui.openoffice.org (The accessibility mailing lists, preferred)
3. For specific implementation details, architecture: mt@openoffice.org (Malte Timmermann)
4. For specific UX and testing questions: es@openoffice.org (Éric Savary)

Migration

The Gridhandling default changes belongs to Impress and Draw application.

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>Link title