What type of word tabs can be used

On the other hand, if you program's commands don't map naturally, don't try to force it. Determine a more natural structure, and be sure to perform a lot of user testing to make sure that you've got it right. The Home tab is an exception to these considerations. While you don't have to have a Home tab, most programs should. The Home tab is the first tab, and contains the most frequently used commands.

If you have frequently used commands that don't fit into the other tabs, the Home tab is the right place for them. If you can't determine a meaningful, descriptive tab name, it is probably because the tab isn't well designed. If your ribbon organization just isn't working, reconsider your tab design. Dividing commands into groups structures the commands into related sets. The group label explains the common purpose of its commands.

In this example, the Font and Paragraph groups are more noticeable than the Clipboard group, because they are what the eye sees first when moving up from the document.

In this example, the Tracking group receives the most attention, in part because the highlighted Review tab acts as a focal point. You can use various types of previews to show what will result from a command. By using helpful previews, you can improve the efficiency of your program and reduce the need for the trial-and-error learning approach. Live previews also invite experimentation and encourage creativity.

In this example, Word changes the Text highlight color and Font color commands to indicate their current effect. In this example, the Page Color command performs a live preview by showing the effect of the color options on hover. Live previews are a powerful feature that can really improve your users' productivity, but even simple static previews can be a big help.

Scaling a toolbar is simple: if a window is too narrow to display a toolbar, the toolbar displays what fits and makes everything else accessible through an overflow button. A goal of rich commands is to take full advantage of the available space, so scaling a ribbon requires more design work.

There is no default ribbon size, so you should not design a ribbon with a particular width in mind. You have to design layouts with a wide range of widths and realize that any one of them could be the one most of your users will see. Scaling is a fundamental part of ribbon design, not the last step. When designing a tab, specify the different layouts for each group up to three as well as the combinations that can be used together.

The ribbon will show the largest valid combination that fits the current window size. Toolbars scale using an overflow button. There is no default ribbon size. The smallest size is a single pop-up group icon. Whenever practical, map your program's commands to these standard tabs, given in their standard order of appearance.

If you have contextual commands related to format, design, and layout, but not enough for multiple tabs, just provide a Format tab. Whenever practical, map your program's commands to these standard groups, which are given within their associated tabs in their standard order of appearance.

Take advantage of the discoverability and scalability of ribbons by exposing all the commonly used commands. When appropriate, move frequently used commands from dialog boxes to the ribbon, especially those that are known to be hard to find. Ideally, users should be able to perform common tasks without using any dialog boxes. Don't use the scalability of ribbons to justify adding unnecessary complexity. Continue to exercise restraint don't add commands to a ribbon just because you can.

Keep the overall command experience simple. The following are ways to simplify the presentation:. Present each command on only one tab. Avoid multiple paths to the same command especially if the command requires many clicks to invoke.

It may seem like a convenience to find a command through multiple paths. But keep in mind that when users find what they are looking for, they stop looking. It is all too easy for users to assume that the first path they find is the only path which is a serious problem if that path is inefficient. Exception: Contextual tabs may duplicate a few commands from the Home and Insert tabs if doing so prevents changing tabs for common contextual tasks.

Within a group, put the commands in their logical order, while giving preference to the most frequently used commands. Overall, the commands should have a logical flow to make them easy to find, while still having the most frequently used commands appear first. Generally, commands with 32x32 pixel icons appear before commands with 16x16 pixel icons to aid scanning across groups. Avoid placing destructive commands next to frequently used commands.

A command is considered destructive if its effect is widespread and either it cannot be easily undone or the effect isn't immediately noticeable. Use separators to indicate strongly related commands, such as a set of mutually exclusive options. Consider using toolbar-style groups for sets of strongly related, well-known commands that don't need labels.

Doing so allows you to present many commands in a compact space without affecting discoverability and ease of learning. To be so well known, such commands are frequently used, instantly recognized, and therefore tend to be on the Home tab. Use 32x32 pixel icons for the most frequently used and important labeled commands. When scaling a group down, make these commands the last to convert to 16x16 pixel icons.

Avoid arbitrary command placement. Think carefully about your tab and group design to ensure that users aren't wasting time inspecting every tab to find the command they want. Avoid marketing-based placement. Marketing objectives around the promotion of new features tend to change over time. Consider future versions of your product and how much frustration a constantly changing organization will cause. Disable commands that don't apply to the current context, or that would directly result in an error.

If helpful, use the enhanced tooltip to explain why the command is disabled. But you can prevent that:. Another place people frequently misuse tabs is to create columns. This is different from data that you would put in a table. It is text meant to be read all the way down one column, then down the next, without the association between cells in a row that you typically see in a table. If you use tabs to create the appearance of columns, a screen reader will read the first line in the first column, then the first line in the second column, then the second line in the first, then the second line in the second column, etc.

In Word, you can divide a part of your document into accessible columns. Put a continuous section break at the beginning and end of where you want your columns. Then, from the layout tab on the ribbon, choose the number of columns you want. These directions are for Office Other versions of Microsoft Office may work slightly differently.

A screen reader will see it more like this: Module 3 Photography for Social Reform, the early days Jan. Jacob Riis and Lewis Hine. Read Pages Take Module 3 Quiz. These tabs are indicated at the bottom of the horizontal ruler by tiny tick marks. The four most common types of custom tabs are left-aligned, centered, right-aligned, and decimal-aligned. Custom tab settings are indicated on the horizontal ruler by tab markers. Bar : Draws a vertical line.

First Line Indent : Inserts an indent marker that indents only the first line in a paragraph. Hanging Indent : Inserts an indent marker that indents all lines but the first line. Editor's Picks. Linux kernel 5. Windows Do these 11 things immediately. Top 5 things to do about your tech before you die. If you're not using a kanban board, you're not as productive as you could be.

Comment and share: Tutorial: How to create and correctly employ Word tabs. Show Comments. Hide Comments.

My Profile Log out. Join Discussion. Add your Comment.