- From: Charles Pritchard <chuck@jumis.com>
- Date: Tue, 20 Mar 2012 17:01:32 -0700
- To: David Singer <singer@apple.com>
- Cc: Janina Sajka <janina@rednote.net>, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, Sam Ruby <rubys@intertwingly.net>, Laura Carlson <laura.lee.carlson@gmail.com>, Maciej Stachowiak <mjs@apple.com>, Paul Cotton <Paul.Cotton@microsoft.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>, "public-html@w3.org" <public-html@w3.org>
On Mar 20, 2012, at 3:59 PM, David Singer <singer@apple.com> wrote: > I just hope that I'm never in the position of needing accessible access to a restaurant Charles manages, as it seems you prefer to focus on describing the front door before describing the menu (if ever). :-( Buddy, my menus are multilingual and available on the web following WCAG. Unfortunately, I have a hard time getting my restaurants to their opening date, but that's a different issue. Equal access does not mean equal effort. Some things take more work. Most of the work on these lists dealing with accessibility has been with peoples putting forth simple requirements and getting rebuffed. The hundreds (or thousands) of hours back and forth has been a learning process for many vendors. I don't expect people to intuit the nuances of multilingualism solely because they've used a .pod file and know UTF8 encoding schemes. I read dozens of books, attended many classes, spoke, argued and experienced. Many of the people posting about a11y are doing so from a perspective of experience in their field. Their perspective is something that is being shared, and many vendors are learning in the process. It seems that, until you feel you have a full grasp on things, you'd sooner block access to items you find to be irrelevant. That's common. Very common. It's ok. We'll get through it. You and me. Together. -Charles
Received on Wednesday, 21 March 2012 00:02:00 UTC