- From: Richard Schwerdtfeger <schwer@us.ibm.com>
- Date: Tue, 22 Sep 2015 08:30:59 -0500
- To: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
- Cc: SVG-A11y TF <public-svg-a11y@w3.org>
- Message-ID: <OF37A3B886.6EA83649-ON86257EC8.004A2ED1-86257EC8.004A3FB2@us.ibm.com>
Sounds good. Rich Schwerdtfeger From: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com> To: Richard Schwerdtfeger/Austin/IBM@IBMUS Cc: SVG-A11y TF <public-svg-a11y@w3.org> Date: 09/21/2015 06:32 PM Subject: Re: update of WAI-ARIA Graphics Module and aria-gtype Hi Rich, I'm fine with any option that keeps it concise. However, be sure to keep the generic text regarding "any other elements that the relevant specifications say are never rendered". That both covers some deprecated SVG 1 elements and keeps it future-proof for new elements. ABR On 21 September 2015 at 16:51, Richard Schwerdtfeger <schwer@us.ibm.com> wrote: Hi Amelia, I am going through the latest API mapping specification. In section 5.1.1 you called out all the SVG namespaced elements that should not have an object in the accessibility tree. Also, later on you ask whether we need to have links to the elements themselves. In section 5.4.2 we already have all the SVG elements with links to the spec. they are defined in in the table which can be readily seen if you click on view as a single table. All elements indicated as "not mapped" should not be exposed in the accessibility tree. Can't we just say this and point to the table? The information is redundant if you put in the definition of "not mapped." Cheers, Rich Rich Schwerdtfeger
Attachments
- image/gif attachment: graycol.gif
Received on Tuesday, 22 September 2015 13:36:07 UTC