Minutes of Mobile-A11y TF teleconference of 11 June 2015

Minutes (in HTML)
http://www.w3.org/2015/06/11-mobile-a11y-minutes.html

Text of Minutes:

    [1]W3C

       [1] http://www.w3.org/

                                - DRAFT -

              Mobile Accessibility Task Force Teleconference

11 Jun 2015

    See also: [2]IRC log

       [2] http://www.w3.org/2015/06/11-mobile-a11y-irc

Attendees

    Present
           Kathy, Marc, Johlic, jeanne, David, JonA, JanR, MarkJ,
           HennyS

    Regrets
           Alan, Detlev, Kim

    Chair
           Kathy

    Scribe
           Jan

Contents

      * [3]Topics
          1. [4]1. Finish Best Practices - Robust
             http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Robust_Te
             chniques
      * [5]Summary of Action Items
      __________________________________________________________

    <trackbot> Date: 11 June 2015

    <David> Having trouble finding password

    <David> :)

    <HennyS> Skype dropped for me and I hear nothing in WebX

    <marcjohlic> The "Call me" function isn't working now either..
    interesting..

    <David> It's just me an Jan on call right now

    <David> Is someone besides Jan talking

    <HennyS> I can neither dial in or get connected to audio via
    WebX, so that sounds about right.

    <scribe> scribe: Jan

    (lots of problems getting on to WebEx)

    <HennyS>
    [6]http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Robust_Techniqu
    es

       [6] http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Robust_Techniques

1. Finish Best Practices - Robust
[7]http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Robust_Techniques

       [7] http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Robust_Techniques

    <David>
    [8]http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Robust_Techniqu
    es

       [8] http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Robust_Techniques

    Kathy: We left off talking about robust technuiques
    ... Were discussing supporting characteristics of the platform
    ... e.g. can set text size in settings but up to apps to honour
    that

    DM: Bullet number 3? ( sometimes the developer narrows the
    input, without being aware of all the possibilities of the
    variety of input being used. )

    KW: No, Support the characteristic properties of the platform

    JR: So native apps should support the platform text size
    directly...
    ... For web apps, it goes through the browser

    JA: Not realistic to support all sizes for all types of text

    JR: So maybe technique is to think about what text makes sense
    to enlarge
    ... And then guidance on how to esnsure that the containers and
    layout for that text

    JR, JA: Discuss different types of resizing

    JA: Font size settings are not AT

    <David> WCAG2ICT language for 1.4.4 This applies directly as
    written, and as described in Intent from Understanding Success
    Criterion 1.4.4 (also provided below).

    <David> Note 1: Content for which there are software players,
    viewers or editors with a 200 percent zoom feature would
    automatically meet this success criterion when used with such
    players, unless the content will not work with zoom.

    JA: 3 finger zoom is AT

    JR: Pinchzoom in browser is not AT

    JA: So I guess WCAG2ICT is consistent.

    DM: Intent of section is to allow enlargement without
    magnification.
    ... But that was from days that magnifiers were separate

    [9]http://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140916/F69

       [9] http://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140916/F69

    JR: Isn't this the failure?

    DM: There was no browser zoom in prior to 2006

    JA: I've found scenarios to break browser zoom

    KW: Are those things we should add to this list?

    JA: Added earlier under another setting
    ... We've been talking about text size, what about stopping
    animation, contrast etc.

    KW: Question is do we have any things we really want to have
    under here.

    JA: Challenge here is that sufficient techniques have to meet
    something

    DM: No, sufficient techs can eb "ands"

    JA: We could provide lots of native techsm eg for iOS
    ... Would be a good place
    ... Following OS settings does seem to fit in

    KW: Would you add anything for mobile web?

    JA: You could
    ... But I'm not sure what you can query from the OS
    ... e.g. I don't think you could query contrast
    ... But could figure out if zoom is on
    ... Apps can do so much more on the native side

    KW: I'm hearing that we don't need to add anything for web apps

    JA: Well, talking with Jeanne we were discussing how certain
    ARIA best practices don't work well with mobile
    ... e.g related to key strokes
    ... e.g. sliders

    DM: Do you have an example?

    JA: Open Ajax alliance etc.
    ... SSB lab as well
    ... VO seems to know its a slider but is not able to control it

    DM: Maybe with a BT keyboard

    JA: I'd have to test that.

    DM: My guess is that it would work.

    JR: BUT still people who do use keyboard (or keyboard emulator)
    still need it to work

    KW: Anything to add?

    Ja, JR, DM: Discuss OAA slider

    KW: End of meeting, tty next week,

    Participants: Kathy W., Jon A., Jan R. Jeanne S., Markc J,

    Participants: Kathy W., Jon A., Jan R. Jeanne S., Markc J,
    Heeni S.

Summary of Action Items

    [End of minutes]

Received on Thursday, 11 June 2015 16:05:35 UTC