W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2018

Re: WCAG violations or accessibility enhancements

From: Olaf Drümmer <olaflist@callassoftware.com>
Date: Sat, 3 Mar 2018 21:37:25 +0100
Cc: Olaf Drümmer <olaflist@callassoftware.com>
Message-Id: <4F64DF2E-A333-450B-998F-65B29F56FAEF@callassoftware.com>
To: w3c WAI List <w3c-wai-ig@w3.org>, chagnon@pubcom.com
> On 2. Mar 2018, at 21:04, <chagnon@pubcom.com <mailto:chagnon@pubcom.com>> <chagnon@pubcom.com <mailto:chagnon@pubcom.com>> wrote:
> Your car analogy (see Duff's comments below) is good, but it doesn't jive in one key way for us in the technology business: Whatever our manufacturers do in their software affects those who create content and use AT to access it. 
> If I make a table in Word, I need a way to designate the user requirement for column headers. Word, the manufacturer, needs to provide me, the content creator, with the tools to do this. I can't do it on my own; the tool has to be there for me to use.


> Therefore, in these types of digital media, the manufacturers — all of them in the workflow — have to be told somehow what the accessibility requirements are for tables and column headers—what you called the user requirements. And the manufacturers must build their software to let the content creator make a compliant table with column headers.

What you say actually supports what Duff has written:

- a car maker has to put a seat belt into the car
- a driver and the passengers have to buckle up

- Word (or any other such program) has to provide a possibility to indicate whether a table cell is a header cell or not, and if so, for which other cells it serves as a header cell
- a user has to pay attention to using this possibility in an adequate manner

Same same.

Received on Saturday, 3 March 2018 20:37:54 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 3 March 2018 20:37:54 UTC