From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Rose Subject: Re: An improvement for a reading of exported HTML tables Date: Thu, 07 May 2009 17:47:38 +0200 Message-ID: <87ws8skj8l.fsf@kassiopeya.MSHEIMNETZ> References: <440047.97592.qm@web28306.mail.ukl.yahoo.com> <87skjhgsly.fsf@brailcom.org> <62BCF64A-144E-43AB-B1EF-392EF73E960B@gmail.com> <87y6t9fazr.fsf@brailcom.org> <44287AE6-13B1-4323-B5A6-62F61BA319F8@gmail.com> <7wmy9pxcmr.fsf@brailcom.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M25lU-0008O9-FH for emacs-orgmode@gnu.org; Thu, 07 May 2009 11:44:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M25lP-0008E1-Ja for emacs-orgmode@gnu.org; Thu, 07 May 2009 11:44:03 -0400 Received: from [199.232.76.173] (port=42624 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M25lP-0008Ds-Dc for emacs-orgmode@gnu.org; Thu, 07 May 2009 11:43:59 -0400 Received: from mail.gmx.net ([213.165.64.20]:44792) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1M25lO-00058m-Qh for emacs-orgmode@gnu.org; Thu, 07 May 2009 11:43:59 -0400 In-Reply-To: <7wmy9pxcmr.fsf@brailcom.org> (Jan Buchal's message of "Thu, 07 May 2009 15:31:56 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Jan Buchal Cc: emacs-orgmode@gnu.org Jan Buchal writes: > CD> On May 7, 2009, at 12:44 PM, Jan Buchal wrote: > >>>>>>> "CD" == Carsten Dominik writes: > >> > CD> On May 7, 2009, at 11:38 AM, Jan Buchal wrote: >> >>> Hello again, >>>> >>>> the problem is little bit complicate :-) I need not in first >>>> row only but by every column which contain the name of row. In >>>> the attachment you can find the example >> >> CD> That is currently not possible. >> And is it possible fix it? From the point of view of accessibility is a >> bug. > > CD> I would not call it a bug, it is a limitation. Org is not a full > CD> HTML table editor, there are many things it cannot do, including > CD> column and row spanning, multiline fields, you name it. > Unfortunately it is a bug. See please WCAG documentation. It's not. It's just something not implemented. And, as I see it, it would be complicated to implement. What you want seems to be this: 1. It's recommended to put the column headers into the element (Org-mode does this). That way column headers are re-printed on every page, if a table exceeds the size of one printed page. 2. It's recommended to use elements in tables like this: | Country | Number of citizens | |---------+--------------------| | Germany | 84 Mio. | | France | XXX Mio. | In this case it could make sense to put the country names in tags (see 4.). I think this is, what you wanted. 3. Use the caption element to describe the purpose of a table. Org-mode does this. 4. The `scope' attribut describes, wich table cells are concerned by the element. Again, our country example. This table should be handled corretly by a screen reader: ... There are more possible values for `scope' (`colgroup' and `rowgroup') as well, as some additional possibilities to assign headers to cells (`header' and `id') in such a way, that multiple headers describe one cell. In our example, the headers `Germany' and `Number of citizens' would describe the cell `84 Mio.'. I don't see, how Org-mode could decide which headers describe wich cells. The most obvious thing to do would be, to a) mark cells as table-headers (this is the only needed new Org-syntax feature), b) if in the first table row, add a scope="col" to the
Citizens per country
Country Number of citizens
Germany 84 Mio.
France XXX Mio.
tag, c) if in the first column, add a scope="row" to the tag. Beacuse if we take all those possible assignments into account, we'll get something complicated to code, use and document... We would have to end with some kind of `formular' syntax, like the one used for the spreadsheet capabilities. Regards Sebastian