See also: IRC log
<chaals> [+1 to Doug - in general people think we are on the right path]
<scribe> scribenick: LJWatson
DS: We had lots of good feedback. People think we're on the right path.
JW: Interesting work in similar areas being done, like web components and data representation.
DS: Also with haptics.
... Think the haptics stuff could end up in CSS. Also chart.ml
was interesting - a format neutral chart framework for
different media.
<AmeliaBR> http://www.onsaito.com/csdv/doc/ChartML.pdf
DS: We should co-ordinate to make sure what we're doing here doesn't conflict.
CMN: Increasing awareness of cognitive accessibility, and note this is an area where we can do a lot of good or a lot of harm, so we should track.
RS: CSUN is a much larger gathering of people with disabilities, than blind/low vision people.
DS: We should include cognitive requirements in the documentation we provide. Should co-ordinate with the Cognitive TF.
FE: Tried to reach out to James Jackson. PhD candidate doing research into Dyslexia.
FE: Let's walk through the requirements to see whether we have enough.
ABR: Need to make sure we haven't missed anything.
<fesch> https://www.w3.org/wiki/SVG_Accessibility#Color_blind_users
FE reads through requirements for blind people.
FE: No requirement to visit items that represent data and get values?
DS: Should add it in.
FE reads requirements for colour-blind people.
<scribe> ACTION: Léonie to add requirement for data values to requirements. [recorded in http://www.w3.org/2015/03/13-svg-a11y-minutes.html#action01]
<trackbot> Created ACTION-1594 - Add requirement for data values to requirements. [on Léonie Watson - due 2015-03-20].
DS: Going back to requirements for blind people... do we need a requirement for finding the styling of elements/geometry of elements?
JW: To understand how something is represented and/or for communicating with others, it's useful to query. Written description is only useful if information is included.
<chaals> [+1 to being able to access style/geometry info of an object… ]
ABR: Good idea for a requirement.
JW: Restricted to elements with semantic value.
<scribe> ACTION: Léonie to add requirement for querying style/geometry information, for blind and colour-blind people. [recorded in http://www.w3.org/2015/03/13-svg-a11y-minutes.html#action02]
<trackbot> Created ACTION-1595 - Add requirement for querying style/geometry information, for blind and colour-blind people. [on Léonie Watson - due 2015-03-20].
CMN: Use case colour blind user trying to follow a non-colour-blind user's instruction to choose the red button.
ABR: We can give author's advice, but also need browser support for querying information.
CMN: Editing the wiki now.
JW: Could be a browser extension to pull out colour information.
RS: YOu want that, or authoring advice?
JW: Both.
DS: An authoring requirement that says people should describe colours seems unlikely. Should be a UA requirement if anything.
<AmeliaBR> There are color-finding plugins for design purposes, e.g.: http://www.colorzilla.com/
RS: We need to include
personalisation.
... Have a proposal for schema.org integration relating to
personalisation.
JW: Should co-ordinate with IndieUI.
FE reads through requirements for low vision people who don't use an AT.
RS: Pan and zoom capability would be good.
<chaals> [+1 - pan and zoom is really important]
DS: Might also be a useful requirement for cognitive disabilities, zoom in to remove extraneous information from view.
JW: With tactile graphics also might want to limit the amount of information presented.
DS: A snapshot feature is being discussed for SVG. Possible we could define print requirements, so only the content in the viewport is printed.
ABR: Zoom/pan is currently dependent on browser capability, and the entire content would be printed regardless of current zoom level.
DS: Also a rotate feature.
<chaals> [+1 to rotate…]
DS: When Firefox and other UA were introducing SVG support, there was resistance to interface behaviours being defined.
ABR: Things have changed in 10 years, for example video and audio elements require browsers to add user interface controls; might be worth looking at this again.
FE: We can ask.
DS: We don't want
non-interoperability.
... Without consistency, people won't know how to interact with
SVG from one example to another.
FE: THink pan/zoom/rotate should be a general requirement?
ABR: As long as it's in there somewhere.
<scribe> ACTION: Léonie to add zoom/pan/rotate requirement to wiki. [recorded in http://www.w3.org/2015/03/13-svg-a11y-minutes.html#action03]
<trackbot> Created ACTION-1596 - Add zoom/pan/rotate requirement to wiki. [on Léonie Watson - due 2015-03-20].
FE: Should there be a requirement for playing well with high-contrast mode?
ABR: "Should play well" is a good broad requirement.
+1 to playing well with HCM.
RS: Are aural style sheets dead?
DS: Pretty much, yes.
... Haptic style sheets, audio style sheets (not aural) with
things like the Web Audio API, might revive the idea.
RS: We think in single modality/visual. Need to think differently - about alternative modalities.
ABR: There is also cross-over - smart phone tools that read pages are not AT.
RS: So either audio style sheets, or programmatic access to speech?
DS: Would need a champion within CSS.
ABR: Plus implementation support.
FE: What does an audio style sheet do?
CMN: It lets you adapt speech output, switch accents, alter volume etc.
<chaals> close action-1596
<trackbot> Closed action-1596.
FE: Do we need a category for low vision people who do use AT?
DS: Should we list different kinds of low vision users?
<chaals> [I am going to go ahead and scribble in the wiki about this, so we can look at it next week too]
DS: For example someone who has narrow scope of vision will have different requirements from someone who has poor colour differentiation.
FE: We don't have time to look at requirements for cognitive disabilities today. There are visual requirements that will be important for them though, such as avoiding high-contrast black and white.
ABR: This is an argument for browser/personalisation, because some user requirements are conflicting (high or low contrast).
FE: Yes. Like the GPII thing for
example.
... Need more requirements for people with mobility
disabilities. For example they don't get tooltips.
ABR: That's an issue on touch devices too.
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/in 10 years,/in 10 years, for example video and audio elements require browsers to add user interface controls;/ Succeeded: s/them though./them though, such as avoiding high-contrast black and white./ Succeeded: s/personalisation/personalisation, because some user requirements are conflicting (high or low contrast)/ Found ScribeNick: LJWatson Inferring Scribes: LJWatson Default Present: fesch, Rich_Schwerdtfeger, +1.512.238.aaaa, LJWatson, Doug_Schepers, +1.609.759.aabb, [IPcaller], chaals, AmeliaBR Present: fesch Rich_Schwerdtfeger +1.512.238.aaaa LJWatson Doug_Schepers +1.609.759.aabb [IPcaller] chaals AmeliaBR Got date from IRC log name: 13 Mar 2015 Guessing minutes URL: http://www.w3.org/2015/03/13-svg-a11y-minutes.html People with action items: l onie WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]