- From: Fred Esch <fesch@us.ibm.com>
- Date: Tue, 12 Apr 2016 12:56:26 -0400
- To: Joanmarie Diggs <jdiggs@igalia.com>
- Cc: public-svg-a11y@w3.org
- Message-Id: <201604121656.u3CGutW8008024@d01av05.pok.ibm.com>
Joanie, The resolution should have said Where an element has role=none or role=presentation and has a child title or desc element, user agents must ignore the role. We are not meeting this week as too many people are unavailable but I will put this back on the agenda to get the corrected resolution in the minutes. Thanks for the wording catch. Regards, Fred Esch Watson, IBM, W3C Accessibility IBM Watson Watson Release Management and Quality From: Joanmarie Diggs <jdiggs@igalia.com> To: Fred Esch/Arlington/IBM@IBMUS Cc: public-svg-a11y@w3.org Date: 04/12/2016 12:11 PM Subject: Re: name and description calculation - is there a mismatch between the document and what Apple implements? Hey Fred. Point of clarification: On 04/07/2016 10:50 AM, Fred Esch wrote: > We decided yesterday, that SVG elements with a title or desc and role > none/presentation - should be *included* in the accessibility tree. And > a SVG element with a title/desc and role none/presentation would be an > author error and would fail validation. Link to resolution. > <https://www.w3.org/2016/04/06-svg-a11y-minutes.html#ResolutionSummary> The resolution states: Where an element has role=none or role=presentation and has a descendent title or desc element, user agents must ignore the role. Descendant is not the same as "child." And the language for inclusion found at https://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html#include_elements specifically states "child." Is the language in the resolution accurate, or is it limited to immediate children? Thanks! --joanie
Attachments
- image/gif attachment: 50490964.gif
- image/gif attachment: graycol.gif
Received on Tuesday, 12 April 2016 17:03:31 UTC