- From: Sailesh Panchang <spanchang02@yahoo.com>
- Date: Fri, 21 Jun 2013 12:01:37 -0700 (PDT)
- To: w3c-wai-gl@w3.org, public-html-a11y@w3.org, Richard Schwerdtfeger <schwer@us.ibm.com>
- Cc: Steve Faulkner <sfaulkner@paciellogroup.com>, mick@nvaccess.org
>>Let's stick with a consistent set of APIs (ARIA) that developers can go to as much as possible for one stop shopping. >>"back to the hodge podge of attributes that were thrown in at the end of HTML 4's release." The 'summary' attribute is like any attributes defined for various HTML elements meant to aid accessibility. Not sure why this is being singled out. ARIA is designed for making custom elements accessible that HTML elementss and attributes are unable to handle and not replace features that are AT-supported and serve users. Not sure why something that works to make content accessible as demonstrated by David's analysis is being thrown out of the window. Making AT and browsers support new techniques that have been authored now is not 'fixing a defect' but an enhancement. Deprecating attributes that are well supported by AT is a retrograde step. Thanks, Sailesh Panchang -------------------------------------------- On Fri, 6/21/13, Richard Schwerdtfeger <schwer@us.ibm.com> wrote: Subject: Re: HTML5 alternatives to table summary don't work in current browsers, and Screen Readers To: w3c-wai-gl@w3.org, public-html-a11y@w3.org Cc: "Steve Faulkner" <sfaulkner@paciellogroup.com>, mick@nvaccess.org Date: Friday, June 21, 2013, 10:48 AM David, I saw your post that you think summary should be reinstated because of a JAWS and/or NVDA have a defect (it works in VoiceOver) does not warrant going back to the hodge podge of attributes that were thrown in at the end of HTML 4's release. Let's stick with a consistent set of APIs (ARIA) that developers can go to as much as possible for one stop shopping. I have alerted Freedom Scientific of the defect and they will fix it. I have copied Mick Curran at NVDA and hopefully they will also correct the problem with IE and Firefox. Mick, please see the following link: http://lists.w3.org/Archives/Public/w3c-wai-gl/2013AprJun/0089.html#start89 We can't be writing specs. based on proprietary assistive technology defects. Rich Rich Schwerdtfeger
Received on Friday, 21 June 2013 19:02:14 UTC