CSS Review Minutes (from the PF Telecon on 19 October)

The following is the CSS related excerpt from the minutes of the Protocols and
Formats Working Group teleconference on 19 October 2011. We are publishing this
excerpt separately because our CSS review is not priveleged.

For more about our current CSS review, please see:
http://www.w3.org/WAI/PF/wiki/CSS/Spec_Review


                                - DRAFT -

           Protocols and Formats Working Group Teleconference
                               19 Oct 2011
           CSS Review -- Beginning at 12:30PM Boston Time
      _________________________________________________________

CSS Review -- Beginning at 12:30PM Boston Time

    <MichaelC> [16]CSS Spec Review planning page

      [16] http://www.w3.org/WAI/PF/wiki/CSS/Spec_Review

    janina: Braille and Haptic and High Contrast and Large Print modules
    requested by PFWG

    mc: Dónal Fitzpatrick cannot get the review until November for
    Braille and Haptic

    <MichaelC> [17]Old thoughts on Braille CSS

      [17] http://www.w3.org/WAI/PF/braillecss.html

    mc: half way through reviewing Paged Media module
    ... problem with specialised zoom device, how will CSS react

    cs: good to let those dealing with zoom device to be aware about
    this matter

    janina: who to take this questions too?

    cs: problem with reordering the text
    ... order is sometimes content

    mc: modules are flexible
    ... css media queries overlay with these issues

    cs: a deep flaw in CSS issue where order is content
    ... tab order is the real issue while reading order is not as
    problematic

    leonie: grey area between content importance and navigability

    mc: need for user to expression preference to styling engine

    <jamesn> scribeNick: jamesn

    MC: Page Layout says to use visibility:hidden to make something not
    rendered. Says not to positition outside the pagebox
    ... it is undefined what the UA might do when this happens.
    ... there are a number of off-screen AT techniques which this may
    break

    JS: if braille display it might only be 18 characters wide do may
    need to do this kind of thing
    ... or once you have zoomed up things may not be on screen

    MC: paged media generally meant for print
    ... there are other ways of moving things around

    JS: large-print or braille printing

    CS: in general the off-screen techniques are older techiques
    ... in general I agree with this as an authoring guideline
    ... having this note mention something about the accessibility
    scenarios of this might be good as it would amke it clear that this
    wasn't forgotten

    MC: Basic UI Model
    ... No reviews have happened. I think this is in CR now

    CS: question would be whether the styling of form elements has been
    improved

    [18]http://dev.w3.org/csswg/css3-ui/#nav-index0

      [18] http://dev.w3.org/csswg/css3-ui/#nav-index0

    JN: has nav-index

    CS: perhaps this could be a solution to some of the ordering issues

    JN: Q? how does this play out with ARIA

    MC: sounds like we need more reviewers

    JN: in LCWD

    MC: next module is the font module
    ... not got to this yet
    ... Marquee module
    ... we do need a review to make sure there is the ability to stop
    the scroolling
    ... there doesn't seem to be a way to turn it off

    CS: AT could probably do something
    ... as long as you are using an AT that is doing more than looking
    at pixels could be ok

    JS: I think we have performed a review

    MC: wanted to look at the colour module partly becuase of the
    deprecation of system colours
    ... should just mark as an issue and go on
    ... we have forwarded the CSS Speech comments
    ... next is the aural style sheets module
    ... we haven't assigned anyone to review it

    JS: only other people other than us would be voice browsers

    MC: basic box model
    ... didn't assign anone to it. Basic CSS to position blocks of
    content on a page, in a line and as floats
    ... also has the visibility property

    JN: would like to see a note on display: none and visibility:hidden
    that these hide content from everybody

    MC: extended boc model

    points to the same URI\

    MC: line layout.
    ... within a line how you position inline content. A lot is about
    how you might move stuff up and down in relation to the line. Also
    stuff about dropcaps

Summary of Action Items

    [End of minutes]




-- 

Janina Sajka,	Phone:	+1.443.300.2200
		sip:janina@asterisk.rednote.net

Chair, Open Accessibility	janina@a11y.org	
Linux Foundation		http://a11y.org

Chair, Protocols & Formats
Web Accessibility Initiative	http://www.w3.org/wai/pf
World Wide Web Consortium (W3C)

Received on Tuesday, 25 October 2011 14:51:08 UTC