W3C home > Mailing lists > Public > public-apa@w3.org > July 2016

ACTION-2046: CSS-AAM

From: Cynthia Shelly <cyns@microsoft.com>
Date: Wed, 13 Jul 2016 00:03:48 +0000
To: "public-apa@w3.org" <public-apa@w3.org>
CC: Rossen Atanassov <Rossen.Atanassov@microsoft.com>
Message-ID: <CY1PR03MB23486785193BB1900C816EDFC6310@CY1PR03MB2348.namprd03.prod.outlook.com>
I've created a preliminary list of CSS modules that appear to have accessibility impacts. I'd like to talk a bit about format and organization before I move this into the CSS-AAM spec stub.

https://github.com/w3c/aria/wiki/CSS-AAM-Potential-Features


*       Some of these are simply about documenting the impact of features on accessibility API, so similar to the tables in the other AAM docs

*       Some of these need authoring advice, which might be WCAG techniques and failures, CSS Best Practices, or both.

*       Some have features that might be useful for other WCAG or COGA techiques

I don't expect any of those categories to be controversial. There is a fair bit of work to do, but it's most documentation of things that work now, and finding gaps.

The deeper conversations are about


*       Reading order, flow, navigation order. What is the right user experience when the visual layout and the dom are not in the same order? What layers of the accessibility stack should control that (AT, AAPI, DOM, Author, some mix of those?).

*       Accessibility views and whether media queries and related features are a good way to enable authors to optimize for accessibility.

There are also some specs that were too big or too dense to cover in an survey of this many specs. They are called out for more detailed review. It would be great if people could sign up to look at these in more detail.
Received on Wednesday, 13 July 2016 00:04:27 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:01 UTC