Written by: Kurt Bunge
London Accessibility is announcing that Alistair Duggin will be presenting the first talk at their July 27th meetup at the Angel Building, 407 St. John St, London, England. Duggin’s talk will be on “How do you make a website as big as GOV.UK accessible to the widest possible audience.”
Michiel Bijl will follow Duggin and talk about, “The ARIA Authoring Practices Guide: what is it and how does it help?”
WAI-ARIA provides semantics designed to allow an author to properly convey user interface behaviors and structural information to assistive technologies in document-level markup. WAI-ARIA 1.1 adds features to WAI-ARIA 1.0 to complete the HTML+ARIA accessibility model.
The new and updated working draft is open for review as they are looking for comments. WAI-ARIA 1.1 adds:
- table roles and a model to distinguish tables from grids.
- the “aria-roledescription” property to refine user understanding of roles.
- changed applicability of “aria-readonly” and “aria-level”.
- expanded explanation of “supported” vs. “required” states and properties.
Core Accessibility API Mappings (Core-AAM) and Accessible Name and Descriptions: Computation and API Mappings (AccName-AAM) provide support for the new WAI-ARIA 1.1 features as well as more complete accessibility API Mapping for other features.
Several new accessibility improvements to Microsoft’s Office Online have been rolled out. The improvements give users who are blind or have low vision a better experience. Microsoft has improved the way screen readers interact with Office Online through the use of the WAI-ARIA (Web Accessibility Initiative – Accessible Rich Internet Applications) web accessibility standard.
Microsoft has made other improvements over the past year as well. The following OfficeGarage videos demonstrate some of the improvements:
The W3C’s Protocols and Formats Working Group has published the first public working draft of API Mappings 1.1 (Core-AAM). It supports the updated working Draft of Accessible Rich Internet Application (WAI-ARIA 1.1). WAI-ARIA helps to improve the accessibility and interoperability of web content by providing an ontology of roles, states, and properties that developers can use to define accessible user interface elements. Core-AAM shows developers how user agents should expose semantics of content languages to accessibility APIs across multiple content technologies and includes much of WAI- ARIA.
Accessible Rich Internet Applications (WAI-ARIA) 1.0 is now a World Wide Web Consortium (W3C) Recommendation. Publishing WAI-ARIA is an important step making web content and application more accessible to people with disabilities. WAI-ARIA defines how developers of browsers, media players, mobile devices and assistive technologies (AT), and content developers can achieve better cross-platform accessibility. WAI-ARIA is introduce in the WAI-ARIA Overview.
More information on WAI-ARIA
The HTML working group at the W3C has published and updated working draft of Using WAI-ARIA in HTML.
The World Wide Web Consortium (W3C), an international community that develops open standards, such as the Web Content Accessibility Guidelines 2.0 (WCAG 2.0), to ensure long-term growth of the web, launched a Web and Mobile Interest Group. The new group is chartered to accelerate the development of Web technology so that it becomes a compelling platform for mobile applications and cross platform development. Read more about the new web and mobile interest group from W3C.
The User Agent Accessibility Guidelines (UAAG) serve as a guide to developers and user-agent vendors. It outlines the process for making Web browsers, media players, and assistive technologies (software that some people with disabilities use in interacting with computers) accessible to people with disabilities.