Movatterモバイル変換

Appendix C: Accessibility Support

This appendix is informative, not normative.

C.1. SVG Accessibility Features

This appendix highlights the accessibility features of SVG and accessibility related specifications used to support SVG and the associatedW3C Web Content Accessibility Guidelines (WCAG) 2.0 [WCAG2] requirements they are designed to support.

[WCAG2] Create content that can be presented in different ways (for example simpler layout) without losing information or structure: Information and Relationships.

• Support foraria-labelledby for label relationships.
• Support foraria-describedby for description relationships.
• Support foraria-owns for structural relationships.
• Support foraria-controls for control relationships where an element controls the content and or behavior of another element.
• The‘g’ for defined groupings.
• Support for the WAI-ARIAgroup andradiogroup roles.

[WCAG2] Time Based Media: Provide alternatives for time-based media.

• The‘audio’ and‘video’ elements support the HTML‘track’ element to provide alternatives for time-based media

[WCAG2] Keyboard Accessible: Make all functionality available from the keyboard.

• Focus support and the‘tabindex’ attribute for sequential focus navigation aligned with HTML
• Keyboard Event attribute support along with Mouse Event support for script authors
• Keyboard Events for script authors
• Script support for setting focus on eachSVG Element in the DOM
• Script support for acquiring the‘tabindex’ attributeon eachSVG Element in the DOM
• Script support for the HTML activeElement property in theDocument interface

[WCAG2] Navigable: Provide ways to help users navigate, find content, and determine where they are.

• To enable bypassing of blocks of content SVG supports the: WAI-ARIAlandmark roles.
• Supports‘title’ to provide page titles.
• Supports‘tabindex’ to provide a sequential focus navigation order.
• Supports the‘a’ element, enabling authors to supply the link purpose both from its content.
• Supports headings and labels through the use of theheading role witharia-level,aria-labelledby andaria-label.
• Support visible focus by rendering visible focus on focused elements in the tab order.

[WCAG2] Readable: Make text content readable and understandable.

• Supports the language of the page as well as its parts through the‘lang’ attribute.

[WCAG2] Compatible: Maximize compatibility with current and future user agents, including assistive technologies.

• Supports Name, Role, and Value through the use ofWAI-ARIA attributes and the‘title’ element.

WAI-ARIA Support and text alternatives

• WAI-ARIA attributes
• Desc and Title text element alternatives

C.2. Supporting SVG Accessibility Specifications and Guidelines

This section enumerates the SVG accessibility-related specifications and authoring guidelines.

Related SVG Accessibility Specifications for User Agents

• TheSVG Accessibility API Mappings [SVG-AAM] specification.
• TheCore Accessibility API Mappings 1.1 [CORE-AAM]specification.
• TheAccessible Name and Description: Computation and API Mappings 1.1 [ACCNAME-AAM] specification.

Related Specifications for Content Authors

• WAI-ARIA 1.1 [WAI-ARIA]
• W3C Web Content Accessibility Guidelines (WCAG) 2.0 [WCAG2]