DOCSEARCHbyAlgolia
Submit Docs

W3C Accessible Rich Internet Applications (ARIA)

repository·main·Indexed 20 days ago

https://github.com/w3c/aria

The W3C ARIA suite of technologies, including the core ARIA specification and various Accessibility API Mappings (AAM) for HTML, CSS, SVG, MathML, and PDF. It provides technical specifications and guidelines for making web content and applications accessible to people with disabilities, featuring modules such as dpub-aria and graphics-aria.

Tokens
10.4K
Snippets
15
Records
55
Agent score
73%

What's inside w3c-aria

  1. Overview of the Graphics WAI-ARIA Module

    main
    The graphics-aria specification is a module within the WAI-ARIA suite. It provides accessibility guidelines and technical specifications specifically for graphics-related content within the ARIA framework.

  2. Overview of the Digital Publishing WAI-ARIA Module (dpub-aria)

    main
    The dpub-aria repository contains the Digital Publishing WAI-ARIA Module. This module is part of the broader WAI-ARIA (Accessible Rich Internet Applications) suite, which provides technical specifications for making web content and applications more accessible to people with disabilities.

  3. Overview of Graphics Accessibility API Mappings (graphics-aam)

    main
    The graphics-aam specification is part of the W3C ARIA suite. It focuses on Graphics Accessibility API Mappings, providing guidance on how graphics-related accessibility information should be mapped to various accessibility APIs.

  4. Overview of PDF Accessibility API Mappings (pdf-aam)

    main
    The pdf-aam repository contains the specification for PDF Accessibility API Mappings. This specification is a component of the broader ARIA (Accessible Rich Internet Applications) suite, which provides guidelines and technical specifications for making web and application content accessible to assistive technologies.

  5. Overview of CSS-AAM

    main
    CSS Accessibility API Mappings (css-aam) is a project developed by the W3C Accessible Rich Internet Applications (ARIA) Working Group. It focuses on defining how CSS properties and values map to accessibility APIs.

  6. Overview of HTML Accessibility API Mappings (html-aam)

    main
    HTML Accessibility API Mappings (html-aam) is a specification developed by the W3C WAI ARIA Working Group. It defines how HTML elements and attributes map to accessibility APIs. This specification serves as the foundation for the Editor's Draft version of the HTML-AAM specification.

  7. ARIA Working Group communication channels

    main

    The ARIA Working Group uses several channels for communication:

    • Email: The public mailing list is public-aria@w3.org.
    • Slack: Join via w3ccommunity.slack.com in the #aria channel or web-a11y.slack.com.
    • New Members: Should receive a welcome email from the Chairs. If you do not receive one, contact the chairs.

  8. Access ARIA specifications and related modules

    main

    This repository contains the core Accessible Rich Internet Applications (ARIA) specification and several related Accessibility API Mappings (AAM) and modules.

    Core Specification:

    • ARIA: The main specification for accessible web applications. Use the ARIA Issue Repository for issues related to the main spec or issues involving both the ARIA spec and other ARIA working group specifications.

    Related Specifications and Modules:

    • accname: Accessible Name and Description Computation.
    • core-aam: Core Accessibility API Mappings.
    • css-aam: CSS Accessibility API Mappings.
    • html-aam: HTML Accessibility API Mappings.
    • dpub-aria: Digital Publishing WAI-ARIA Module.
    • dpub-aam: Digital Publishing Accessibility API Mappings.
    • graphics-aria: Graphics WAI-ARIA Module.
    • graphics-aam: Graphics Accessibility API Mappings.
    • svg-aam: SVG Accessibility API Mappings.
    • mathml-aam: MathML Accessibility API Mappings.
    • pdf-aam: Portable Document Format Accessibility API Mappings.

    Note on Issue Tracking: For most specifications listed above, please use their specific dedicated issue tracking repositories rather than the main ARIA repository.

  9. Access the SVG Accessibility API Mappings (svg-aam) specification

    main

    The svg-aam specification defines how SVG elements map to the Accessibility API. You can access the specification in two forms:

    1. Editor's Draft: The current working version of the specification, available at https://w3.github.io/svg-aam/.
    2. Published Version: The most recent stable release, available at https://www.w3.org/TR/svg-aam-1.0/.

    This specification is part of the ARIA suite and is maintained by the SVG working group.

  10. What is IDL (Interface Definition Language)?

    main

    IDL (Interface Definition Language) is used to define object interfaces and specify the surface APIs of web platform objects. It provides the syntax for how these APIs manifest as JavaScript constructs.

    Key distinctions for developers:

    • HTML vs. DOM: HTML is the static markup (content attributes) parsed from a server. The DOM is the live, in-memory tree (IDL attributes) manipulated via JavaScript.
    • Content Attributes vs. IDL Attributes: Content attributes are found in the source HTML (e.g., <input type="text">). IDL attributes are the JavaScript properties used to access or change those values (e.g., el.type = "text").

  11. How to manage shared resources in ARIA specifications

    main

    The aria-common repository serves as the central source for files shared across multiple ARIA specification repositories.

    Important Workflow Rule: All content updates must be made in the w3c/aria-common repository. Changes made directly in copies within other ARIA repositories will be overwritten the next time the content is synced from the common repository.

  12. How issues are triaged in the ARIA WG

    main

    New issues are triaged during ARIA WG meetings. The triage process involves:

    • Moving the issue to the correct issue-tracking repository if necessary.
    • Adding a release label to prioritize the expected resolution year.
    • Assigning WG members to the issue.
    • Adding the agenda label if the issue requires group discussion to reach consensus.

    WG members can manually add the agenda label to any issue they believe requires further discussion.