W3C home > Mailing lists > Public > public-aria-admin@w3.org > March 2016

Re: Tables in the APG

From: Michiel Bijl <michiel@agosto.nl>
Date: Thu, 31 Mar 2016 11:50:39 +0200
Cc: James Nurthen <james.nurthen@oracle.com>, Matt King <a11ythinker@gmail.com>, Shane McCarron <shane@aptest.com>
Message-Id: <3DD2BF1F-3B3C-40B0-BDE3-175D74DA2448@agosto.nl>
To: ARIA Working Group <public-aria-admin@w3.org>
As discussed during CSUN; all editors accept this change; use headings instead of tables for design pattern description. I’ve finished the edits <https://github.com/w3c/aria/tree/headings>. There is a rawgit version <https://cdn.rawgit.com/w3c/aria/headings/practices/aria-practices.html> available. I would like to merge this into master just to prevent any conflicts with future edits.

One thing that remains is that we need to figure out how to exclude the sub-headings within the design patterns—since these repeat for all of them; it get’s tiresome real quick and makes the TOC longer than necessary. I’ve contacted Shane about this, but have not yet heard back from him. I’ve included him in this e-mail as a reminder :)


> On 19 Mar 2016, at 00:06, Michiel Bijl <michiel@agosto.nl> wrote:
> Hi Matt,
> With the new stylesheet came a bug—originating in the APG stylesheet—; tables are now too wide for moderate screen widths if they have more than two columns. We can quite easily change this. However, this made me think, why is all design pattern information (the characteristics) in a table anyway?
> I’ve discussed this with James, and I think it would be interesting to see how the document would look and feel if we used headings in stead of the tables. I’ll create a branch and work on this. I’ll try to have it finished somewhere tonight (10PM PST).
> If there is any good reason why this information is in a table, I’d gladly hear about it.
> —Michiel

Received on Thursday, 31 March 2016 09:51:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:59:02 UTC