W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2015

Minutes: User Agent Telecon 9 April 2015

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 9 Apr 2015 13:54:06 -0500
Message-ID: <CA+=z1WmE_+-o4do6mSohR0Mmb-bgvvouTNAKsQqWEyvE6Fr5Pw@mail.gmail.com>
To: WAI-ua <w3c-wai-ua@w3.org>
from http://www.w3.org/2015/04/09-ua-minutes.html
User Agent Accessibility Guidelines Working Group Teleconference 09 Apr 2015

See also: IRC log  http://www.w3.org/2015/04/09-ua-irc
<http://www.w3.org/2015/04/09-ua-irc>
Attendees
PresentJeanne, Jim_Allan, Greg_Lowney, Kim_PatchRegretspartial-KimChairJim
AllanScribeallanj
Contents

   - Topics <http://www.w3.org/2015/04/09-ua-minutes.html#agenda>
      1. Joseph Comment
      <http://www.w3.org/2015/04/09-ua-minutes.html#item01>
      2. exit criteria <http://www.w3.org/2015/04/09-ua-minutes.html#item02>
      3. Documenting Implementations
      <http://www.w3.org/2015/04/09-ua-minutes.html#item03>
   - Summary of Action Items
   <http://www.w3.org/2015/04/09-ua-minutes.html#ActionSummary>

------------------------------

<trackbot> Date: 09 April 2015

<scribe> scribe: allanj

Open item 1
Joseph Comment

4.1.6
https://www.w3.org/WAI/UA/work/wiki/Comment_Response_20_March_2015#Follow_up_comment_from_Joseph_from_1_April_2015

joseph - I would make changing states/values level A.

Consider any interactive UI such as a combobox, or a slider, or a live
region. Surely it's a basic (level A) requirement that if the value of
slider changes, or if a chat log changes (live region), then the AT is
notified. Accessibility APIs support a whole raft of accessibility events.
They don't just store role, states, and properties; they also send out
notifications whenever these...

scribe: change. Here are links to changes supported by a11y API event
systems: ....

Any UA that has a complete implementation of some a11y API service MUST
have implemented the event model thereof. Of course, it's up the AT to
decide which events it wants to pay attention to, but these 4.1.x rules
apply to the UA.

jr: remove 4.1.6 bullet - Change state/value notifications as this is
already covered in 4.1.2 as a A level

*RESOLUTION: The change notification is covered in 4.1.2 as a level A
success criteria. UAWG removed the bullet "Change state/value
notifications" in 4.1.6 as it is redundant and at the wrong level.*
exit criteria

<jeanne> https://www.w3.org/WAI/UA/work/wiki/Latest_Draft_of_Exit_Criteria

js: added "Each feature may be implemented by a different set of products,
there is no requirement that all features be implemented by a single
product. "

gl: +1

ja: +1

<jeanne> https://www.w3.org/WAI/UA/work/wiki/Latest_Draft_of_Exit_Criteria

<jeanne> http://www.w3.org/TR/css3-fonts/#cr-exit-criteria

jr: there are a few others - def of implemented, and def of independent
that are needed

js: perhaps a need for interoperable
... that is worth keeping.... interoperable - passing the respective test
cases

=== independent ===

gl: what about IE and Spartan...they are the same company.

jr: just use independent and don''t define it. use common sense.

ja: should we say
... "at least 2 different products"

gl: covered in bullet 2

ja: do we want to use def of implemented and independent

gl: interoperability - platform AAPI is outside the UA and necessary for
all implementation. so breaks the interoperable def

js: GL 4?

gl: 4.1.1 covers interoperability, 4.1.x is details.
... our test suites will find a tool that check the interaction between the
UA and AAPI -- msaa inspect tool
... interoperability in section 4 doesn't need to be mentioned.

jr: we have test cases or procedures. if the UAs pass the test then we have
implementations

js: the defs may convolute the process

*RESOLUTION: UAWG approves latest draft of Exit Criteria -
https://www.w3.org/WAI/UA/work/wiki/Latest_Draft_of_Exit_Criteria
<https://www.w3.org/WAI/UA/work/wiki/Latest_Draft_of_Exit_Criteria>*

close item 3

open item 2
Documenting Implementations

<jeanne>
http://w3c.github.io/UAAG-Implementations/Implementations-by-feature

jr: 1.1.1 at least 2 implementations for every item on list -
https://www.w3.org/WAI/UA/work/wiki/Appendix_E:_Alternative_Content

gl: all must be done by 2 browsers with various extensions or settings

<scribe> *ACTION:* allanj to create a table (some mechanism) to track
implementations for
https://www.w3.org/WAI/UA/work/wiki/Appendix_E:_Alternative_Content
[recorded in http://www.w3.org/2015/04/09-ua-minutes.html#action01]

<trackbot> Error finding 'allanj'. You can review and register nicknames at
<http://www.w3.org/WAI/UA/tracker/users>.

<scribe> *ACTION:* jallan to create a table (some mechanism) to track
implementations for
https://www.w3.org/WAI/UA/work/wiki/Appendix_E:_Alternative_Content
[recorded in http://www.w3.org/2015/04/09-ua-minutes.html#action02]

<trackbot> Created ACTION-1082 - Create a table (some mechanism) to track
implementations for
https://www.w3.org/wai/ua/work/wiki/appendix_e:_alternative_content [on Jim
Allan - due 2015-04-16].

gl: can we use user style sheets to solve these for @alt, @title, etc.

js: need to add the use of user style sheets to applicability notes, or
definition of UA,

<Greg> But we should explicitly address to what extent user style sheets,
or just the user style sheet mechanism, can be used to comply with SC. And
whether this works even if the UA only supports a single user style sheet,
which makes it unlikely the user could find an off-the-shelf style sheet
that allows the UA to comply with a wide range of SC.

js: or part of plugin

all discussion of fallback content

<jeanne> https://www.w3.org/WAI/UA/work/wiki/1.1.1

jr: if there is not a mechanism for turning off or ignoring elements then
...

<canvas id="mycanvas" width="300" height="300">

Sorry, your browser cannot display this image.

</canvas>

<Jan> http://www.w3.org/html/wg/drafts/html/master/dom.html#fallback-content

js: find a better solution, table with 20+ items...this is a bad SC.
... change wording.
... with ATAG when there were lots of items to test no one passes.

ja: main issue is "fallback"

js: need a different SC for fallback
... can't create new SC this late. how do we eliminate 'fallback'

<jeanne> http://w3c.github.io/UAAG/UAAG20/#def-conditional-content

jr: could add a note to eliminate fallback content

<Greg> Currently, our definition of Alternative Content implicitly includes
fallback content (“Text that is programmatically associated with non-text
content”). But we could exclude it through a Note or adding to the SC
"(other than fallback content)".

gl: or parenthetical (fallback content not included)

jr: fallback is not necessarily text. an image could have video as fallback

<Jan> *ACTION:* JR to New note for alternative content, excluding fallback
content [recorded in http://www.w3.org/2015/04/09-ua-minutes.html#action03]

<trackbot> Created ACTION-1083 - New note for alternative content,
excluding fallback content [on Jan Richards - due 2015-04-16].

rrsagent make minutes
 Summary of Action Items *[NEW]* *ACTION:* allanj to create a table (some
mechanism) to track implementations for
https://www.w3.org/WAI/UA/work/wiki/Appendix_E:_Alternative_Content
[recorded in http://www.w3.org/2015/04/09-ua-minutes.html#action01]
*[NEW]* *ACTION:* jallan to create a table (some mechanism) to track
implementations for
https://www.w3.org/WAI/UA/work/wiki/Appendix_E:_Alternative_Content
[recorded in http://www.w3.org/2015/04/09-ua-minutes.html#action02]
*[NEW]* *ACTION:* JR to New note for alternative content, excluding
fallback content [recorded in
http://www.w3.org/2015/04/09-ua-minutes.html#action03]

[End of minutes]

-- 
[image: http://www.tsbvi.edu] <http://www.tsbvi.edu>Jim Allan,
Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Thursday, 9 April 2015 18:54:30 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 9 April 2015 18:54:31 UTC