- From: Fred Esch <fesch@us.ibm.com>
- Date: Tue, 27 Oct 2015 10:22:24 -0500
- To: "SVG-A11y TF" <public-svg-a11y@w3.org>
- Message-Id: <201510271526.t9RFQaQ2018357@d03av05.boulder.ibm.com>
All,
No meeting this week, TPAC is going on.
I made several edits to the Graphics Module to fix ReSpec errors and I
removed the figure section which was in the Graphics Module until figure
was included in ARIA 1.1.
In reviewing the Graphics Module I found several issues. We can discuss
them when we meet again - in a couple of weeks. No changes for the issues
below have been made.
Section: Abstract
We should mention user agents as well as assistive technologies in the
abstract. Other places in the doc, we call out user agents or features
that will be done by user agents and not just AT, for instance in the
introduction we state "enable semantic navigation, alternative styling,
and interactivity support". Below is the abstract with the suggested
changes. The only changes are 'web graphic' is used in the first sentence
instead of 'document' and 'user agents and assistive technologies' are used
instead of 'assistive technologies' throughout the first paragraph. I
styled the changes in purple and added angle brackets for those who can't
see the purple color.
<User agents and> assistive technologies need semantic information about
the structures and expected behaviors of a <web graphic> in order to convey
appropriate information to persons with disabilities. This specification
defines a [WAI-ARIA] module of core roles, states and properties specific
to web graphics. These semantics allow an author to express the logical
structure of the graphic to <user agents and> assistive technologies. <User
agents and> assitive technologies could then enable semantic navigation and
adapt styling and interactive features, to provide an optimal experience
for the audience. These features complement the graphics and document
structure elements defined by [HTML5] and [SVG2].
This document is part of the WAI-ARIA suite described in the WAI-ARIA
Overview.
Section: 4.1 Definition of Roles
Example 1
We don't discuss aria-flowto anywhere and aria-flowto appears in the
example. I would remove aria-flowto from the example.
Question - why was role graphics-symbol used on a group in the example. The
alternative is to use role graphics-symbol on the path and role none on the
group.
graphics-doc characteristics table
related roles should figure be a related role?
Example 2
Examples 3 and 4 are sufficient examples. I would eliminate example 2 until
the role (graphics-)symbol is moved to ARIA core. Using role
graphics-symbol on an img element in a list may confuse a user since the
default img role already works and a similar examples using the default
role appear elsewhere in other docs.
Example 3
We don't discuss aria-flowto anywhere. And aria-flowto appears in the
example. I would remove aria-flowto from the example.
We haven't agreed that aria-roledescription is the way we want to go. I
would remove aria-rolediescription from the example.
Regards,
Fred Esch
Watson, IBM, W3C
Accessibility
IBM Watson Watson Release Management and Quality
--1__
BBF478DFC239418f9e8a93df938690918c0ABBF478DFC23941
Content-Transfer-Encoding: quoted-printable
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline
<html><body><p>All,<br><br>No meeting this week, TPAC is going on.<br><br>I made several edits to the Graphics Module to fix ReSpec errors and I removed the figure section which was in the Graphics Module until figure was included in ARIA 1.1.<br><br><br>In reviewing the Graphics Module I found several issues. We can discuss them when we meet again - in a couple of weeks. No changes for the issues below have been made.<br><br><b>Section: Abstract</b><br><br>We should mention user agents as well as assistive technologies in the abstract. Other places in the doc, we call out user agents or features that will be done by user agents and not just AT, for instance in the introduction we state "enable semantic navigation, alternative styling, and interactivity support". Below is the abstract with the suggested changes. The only changes are 'web graphic' is used in the first sentence instead of 'document' and 'user agents and assistive technologies' are used instead of 'assistive technologies' throughout the first paragraph. I styled the changes in purple and added angle brackets for those who can't see the purple color.<br><br><font size="4" color="#8100FF"><User agents and> </font><font size="4">assistive technologies need semantic information about the structures and expected behaviors of a </font><font size="4" color="#8100FF"><web graphic> </font><font size="4">in order to convey appropriate information to persons with disabilities. This specification defines a [WAI-ARIA] module of core roles, states and properties specific to web graphics. These semantics allow an author to express the logical structure of the graphic to </font><font size="4" color="#8100FF"><user agents and</font><font size="4">> assistive technologies.</font><font size="4" color="#8100FF"> <User agents and> </font><font size="4">assitive technologies could then enable semantic navigation and adapt styling and interactive features, to provide an optimal experience for the audience. These features complement the graphics and document structure elements defined by [HTML5] and [SVG2].</font><br><br><font size="4">This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.</font><br><br><br><b><font size="4">S</font></b><b><font face="Default Sans
Serif">ection: 4.1 Definition of Roles </font></b><br><br><b><font face="Default Sans
Serif">Example 1</font></b><br><font face="Default Sans
Serif">We don't discuss aria-flowto anywhere and aria-flowto appears in the example. I would remove aria-flowto from the example.</font><br><br><font face="Default Sans
Serif">Question - why was role graphics-symbol used on a group in the example. The alternative is to use role graphics-symbol on the path and role none on the group.</font><br><br><br><b><font face="Default Sans
Serif">graphics-doc characteristics table</font></b><font face="Default Sans
Serif"> </font><br><font face="Default Sans
Serif">related roles should figure be a related role?</font><br><br><br><b><font face="Default Sans
Serif">Example 2</font></b><font face="Default Sans
Serif"> </font><br><font face="Default Sans
Serif">Examples 3 and 4 are sufficient examples. I would eliminate example 2 until the role (graphics-)symbol is moved to ARIA core. Using role graphics-symbol on an img element in a list may confuse a user since the default img role already works and a similar examples using the default role appear elsewhere in other docs.</font><br><br><b><font face="Default Sans
Serif">Example 3 </font></b><br><font face="Default Sans
Serif">We don't discuss aria-flowto anywhere. And aria-flowto appears in the example. I would remove aria-flowto from the example.</font><br><font face="Default Sans
Serif">We haven't agreed that aria-roledescription is the way we want to go. I would remove aria-rolediescription from the example.</font><font face="Default Sans
Serif"><br></font><br><br><br>
<table border="0" cellspacing="0" cellpadding="0"><tr valign="top"><td width="473" colspan="2" valign="middle"><div align="center"><font size="4" face="Verdana">Regards, <br><br>Fred Esch <br>Watson, IBM, W3C Accessibility</font></div></td></tr>
<tr valign="top"><td width="130" valign="middle"><img src="cid:1__=0ABBF478DFC239418f9e8a93df938690918c0AB@" width="163" height="23" alt="IBM Watson" align="bottom"></td><td width="342" valign="middle"><font size="4" face="Verdana">Watson Release Management and Quality </font></td></tr></table><br><BR>
</body></html>
--1__
BBF478DFC239418f9e8a93df938690918c0ABBF478DFC23941--
--0__
BBF478DFC239418f9e8a93df938690918c0ABBF478DFC23941
Content-type: image/gif;
name="09175227.gif"
Content-Disposition: inline; filename="09175227.gif"
Content-ID: <1__
BBF478DFC239418f9e8a93df938690918c0AB@>
Content-Transfer-Encoding: base64
iVBORw0KGgoAAAANSUhEUgAAAKMAAAAXCAMAAABQ6Q/RAAADAFBMVEXIx8cxLS5MSUrW1dXx8fE/
Ozzj4+N2c3SRj49oZWaEgYKsq6uenZ26ubmbm5v29vZ7e3tTU1M7OzsfHx/FxcX39/eamppmZmaR
j5AgICCqqqrR0dFaV1gAAAAjHyD///8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAADe7fL7AAADE0lEQVR4nM2WiW7kIAyGTbhz9O6eCL//U6bYGJJOst2dlaqppUm4
+fhtnAH8+gb7sroZxodWGZfA5UxP52+Ic2qVEbLDxujTLXnOTHydSDxNdC7DR+NvYQK02PLQYBDn
z5dRw04GAPibKIBec2GKuZjyrtbosVZr72J397Xyc+suPshsiOUBvRb4xavlzYoA2tI+XEQTFDfT
rkCFiFLIec8Y82jQ0dIhjOU5lmWGa254owKe/J5xPDBqdYHLphZBm08Zi5/nOnEsEUmHwiG6cx3X
Z6k8ID5c6kgHHC4YlblkJHcNlotO7Xp0RVP6lLFIPtTmsuDQDn+FGT4YTy3OXcTFEy85VUYonQMQ
WHWopSIdR83aTYRs5bBD9cz+VjBjyI3RbVEkSu7ed/XF8r18ExXF25ZJiWnk/RhD1S1JlFT5mLGc
B0KYNJG5rtEkLhjPGUVz32Lh2iw+k68WnhqJjeZTldqBr27dFkCz2mlyooxcac0zJUyWM8YKFnn8
KLofdFy7brvwXLctZs+6KScOTrSr6uft2y4SmJqa+tUcxPeKY/iEcc4+W8qNfYUrdSTtYvnRrfE1
rgk1QOqBs207ideoc2gLJGFMtEQ6YQy53OvwA1DifmM86PhQKxSZ66+uI/o6zdVcMmwtRHrBiGbm
XWysp2FTjbERHHUEPXAgtDRxrY5Vfsvph6PebGnFvmcswSnp2PcDcECPdYzkz2M8ziBH9rtl8c/3
Gh/X9TtuOhphWyToedNUzEp0boyZ8zQNnHLrXIhLy5jplBHVINnHmKj+415Lamt+QAdWDkphmcC5
mh8lodvqNsOqDyHw5GjamHjKGLKEj66LuK7i5XfmsVbwdX1+leL9vTiLIiTy8qFFjHwygjQA7j46
sUc/oxpoY4w9YzRW+RbsZeJ135mnJ9ErCuv8T4yqCGH6zYoGOyOXDowSqJ5yRtq6jzq2/z2IL7+l
H58eaWxMiULLlRjUOCU2+kfKNkkDuam8KJP6eqPB0+eIU7PexswpjQdG5AAJEOL1X+vPt/7/cuLg
UP7L/QtHfANvSEKvsxvttAAAAABJRU5ErkJggg=
--0__
BBF478DFC239418f9e8a93df938690918c0ABBF478DFC23941--
Received on Tuesday, 27 October 2015 15:27:14 UTC