- From: Mark Sadecki <mark@w3.org>
- Date: Wed, 30 Apr 2014 17:03:50 -0400
- To: David MacDonald <david100@sympatico.ca>, HTML Accessibility Task Force <public-html-a11y@w3.org>, lwatson@paciellogroup.com, Steve Faulkner <faulkner.steve@gmail.com>, John Foliot <john@foliot.ca>
On 4/24/14, 12:37 PM, David MacDonald wrote: > I've reviewed my results of testing: > > http://davidmacd.com/test/details.html > > The existing examples are spotty but NVDA is working OK using describedby in > Chrome and FF . > > On the call I suggested using a straight paragraph above the table summarizing > the table. That is essentially what example 1 is (with the addition of > describedby). Since leaving the describedby doesn't break anything, and works in > some AT, let's leave that as a core technique... I expect Freedom Scientific > will come on board, eventually. I agree. > > The same for the other examples using "figure". They don't work when the table > gets focus, but they are no worse than using a paragraph before the table. They > don't break anything. So my proposed changes to the spec are: I agree with this also. > > 1) Remove example 3 if "Details" is pulled from the spec. A new Heartbeat was published yesterday and example 3 was removed from the spec. > 2) Amend the text in the last example > > ===current text=== > The best option, of course, rather than writing a description explaining the way > the table is laid out, is to adjust the table such that no explanation is needed. > > ===suggested text=== > It would be best to rearrange the table so the row headers are in the first > column and the column headers are in the first row as in the following example, > and to ensure the table headers are give <th>. For simple data tables that > don't have merged headings or multiply layers of headings, this would usually > eliminate the need for for a table summary. I'm not sure this is actually necessary as the paragraph that follows already says this. http://www.w3.org/TR/2014/CR-html5-20140429/tabular-data.html#table-descriptions-techniques (see Code Example that follows the text you suggest replacing) With the text as it stands in the current Heartbeat draft, I see no need for any change to this section of the spec. Does everyone agree? Best, Mark > > Cheers, > > David MacDonald > > > > *Can**Adapt**Solutions Inc.* > > Tel: 613.235.4902 > > LinkedIn <http://www.linkedin.com/in/davidmacdonald100> > > www.Can-Adapt.com <http://www.Can-Adapt.com> > > > > / Adapting the web to *all* users/ > > / Including those with disabilities/ > > If you are not the intended recipient, please review our privacy policy > <http://www.davidmacd.com/disclaimer.html> > // > > > -- Mark Sadecki Web Accessibility Engineer World Wide Web Consortium, Web Accessibility Initiative Telephone: +1.617.715.4017 Email: mark@w3.org Web: http://w3.org/People/mark
Received on Wednesday, 30 April 2014 21:04:01 UTC