This page has been relocated to the new instance of the Sahana Wiki. Please reference it here. Thank you.

Guidelines and Checklist Documentation

The original Guidelines and Checklist documentation can be found here: guidelines_and_checklist.doc


Objective is to check for all the links in the website.

  1. All Internal Links
  2. All External Links
  3. All mail to links
  4. Check for orphan Pages
  5. Check for Broken Links


Test for the integrity of submission of all forms.

  1. All Field Level Checks
  2. All Field Level Validations.
  3. Functionality of Create, Modify, Delete & View.
  4. Handling of Wrong inputs (Both client & Server)
  5. Default Values if any
  6. Optional versus Mandatory fields.


Check for the cookies that have to be enabled and their expiration conditions.

Web Indexing

Depending on how the site is designed using Meta tags, frames, HTML syntax, dynamically created pages, passwords or different languages, our site will be searchable in different ways.

  1. Meta Tags
  2. Frames
  3. HTML syntax.


Two types of errors that may occur in Web applications:
Data Integrity:
Missing or wrong data in table.

Output Error:
Errors in writing, editing or reading operations in the tables.

The issue is to test the functionality of the database, not the content and the focus here is therefore on output errors. Verify that queries, writing, retrieving or editing in the database is performed in a correct way.


Navigation describes the way users navigate within a page, between different user interface controls (buttons, boxes, lists, windows etc.), or between pages via e.g. links.

  1. Application navigation is proper through tab
  2. Navigation through Mouse
  3. Main features accessible from the main/home page.
  4. Any hot keys, control keys to access menus.


Correctness is whether the information is truthful or contains misinformation. The accuracy of the information is whether it is without grammatical or spelling errors. Remove irrelevant information from your site. This may otherwise cause misunderstandings or confusion.

  1. Spellings and Grammars
  2. Updated information

General Appearance

  1. Page appearance
  2. Color, font and size
  3. Frames
  4. Consistent design

Server Side Interfaces

Server Interface

  1. Verify that communication is done correctly, Web server-application server, application server-database server and vice versa.
  2. Compatibility of server software, hardware, network connections.
  3. Database compatibility (SQL, Oracle etc.)

External Interface

Check to ensure external interface compatiability if any are present within the system.

Client Side Compatibility


Check for the compatibility of

  • Windows (95, 98, 2000, NT)
  • Unix (different sets)
  • Macintosh (If applicable)
  • Linux
  • Solaris (If applicable)


Check for the various combinations:

  • Internet Explorer (3.X 4.X, 5.X)
  • Netscape Navigator (3.X, 4.X, 6.X)
  • AOL
  • Browser settings (security settings, graphics, Java etc.)
  • Frames and Cascade Style sheets
  • Applets, ActiveX controls, DHTML, client side scripting
  • HTML specifications.


Ensure that graphics, images, and other media items which are used are present and in working order.


Despite the paperless society the web was to introduce, printing is done more than ever. Verify that pages are printable with considerations on:

  • Text and image alignment
  • Colours of text, foreground and background
  • Scalability to fit paper size
  • Tables and borders


Connection speed

  • Try with Connection speed: 14.4, 28.8, 33.6, 56.6, ISDN, cable, DSL, T1, T3
  • Time*out


Check/Measure the following:

  • What is the estimated number of users per time period and how will it be divided over the period?
  • Will there be peak loads and how will the system react?
  • Can your site handle a large amount of users requesting a certain page?
  • Large amount of data from users.


Stress testing is done in order to actually break a site or a certain feature to determine how the system reacts. Stress tests are designed to push and test system limitations and determine whether the system recovers gracefully from crashes. Hackers often stress systems by providing loads of wrong in*data until it crash and then gain access to it during start*up.

  • Typical areas to test are forms, logins or other information transaction components.
  • Performance of memory, CPU, file handling etc.
  • Error in software, hardware, memory errors (leakage, overwrite or pointers)

Continuous Use

  • Is the application or certain features going to be used only during certain periods of time or will it be used continuously 24 hours a day 7 days a week?
  • Will downtime be allowed or is that out of the question?
  • Verify that the application is able to meet the requirements and does not run out of memory or disk space.


  • Valid and Invalid Login
  • Limit defined for the number of tries.
  • Can it be bypassed by typing URL to a page inside directly in the browser?
  • Verify Log files are maintained to store the information for traceability.
  • Verify encryption is done correctly if SSL is used (If applicable)
  • No access to edit scripts on the server without authorization.

Before Hosting a Website

Checklist before hosting a website:



  • Internal Links - Should be present
  • External Links - Should be present
  • MailTo Links - Should open mailbox
  • Orphan Pages - Should not be present
  • Broken Links - Should not be present


  • Field Level Checks - Checked for length, special characters, numerical characters etc.,
  • Field Level Validation - Checked Unique records, Date validation
  • Functional Checks - Create, modify, view and delete are working.
  • Error Handling - For incorrect inputs or actions appropriate error messages to be displayed.
  • Optional and Mandatory Fields - Mandatory field should not be left blank.
  • Optional should allow the user to skip the field.

Check whether cookies are enabled.
Depends on project

Web Indexing

  • Meta tags - Should be present.
  • Html Syntax - Should be valid
  • Frames - To be found by indexing agents appropriately.


  • Data Integrity - Should not be any missing or incorrect data in the database
  • Output Errors - Errors in writing, reading or editing operations should not be present



  • Navigation through Mouse - Should be proper
  • Navigation through Tab - Should be proper
  • Main features access - Should be accessed from home/Main page
  • Hot Keys, Control Keys for Menu or Action - Should be present


  • Spelling and Grammar - To be proper
  • Updated information's. - Past events/ information's to be removed.

General Appearance

  • Page Appearance - Should not be any overlapping, missing etc.,
  • Colour, font and size - Should be as per standard
  • Frames - All frames to be visible
  • Consistent Design - Everywhere in the website consistent layout and design should be carried out.

Server Side Interface

Server Interface

  • Communications - Should be correct with respect to Web server, App server and DB server
  • Compatibility with server hardware, SW, network connections - Should be proper.
  • Database - Should be easily portable to other database.

Client side Compatibility


  • Windows 2000, NT - Should be functioning properly.
  • Unix - Should be functioning properly.
  • Linux - Should be functioning properly.
  • Solaris - Should be functioning properly.
  • Macintosh - Should be functioning properly.


  • I.E - Should work in all versions above 4.x
  • Netscape Navigator - Should work in all versions above 3.x
  • AOL
  • Any ActiveX controls
  • Graphics - Loading of images, graphics should be proper


  • Text and alignment - Should be proper
  • Colours of text, foreground and background - Should be readable.
  • Scalability to fit paper size. - Should print in A4, Letter size.
  • Tables and borders. - Should be proper.


Connection Speed

  • Should be measured in 14.4, 28.8, 33.6, 56.6, ISDN, Cable and DSL
  • Timeout Should give appropriate time to search. Incorrect message, data loss should not be present.


  • Estimated users. - Per requirements
  • Peak load - Should withstand
  • Large amount of data from users - Should accept


  • System Crash - Should not be present
  • Error in Sw, HW, Memory Leakage, overwrite should not happen.

Continuous Use

  • Estimate whether available for 24 Hrs, 7 days a week - Try with various timings.
  • Downtime - Measure the downtime
  • Memory or disk space - Should not run out of memory or disk space.


Valid and Invalid

  • Login - Should not enter with Invalid login
  • Number of Tries - Should not be more than 3 times for invalid try.
  • Direct URLs - Entering url directly without logging in should not display information.
  • Log files - Should be maintained

Golden Rules of Interface Design

You Should Use the Eight Golden Rules of Interface Design:

Strive for Consistency

  • consistent sequences of actions should be required in similar situations
  • identical terminology should be used in prompts, menus, and help screens
  • consistent color, layout, capitalization, fonts, and so on should be employed


Enable Frequent Users to Use Shortcuts

  • to increase the pace of interaction use abbreviations, special keys, hidden

commands, and macros

Offer Informative Feedback

  • for every user action, the system should respond in some way (in web design, this

can be accomplished by DHTML - for example, a button will make a clicking sound or change color when clicked to show the user something has happened)

Design Dialogs To Yield Closure

  • Sequences of actions should be organized into groups with a beginning, middle,

and end. The informative feedback at the completion of a group of actions shows the user their activity has completed successfully

Offer Error Prevention And Simple Error Handling

  • design the form so that users cannot make a serious error; for example, prefer

menu selection to form fill-in and do not allow alphabetic characters in numeric entry fields

  • if users make an error, instructions should be written to detect the error and offer

simple, constructive, and specific instructions for recovery

  • segment long forms and send sections separately so that the user is not penalized

by having to fill the form in again - but make sure you inform the user that multiple sections are coming up

Permit Easy Reversal Of Actions
A user should be able to easily and effectively reverse their actions made within the interface.

Support Internal Locus Of Control

  • Experienced users want to be in charge. Surprising system actions, tedious

sequences of data entries, inability or difficulty in obtaining necessary information, and inability to produce the action desired all build anxiety and dissatisfaction

Reduce Short-Term Memory Load

  • A famous study suggests that humans can store only 7 (plus or minus 2) pieces of

information in their short term memory. You can reduce short term memory load by designing screens where options are clearly visible, or using pull-down menus and icons

Prevent Errors

  • The third principle is to prevent errors whenever possible. Steps can be taken to design so that errors are less likely to occur, using methods such as organizing screens and menus functionally, designing screens to be distinctive and making it difficult for users to commit irreversible actions. Expect users to make errors, try to anticipate where they will go wrong and design with those actions in mind.

Windows Compliance Testing


For Each Application:

Start Application by Double Clicking on its ICON The Loading message should show the application name, version number, and a bigger pictorial representation of the icon.

No Login is necessary

The main window of the application should have the same caption as the caption of the icon in Program Manager.

Closing the application should result in an “Are you Sure” message box

Attempt to start application Twice This should not be allowed - you should be returned to main Window

Try to start the application twice as it is loading.

On each window, if the application is busy, then the hour glass should be displayed. If there is no hour glass (e.g. alpha access enquiries) then some enquiry in progress message should be displayed.

All screens should have a Help button, F1 should work doing the same.

For Each Window in the Application
If Window has a minimize Button, click it.

Window Should return to an icon on the bottom of the screen This icon should correspond to the Original Icon under Program Manager.

Double Click the Icon to return the Window to its original size.

The window caption for every application should have the name of the application and the window name - especially the error messages. These should be checked for spelling, English and clarity, especially on the top of the screen. Check does the title of the window makes sense.

If the screen has an Control menu, then use all ungreyed options.

Check all text on window for Spelling/Tense and Grammar

Use TAB to move focus around the Window. Use SHIFT+TAB to move focus backwards.

Tab order should be left to right, and Up to Down within a group box on the screen. All controls should get focus - indicated by dotted box, or cursor. Tabbing to an entry field with text in it should highlight the entire text in the field.

The text in the Micro Help line should change - Check for spelling, clarity and non-updateable etc.

If a field is disabled (greyed) then it should not get focus. It should not be possible to select them with either the mouse or by using TAB. Try this for every greyed control.

Never updateable fields should be displayed with black text on a grey background with a black label.

All text should be left-justified, followed by a colon tight to it.

In a field that may or may not be updateable, the label text and contents changes from black to grey depending on the current status.

List boxes are always white background with black text whether they are disabled or not. All others are grey.

In general, do not use goto screens, use gosub, i.e. if a button causes another screen to be displayed, the screen should not hide the first screen, with the exception of tab in 2.0

When returning return to the first screen cleanly i.e. no other screens/applications should appear.

In general, double-clicking is not essential. In general, everything can be done using both the mouse and the keyboard.

All tab buttons should have a distinct letter.

Application Objects

Text Boxes

Original image and more information at:

Move the Mouse Cursor over all Enterable Text Boxes. Cursor should change from arrow to Insert Bar. If it doesn't then the text in the box should be grey or non-updateable. Refer to previous page.

Enter text into Box

Try to overflow the text by typing to many characters - should be stopped Check the field width with capitals W.

Enter invalid characters - Letters in amount fields, try strange characters like +, - - etc. in All fields.

SHIFT and Arrow should Select Characters. Selection should also be possible with mouse. Double Click should select all text in box.

Option (Radio Buttons)

Original image and more information at:

Left and Right arrows should move 'ON' Selection. So should Up and Down.. Select with mouse by clicking.

Check Boxes

Original image and more information at:

Clicking with the mouse on the box, or on the text should SET/UNSET the box. SPACE should do the same

Command Buttons

Original image and more information at:

If Command Button leads to another Screen, and if the user can enter or change details on the other screen then the Text on the button should be followed by three dots.

All Buttons except for OK and Cancel should have a letter Access to them. This is indicated by a letter underlined in the button text. The button should be activated by pressing ALT+Letter. Make sure there is no duplication.

Click each button once with the mouse - This should activate Tab to each button - Press SPACE - This should activate Tab to each button - Press RETURN - This should activate The above are VERY IMPORTANT, and should be done for EVERY command Button.

Tab to another type of control (not a command button). One button on the screen should be default (indicated by a thick black border). Pressing Return in ANY no command button control should activate it.

If there is a Cancel Button on the screen, then pressing <Esc> should activate it. If pressing the Command button results in uncorrectable data e.g. closing an action step, there should be a message phrased positively with Yes/No answers where Yes results in the completion of the action.

Drop Down List Boxes

Original image and more information at:

Pressing the Arrow should give list of options. This List may be scrollable. You should not be able to type text in the box.

Pressing a letter should bring you to the first item in the list with that start with that letter. Pressing ‘Ctrl - F4' should open/drop down the list box.

Spacing should be compatible with the existing windows spacing (word etc.). Items should be in alphabetical order with the exception of blank/none which is at the top or the bottom of the list box.

Drop down with the item selected should be display the list with the selected item on the top.

Make sure only one space appears, shouldn't have a blank line at the bottom.

Combo Boxes

Original image and more information at:

Should allow text to be entered. Clicking Arrow should allow user to choose from list

List Boxes

Original image and more information at:

Should allow a single selection to be chosen, by clicking with the mouse, or using the Up and Down Arrow keys.

Pressing a letter should take you to the first item in the list starting with that letter.

If there is a 'View' or 'Open' button beside the list box then double clicking on a line in the List Box, should act in the same way as selecting and item in the list box, then clicking the command button.

Force the scroll bar to appear, make sure all the data can be seen in the box.

Screen Validation Checklist

Aesthetic Conditions

  1. Is the general screen background the correct colour?.
  2. Are the field prompts the correct colour?
  3. Are the field backgrounds the correct colour?
  4. In read-only mode, are the field prompts the correct colour?
  5. In read-only mode, are the field backgrounds the correct colour?
  6. Are all the screen prompts specified in the correct screen font?
  7. Is the text in all fields specified in the correct screen font?
  8. Are all the field prompts aligned perfectly on the screen?
  9. Are all the field edit boxes aligned perfectly on the screen?
  10. Are all groupboxes aligned correctly on the screen?
  11. Should the screen be resizable?
  12. Should the screen be minimisable?
  13. Are all the field prompts spelt correctly?
  14. Are all character or alpha-numeric fields left justified? This is the default unless otherwise specified.
  15. Are all numeric fields right justified? This is the default unless otherwise specified.
  16. Is all the microhelp text spelt correctly on this screen?
  17. Is all the error message text spelt correctly on this screen?
  18. Is all user input captured in UPPER case or lower case consistently?
  19. Where the database requires a value (other than null) then this should be defaulted into fields. The user must either enter an alternative valid value or leave the default value intact.
  20. Assure that all windows have a consistent look and feel.
  21. Assure that all dialog boxes have a consistent look and feel.

Validation Conditions

  1. Does a failure of validation on every field cause a sensible user errormessage?
  2. Is the user required to fix entries which have failed validation tests?
  3. Have any fields got multiple validation rules and if so are all rules being applied?
  4. If the user enters an invalid value and clicks on the OK button (i.e. does not TAB off the field) is the invalid entry identified and highlighted correctly with an error message.?
  5. Is validation consistently applied at screen level unless specifically required at field level?
  6. For all numeric fields check whether negative numbers can and should be able to be entered.
  7. For all numeric fields check the minimum and maximum values and also some mid-range values allowable?
  8. For all character/alphanumeric fields check the field to ensure that there is a character limit specified and that this limit is exactly correct for the specified database size?
  9. Do all mandatory fields require user input?
  10. If any of the database columns don't allow null values then the corresponding screen fields must be mandatory. (If any field which initially was mandatory has become optional then check whether null values are allowed in this field.)

Navigation Conditions

  1. Can the screen be accessed correctly from the menu?
  2. Can the screen be accessed correctly from the toolbar?
  3. Can the screen be accessed correctly by double clicking on a list control on the previous screen?
  4. Can all screens accessible via buttons on this screen be accessed correctly?
  5. Can all screens accessible by double clicking on a list control be accessed correctly?
  6. Is the screen modal. i.e. Is the user prevented from accessing other functions when this screen is active and is this correct?
  7. Can a number of instances of this screen be opened at the same time and is this correct?

Usability Conditions

  1. Are all the dropdowns on this screen sorted correctly? Alphabetic sorting is the default unless otherwise specified.
  2. Is all date entry required in the correct format?
  3. Have all pushbuttons on the screen been given appropriate Shortcut keys?
  4. Do the Shortcut keys work correctly?
  5. Have the menu options which apply to your screen got fast keys associated and should they have?
  6. Does the Tab Order specified on the screen go in sequence from Top Left to bottom right? This is the default unless otherwise specified.
  7. Are all read-only fields avoided in the TAB sequence?
  8. Are all disabled fields avoided in the TAB sequence?
  9. Can the cursor be placed in the microhelp text box by clicking on the text box with the mouse?
  10. Can the cursor be placed in read-only fields by clicking in the field with the mouse?
  11. Is the cursor positioned in the first input field or control when the screen is opened?
  12. Is there a default button specified on the screen?
  13. Does the default button work correctly?
  14. When an error message occurs does the focus return to the field in error when the user cancels it?
  15. When the user Alt+Tab's to another application does this have any impact on the screen upon return to The application?
  16. Do all the fields edit boxes indicate the number of characters they will hold by there length? e.g. a 30 character field should be a lot longer

Data Integrity Conditions

  1. Is the data saved when the window is closed by double clicking on the close box?
  2. Check the maximum field lengths to ensure that there are no truncated characters?
  3. Where the database requires a value (other than null) then this should be defaulted into fields. The user must either enter an alternative valid value or leave the default value intact.
  4. Check maximum and minimum field values for numeric fields?
  5. If numeric fields accept negative values can these be stored correctly on the database and does it make sense for the field to accept negative numbers?
  6. If a set of radio buttons represent a fixed set of values such as A, B and C then what happens if a blank value is retrieved from the database? (In some situations rows can be created on the database by other functions which are not screen based and thus the required initial values can be incorrect.)
  7. If a particular set of data is saved to the database check that each value gets saved fully to the database. i.e. Beware of truncation (of strings) and rounding of numeric values.

Modes (Editable Read-Only) Conditions

  1. Are the screen and field colours adjusted correctly for read-only mode?
  2. Should a read-only mode be provided for this screen?
  3. Are all fields and controls disabled in read-only mode?
  4. Can the screen be accessed from the previous screen/menu/toolbar in read-only mode?
  5. Can all screens available from this screen be accessed in read-only mode?
  6. Check that no validation is performed in read-only mode.

General Conditions:

  1. Assure the existence of the “Help” menu.
  2. Assure that the proper commands and options are in each menu.
  3. Assure that all buttons on all tool bars have a corresponding key commands.
  4. Assure that each menu command has an alternative(hot-key) key sequence which will invoke it where appropriate.
  5. In drop down list boxes, ensure that the names are not abbreviations / cut short
  6. In drop down list boxes, assure that the list and each entry in the list can be accessed via appropriate key / hot key combinations.
  7. Ensure that duplicate hot keys do not exist on each screen
  8. Ensure the proper usage of the escape key (which is to undo any changes that have been made) and generates a caution message “Changes will be lost - Continue yes/no”
  9. Assure that the cancel button functions the same as the escape key.
  10. Assure that the Cancel button operates as a Close button when changes have be made that cannot be undone.
  11. Assure that only command buttons which are used by a particular window, or in a particular dialog box, are present. - i.e make sure they don't work on the screen behind the current screen.
  12. When a command button is used sometimes and not at other times, assure that it is grayed out when it should not be used.
  13. Assure that OK and Cancel buttons are grouped separately from other command buttons.
  14. Assure that command button names are not abbreviations.
  15. Assure that all field labels/names are not technical labels, but rather are names meaningful to system users.
  16. Assure that command buttons are all of similar size and shape, and same font & font size.
  17. Assure that each command button can be accessed via a hot key combination.
  18. Assure that command buttons in the same window/dialog box do not have duplicate hot keys.
  19. Assure that each window/dialog box has a clearly marked default value (command button, or other object) which is invoked when the Enter key is pressed - and NOT the Cancel or Close button
  20. Assure that focus is set to an object/button which makes sense according to the function of the window/dialog box.
  21. Assure that all option buttons (and radio buttons) names are not abbreviations.
  22. Assure that option button names are not technical labels, but rather are names meaningful to system users.
  23. If hot keys are used to access option buttons, assure that duplicate hot keys do not exist in the same window/dialog box.
  24. Assure that option box names are not abbreviations.
  25. Assure that option boxes, option buttons, and command buttons are logically grouped together in clearly demarcated areas “Group Box”
  26. Assure that the Tab key sequence which traverses the screens does so in a logical way.
  27. Assure consistency of mouse actions across windows.
  28. Assure that the color red is not used to highlight active objects (many individuals are red-green color blind).
  29. Assure that the user will have control of the desktop with respect to general color and highlighting (the application should not dictate the desktop background characteristics).
  30. Assure that the screen/window does not have a cluttered appearance
  31. Ctrl + F6 opens next tab within tabbed window
  32. Shift + Ctrl + F6 opens previous tab within tabbed window
  33. Tabbing will open next tab within tabbed window if on last field of current tab
  34. Tabbing will go onto the 'Continue' button if on last field of last tab within tabbed window
  35. Tabbing will go onto the next editable field in the window
  36. Banner style & size & display exact same as existing windows
  37. If 8 or less options in a list box, display all options on open of list box - should be no need to scroll
  38. Errors on continue will cause user to be returned to the tab and the focus should be on the field causing the error. (i.e the tab is opened, highlighting the field with the error on it)
  39. Pressing continue while on the first tab of a tabbed window (assuming all fields filled correctly) will not open all the tabs.
  40. On open of tab focus will be on first editable field
  41. All fonts to be the same
  42. Alt+F4 will close the tabbed window and return you to main screen or previous screen (as appropriate), generating “changes will be lost” message if necessary.
  43. Microhelp text for every enabled field & button
  44. Ensure all fields are disabled in read-only mode
  45. Progress messages on load of tabbed screens
  46. Return operates continue
  47. If retrieve on load of tabbed window fails window should not open

Specific Field Tests

Date Field Checks

  • Assure that leap years are validated correctly & do not cause errors/miscalculations
  • Assure that month code 00 and 13 are validated correctly & do not cause errors/miscalculations
  • Assure that 00 and 13 are reported as errors
  • Assure that day values 00 and 32 are validated correctly & do not cause errors/miscalculations
  • Assure that Feb. 28, 29, 30 are validated correctly & do not cause errors/miscalculations
  • Assure that Feb. 30 is reported as an error
  • Assure that century change is validated correctly & does not cause errors/miscalculations
  • Assure that out of cycle dates are validated correctly & do not cause errors/miscalculations

Numeric Fields

  • Assure that lowest and highest values are handled correctly
  • Assure that invalid values are logged and reported
  • Assure that valid values are handles by the correct procedure
  • Assure that numeric fields with a blank in position 1 are processed or reported as an error
  • Assure that fields with a blank in the last position are processed or reported as an error an error
  • Assure that both + and - values are correctly processed
  • Assure that division by zero does not occur
  • Include value zero in all calculations
  • Include at least one in-range value
  • Include maximum and minimum range values
  • Include out of range values above the maximum and below the minimum
  • Assure that upper and lower values in ranges are handled correctly

Alpha Field Checks

  • Use blank and non-blank data
  • Include lowest and highest values
  • Include invalid characters & symbols
  • Include valid characters
  • Include data items with first position blank
  • Include data items with last position blank

Validation Testing - Standard Actions

On every Screen:

  1. Add
  2. View
  3. Change
  4. Delete
  5. Continue
  6. Add
  7. View
  8. Change
  9. Delete
  10. Cancel
  11. Fill each field - Valid data
  12. Fill each field - Invalid data
  13. Different Check Box combinations
  14. Scroll Lists
  15. Help
  16. Fill Lists and Scroll
  17. Tab
  18. Tab Order
  19. Shift Tab
  20. Shortcut keys - Alt + F

Shortcut Keys / Hot Keys

Key No Modifier SHIFT CTRL ALT
F1 Help Enter Help Mode N/A N/A
F2 N/A N/A N/A N/A
F3 N/A N/A N/A N/A
F4 N/A N/A Close Document Window Close Application Window
F5 N/A N/A N/A N/A
F6* Move clockwise to next pane of active window Move counterclockwise to next pane of active window Move to next document window; top window moves to bottom of stack (adding SHIFT reverses action : previous window moves to top.) Move to application's next open non-document window (Adding SHIFT reverses order of movement)
F7 N/A N/A N/A N/A
F8 Toogle extend mode, if supported Toggle add mode, if supported N/A N/A
F9 N/A N/A N/A N/A
F10 Toggle menu bar activation N/A N/A N/A
F11 N/A N/A N/A N/A
F12 N/A N/A N/A N/A

Control Shortcut Keys
Recommended CTRL+Letter Shortcuts

Key Function
CTRL + Z Undo
CTRL + X Cut
CTRL + C Copy
CTRL + V Paste

Suggested CTRL+Letter Shortcuts

Key Function
CTRL + N New
CTRL + O Open
CTRL + P Print
CTRL + S Save
CTRL + B Bold*
CTRL + I Italic*
CTRL + U Underline*

* These shortcuts are suggested for text formatting applications, in the context for which they make sense. Applications may use other modifiers for these operations.

QR Code
QR Code dev:guidelinesandchecklistfortesting (generated for current page)