Principle A3: Editing views are operable
Guideline A3.1: Provide keyboard access to authoring features
A3.1.1: Keyboard Access (Minimum) (Level A)
All functionality of the authoring tool is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.
The intent of this success criterion is that users can operate the authoring tool using a keyboard. If it is keyboard accessible, then other input methods that use keyboard techniques, such as voice recognition software, will also work.
A3.1.2: No Keyboard Traps (Level A)
If keyboard focus can be moved to a component using a keyboard interface, then focus can be moved away from that component using only a keyboard interface. If it requires more than unmodified arrow or tab keys or other standard exit methods, authors are advised of the method for moving focus away.
The intent of this success criterion is that users navigating by keyboard shouldn't get trapped within an item. This applies to the user interface and any rendered web content.
A3.1.3: Efficient Keyboard Access (Level AA)
The authoring tool user interface includes mechanisms to make keyboard access more efficient than sequential keyboard access.
The intention of this success criterion is to make keyboard navigation more efficient that merely tabbing through every component. For example, in many desktop apps, users can press the Alt key to bring up letters or numbers for every menu item, and then select and continue to navigate using these.
Guideline A3.2: Provide authors with enough time
A3.2.1: Auto-Save (Minimum) (Level A)
The authoring tool does not include session time limits or the authoring tool can automatically save edits made before the session time limits are reached.
The intent of this success criterion is to avoid users losing their work due to it not being saved when a session times out. It can be achieved by not having timeouts or by automatically saving work before a user is timed out.
A3.2.2: Timing Adjustable (Level A)
The authoring tool does not include time limits or at least one of the following is true:
- Turn Off
- Authors are allowed to turn off the time limit before encountering it; or
- Adjust
- Authors are allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
- Extend
- Authors are warned before time expires and given at least 20 seconds to extend the time limit with a simple action (e.g. "press the space bar"), and authors are allowed to extend the time limit at least ten times; or
- Real-time Exception
- The time limit is a required part of a real-time event (e.g. a collaborative authoring system), and no alternative to the time limit is possible; or
- Essential Exception
- The time limit is essential and extending it would invalidate the activity; or
- 20 Hour Exception
- The time limit is longer than 20 hours.
The intent of this success criterion is to ensure users have enough time to complete tasks. Time limits can be anything that happens automatically at the end of a set period of time, so it includes things like auto-refreshing content, or the session ending. The best way to meet this criterion is to allow time limits to be turned off.
A3.2.3: Static Input Components (Level A)
The authoring tool does not include moving user interface components that accept input where the movement of these components cannot be paused by authors.
The intent of this success criterion in to prevent users from having to respond to moving objects, either by clicking on a moving target or having to track a moving object.
Guideline A3.3: Help authors avoid flashing that could cause seizures
A3.3.1: Static View Option (Level A)
If an editing-view can play visual time-based content, then playing is not necessarily automatic upon loading the content and playing can be paused.
The intent of this success criterion is to avoid users with photosensitive seizure disorder from accidentally being exposed to flashing content that could trigger a seizure. This means that time-based media, such as animations, should not play automatically, or there should be a way to pause or stop it.
Guideline A3.4: Enhance navigation and editing via content structure
A3.4.1: Navigate By Structure (Level AA)
If editing-views expose the markup elements in the web content being edited, then the markup elements (e.g. source code, content renderings) are selectable and navigation mechanisms are provided to move the selection focus between elements.
The intent of this success criterion is to help users who navigate using the keyboard to work more efficiently. If web elements are already exposed to the author, they should be able to search and navigate by them. For example, in Microsoft Word, you can navigate by heading and heading level.
Guideline A3.5: Provide text search of the content
A3.5.1: Text Search (Level AA)
If the authoring tool provides an editing-view of text-based content, then the editing-view enables text search, such that all of the following are true:
- All Editable Text
- Any text content that is editable by the editing-view is searchable (including alternative content); and
- Match
- Matching results can be presented to authors and given focus; and
- No Match
- Authors are informed when no results are found; and
- Two-way
- The search can be made forwards or backwards.
The intent of this success criterion is to make it easy for authors to find and edit content. For example, many applications allow users to find and replace words or phrases.
Guideline A3.6: Manage preference settings
A3.6.1: Independence of Display (Level A)
If the authoring tool includes display settings for editing-views, then the authoring tool allows authors to adjust these settings without modifying the web content being edited.
The intent of this success criterion is that authors should be able to set their preferences for the editing view and that this should not affect how the published content appears. For example, authors should be able to work in high contrast mode but publish content that appears with normal contrast settings.
A3.6.2: Save Settings (Level AA)
If the authoring tool includes display and/or control settings, then these settings can be saved between authoring sessions.
The intent of this success criterion is that authors should not have to re-enter their setting preferences every time they use the tool. Their preferences should be saved and automatically load each time they open the tool.
A3.6.3: Apply Platform Settings (Level AA)
The authoring tool respects changes in platform display and control settings, unless authors select more specific display and control settings using the authoring tool.
The intent of this success criterion is that the authoring tool should allow platform level settings to be used within it. For example, if the author has selected large icons in the operating system settings, then the icons in the authoring tool should also be large. If the author specifically selects different settings within the authoring tool, that should also be respected.
Guideline A3.7: Ensure that previews are at least as accessible as in-market user agents
A3.7.1: Preview (Minimum) (Level A)
If a preview is provided, then at least one of the following is true:
- In-Market User Agent
- The preview renders content using a user agent that is in-market; or
- UAAG (Level A)
- The preview conforms to the User Agent Accessibility Guidelines 1.0 Level A
The intent of this success criterion is that authors should be able to preview their content in a way that is accessible for them but without giving an unrealistic view of what the end user would experience. It is best if the preview is displayed in the same user agent or authoring tool.
