ISSUE-38: A.2.1 Naming non-text-objects

A.2.1 Naming non-text-objects

Raised by:
Jeanne F Spellman
Opened on:
Level A Success Criteria for Guideline A.2.1
• A.2.1.1 Editing Non-text Objects (content display): Editing views that render non-text objects contained within the content being edited can display any text alternatives that are identifiable by the authoring tool. It is permissible for the authoring tool to change editing views to display the text alternatives (e.g., from WYSIWYG to instruction level).

RS: Surfacing other accessible UI should also be an option and may even be better in some cases.

• A.2.1.2 Non-text Objects (user interface "chrome"): Non-text objects in the "chrome" have text alternatives that present equivalent information, except for the situations listed below. [WCAG 2.0]
o (a) Controls-Input: If a non-text object is a control or accepts user input, then it has a name that describes its purpose. [WCAG 2.0]

How is this exposed? This teps on the platform for exposure. And what does it mean to have a name?
It's like that every object in the chrome is a non-text object.
Related Actions Items:
No related actions
Related emails:
No related emails

Related notes:

JR: OK so exposed via accessibility platform architecture should be made clear. Doesn't seem to be a problem that all UI objects need name does it?

Jeanne F Spellman, 25 Jul 2008, 17:26:50

Text removed. Satisfied.

Jeanne F Spellman, 1 Aug 2008, 19:32:13

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 38.html,v 1.1 2016/02/01 09:50:29 carine Exp $