Skip to main content

Operable

Content tagged with Operable

Not finding what you're looking for? Try using Advanced Search.
Not finding what you're looking for? Try using Advanced Search.

✎ Technique: Site and page navigation

Page

It's important to provide consistent navigation regions to navigate between a site's pages and—where there is a lot content on each page—between sections of pages.

✎ Technique: Session extension

Page

For a number of reasons including data persistence, performance and security, it is sometimes beneficial to terminate idle user sessions. It's important to warn people a session is about to expire and give them the option to continue.

✎ Technique: Accessible modal dialogs

Page

Modal dialogs can enhance usability by focusing attention on a specific message that requires a user action to continue.

An accessible modal dialog is one where keyboard focus is managed properly, and the correct information is exposed to screen readers.

✎ Technique: Expandable sections

Page

Expandables (sometimes called “collapsible” or “disclosure widgets”) are simple interface patterns that allow you to expand and collapse content.

✎ Technique: Hit areas

Page

Interactive elements should not be difficult to select or activate when using a mouse or a touchscreen.

Generous sizing and spacing is important, and their implied visual “hit area” should correspond to the control’s active area.

✎ Technique: Focus order and tabindex

Page

Interactive elements should, under most circumstances, be focusable in the order that they appear in the source code. This helps people who are using the keyboard or alternative input devices to follow focus in a logical order.

✎ Technique: Keyboard operable custom controls

Page

Sometimes, design requirements mean that you need to create a custom interactive element rather than using a native HTML element.

Your element will not be accessible by keyboard unless it is included in focus order and it can be activated using keys.