WAI Technical Activity Statement
The Web
Accessibility Initiative (WAI) Technical Activity addresses
barriers to Web accessibility on several levels. First, it seeks to
ensure that the full range of core technologies of the Web, from HTML to
the Semantic Web, is accessible. Barriers exist when these technologies
lack features needed by users with visual, auditory, physical, cognitive
or neurological disabilities; or when the accessibility potential in the
technology is not implemented in Web content or applications. The WAI
Technical Activity coordinates closely with the WAI
International Program Office, which focuses on WAI education and
outreach, web accessibility community discussion, and accessibility
standards coordination.
The WAI Technical Activity reviews accessibility support across all W3C
specifications through the Accessible Platform Architectures (APA)
Working Group, and develops the WAI-ARIA suite of resources for making
Rich Internet Applications accessible through the work of the Accessible
Rich Internet Applications Working Group (ARIA WG). The WAI Technical
Activity has promoted implementation of accessibility improvements in
Web technologies through development of a set of three WAI guidelines:
Web Content Accessibility Guidelines (WCAG), User Agent Accessibility
Guidelines (UAAG), and Authoring Tool Accessibility Guidelines (ATAG).
These guidelines describe features needed to achieve different levels of
accessibility, and include reference checklists and implementation
techniques. Future guidelines work may be through the development of
combined guidelines.
Highlights Since the Previous Advisory Committee Meeting
Since the previous W3C Advisory Committee Meeting in October 2015, the
WAI Technical Activity accomplished the following through its currently
active Working Groups.
- Newly chartered in October 2015; began operating separately from
the former PFWG in January 2016.
- Participated in multi-group discussions on a harmonized approach
to text alternatives.
- Co-sponsored the Cognitive
and Learning Disabilities Task Force and the HTML Accessibility Task Force.
- Initial exploration of creating a Research Task Force to take over
some activity conducted by the former Research
and Development Working Group.
- Continued review of W3C Last Call Working Drafts, and dialog with
other W3C Working Groups to address accessibility issues in W3C
specifications where needed. Reviewed and in some cases sent
comments on specifications, and addressed feedback received.
- Continued regular review of new Community
and Business Groups to help ensure that accessibility issues
are considered from the beginning, attempting to respond efficiently
to large number of new groups.
- Increased formal
tracking of specification reviews via a wiki structure.
- Group was not recharted after the expiry of its charter; some
aspects of its work expected to be taken up in other Working Groups.
- Group was not recharted after the expiry of its charter; some
aspects of its work expected to be taken up in other Working Groups.
- Group was not recharted after the expiry of its charter; its scope
will be taken up by the new APA and ARIA Working Groups described
above.
- Published Media
Accessibility User Requirements as a Working Group Note.
Upcoming Activity Highlights
Accessible Platform Architectures Working Group
- Begin work on Web Payments Accessibility User Requirements.
- Continue review and dialog on accessibility issues in W3C Working
Drafts.
- Increase outreach to other W3C Working Groups to help incorporate
accessibility in their own process.
- Increase use of the WAI Interest Group and other channels to
support broader engagement in the process of ensuring accessibility
features in W3C specifications.
- Continue to monitor Community Groups and other relevant activity
that impacts accessibility.
Accessible Rich Internet Applications Working Group
- Publish WAI-ARIA 1.1 as a Candidate Recommendation.
- Publish updated Working Drafts of the remaining WAI-ARIA 1.1
modules and accessibility API mappings.
- Perform interoperability testing of WAI-ARIA 1.1.
- Identify requirements for WAI-ARIA 2.0.
Web Content Accessibility Guidelines Working Group
- Continue to document additional techniques for WCAG 2.0, primarily
focused on HTML 5 and WAI-ARIA.
- Respond to public comments on WCAG 2.0 and support materials.
- Publish updated versions of Understanding WCAG 2.0 and WCAG 2.0
Techniques.
- Continue to explore gap analysis and potential requirements for
future content authoring guidelines.
- Coordinate with other groups to support understanding and
implementation of WCAG 2.0.
- Improve the effectiveness of How to Meet WCAG 2.0, also known as
the Quick Reference.
Summary of Activity Structure
Michael Cooper,
WAI Technical Activity Lead
$Id: Activity.html,v 1.643 2016/02/17
16:52:47 cooper Exp $
