Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 11581-2-02:2002 Technical Guide — Standardized Object Icons for User Interfaces
CAN/CSA-ISO/IEC 11581-2:02 Requirements, Use Cases, and Compliance Guidance
The consistency of visual symbols in software interfaces is critical for usability, especially in global markets where icons must transcend language barriers. The international standard IEC 11581-2-02 (ISO/IEC 11581-2:2002), adopted in Canada as CAN/CSA-ISO/IEC 11581-2:02, defines a set of standardized object icons for graphical user interfaces. This article provides a comprehensive overview of the standard’s scope, technical requirements, implementation highlights, and compliance notes, serving as a practical guide for software developers, UI designers, and quality assurance teams.
1. Scope and Applicability
IEC 11581-2-02 is the second part of the IEC 11581 series on user interface icons. It specifies the design, meaning, and usage of object icons that represent concrete or abstract objects in interactive systems. These icons include representations for data objects (e.g., documents, spreadsheets), container objects (e.g., folders, wastebaskets), and system resources (e.g., disk drives, printers). The standard applies to any software application or operating system that employs graphical user interfaces, aiming to ensure cross-platform and cross-application consistency.
The standard defines a core set of mandatory object icons that must be used when their associated objects appear in an interface. It also provides guidelines for additional optional icons and variations (e.g., open vs. closed folder). The scope is limited to static objects; icons for actions or processes are covered in other parts of the series (e.g., IEC 11581-1 for general icon principles and IEC 11581-3 for pointer icons).
2. Technical Requirements for Object Icons
Icon Categories
Standardized object icons are grouped into categories based on the type of object they represent. Each category has specific graphical attributes that ensure immediate recognition. The table below summarizes the main categories and their distinctive features.
| Icon Category | Examples | Color / Style | Critical Shape Features |
|---|---|---|---|
| Data Objects | Document, Spreadsheet, Presentation | Typically white page with colored accents | Corner fold, content lines |
| Container Objects | Folder (closed/open), Wastebasket/Trash | Folder: Yellow or manila stylization; Wastebasket: Gray or blue | Folder: tab and flap; Wastebasket: outlines and opening |
| System Resources | Disk Drive, CD-ROM, Printer, Network Drive | Device-specific colors (printer: gray, CD: silver) | Distinctive physical outlines (disk shape, printer tray) |
| Applications | Generic application icon, Executable file | Varies, but must include indicator of software (e.g., small window) | May include a symbolic representation of the application type |
The standard specifies both monochrome and color versions for each icon, ensuring usability in diverse visual contexts. It also defines the minimum graphical detail required to maintain recognizability when icons are reduced to small sizes (e.g., 16×16 pixels). Each icon is formally described using an icon matrix – a grid that specifies the relative positions of essential pixel or vector elements, guaranteeing reproducible rendering across different platforms.
Graphical Representation Specifications
Each icon is described through a precise combination of shapes, relative dimensions, and positioning. For example, the Document icon must include a rectangular page with a folded upper-right corner and a set of horizontal lines representing text. The Folder icon consists of a tabbed front cover and a back portion, typically shown at a slight angle to suggest three dimensions. Color guidelines are provided where applicable: the Wastebasket icon is commonly rendered in shades of gray or blue with a cylindrical or rectangular outline, while the Printer icon features a paper feed slot and a control panel.
Implementation Tip: When creating icons based on IEC 11581-2-02, use vector graphics formats (e.g., SVG, EPS) to ensure that the relative proportions specified in the standard are preserved at any resolution. Avoid adding unnecessary detail that could obscure the icon at smaller sizes.
3. Implementation Highlights
Using Standard Icons in Software
Adopting IEC 11581-2-02 object icons provides significant benefits for software projects. It ensures that users immediately understand the purpose of interface elements without needing to learn custom iconography. Moreover, it facilitates internationalization since the icons rely on visual metaphors rather than text, reducing localization costs. Developers should map each core object (file, folder, disk, printer, etc.) to the corresponding standardized icon. The standard allows for minor stylistic variations – for instance, flat or detailed shading – as long as the essential graphical features remain unchanged.
Adapting to Resolution and Context
Modern applications require icons at multiple sizes (e.g., 16×16, 32×32, 48×48, 256×256). IEC 11581-2-02 includes guidelines for scaling: it recommends using simplified outlines for very small sizes while preserving the icon’s distinct silhouette. For high-resolution displays, the same vector definitions can be used at proportionally high resolutions. In dark‑mode or high‑contrast themes, the standard advises adjusting the icon base colors or applying a monochrome version while maintaining the shape specifications.
Caution: Modifying a standard object icon to the point where its silhouette or essential detail is lost may mislead users and break consistency. Always ensure that any custom variant retains the recognizable characteristics defined in the standard.
4. Compliance and Certification
Compliance with IEC 11581-2-02 is voluntary, but highly recommended for products aiming for international usability and accessibility. Manufacturers, software developers, and UI design teams can declare conformance by implementing all mandatory object icons in accordance with the specification’s graphic and semantic definitions.
Certification typically involves an audit of the icon set against the standard’s descriptions and reference images. Conformance marks can be used if the product passes an accredited testing process. To maintain compliance, any addition of new object icons must not conflict with those defined in the standard.
Compliance Benefit: Certification to IEC 11581-2-02 demonstrates a commitment to user interface consistency and quality. It can be a differentiator in public‑sector and enterprise software procurement, where adherence to international standards is often required.
For Canadian organizations, the adoption as CAN/CSA-ISO/IEC 11581-2:02 means that compliance with the standard aligns with Canada’s National Standard of Canada requirements, facilitating conformity with domestic interoperability mandates.
Frequently Asked Questions
Q: What is the difference between IEC 11581-2-02 and other parts of the IEC 11581 series?
A: This part (Part 2) specifically addresses object icons (documents, folders, drives, etc.). Part 1 covers general icon design principles, Part 3 deals with pointer icons, and later parts handle specific icon kinds (e.g., communication icons). Each part builds on a common framework.
A: This part (Part 2) specifically addresses object icons (documents, folders, drives, etc.). Part 1 covers general icon design principles, Part 3 deals with pointer icons, and later parts handle specific icon kinds (e.g., communication icons). Each part builds on a common framework.
Q: Are software developers required to comply with IEC 11581-2-02?
A: Compliance is not mandatory by law, but many large organizations and government agencies require conformance as part of their usability and accessibility policies. Adhering to the standard simplifies cross‑platform consistency and user training.
A: Compliance is not mandatory by law, but many large organizations and government agencies require conformance as part of their usability and accessibility policies. Adhering to the standard simplifies cross‑platform consistency and user training.
Q: Can I use modified versions of the standard icons?
A: Yes, as long as the modifications do not detract from the icon’s recognizability and meaning. The standard allows for alternative rendering styles (flat, skeuomorphic, etc.) provided the essential geometrical features remain intact and the icon’s semantics are unambiguous.
A: Yes, as long as the modifications do not detract from the icon’s recognizability and meaning. The standard allows for alternative rendering styles (flat, skeuomorphic, etc.) provided the essential geometrical features remain intact and the icon’s semantics are unambiguous.
Q: Does this standard cover icons for web‑based interfaces?
A: Yes, the standard applies to any graphical user interface, including web applications. For best results, web developers should ensure that scalable vector formats are used and that fallback images are provided for older browsers if needed.
A: Yes, the standard applies to any graphical user interface, including web applications. For best results, web developers should ensure that scalable vector formats are used and that fallback images are provided for older browsers if needed.
This article is for informational purposes and does not constitute legal or certification advice. Always refer to the full text of IEC 11581-2-02 (CAN/CSA-ISO/IEC 11581-2:02) for precise specifications.
© 2026 IEC Standards Publications. All rights reserved.