trackbot, start meeting

<trackbot> Meeting: Silver Community Group Teleconference

<trackbot> Date: 08 February 2019

Requirements draft: https://w3c.github.io/silver/requirements/index.html

"Flexibility: As the web continues to diversify, a conformance structure is needed that can be customized for different uses and technologies. A static website for a pizza shop has different accessibility conformance needs than a social media site being updated thousands of times per second."

Under maintenance "Flexibility: A flexible structure enables greater scaling of new and expiry of outdated guidelines. A flexible process enables guidelines to keep pace with technology. Flexible participation – particularly of people with disabilities – empowers a community and enables more inclusive insights."

<Zakim> bruce_bailey, you wanted to say I already got lost

"A flexible structure enables greater scaling of new and expiry of outdated guidelines." proposing rewording that to methods of meeting guidelines, rather than guidelines themselves expiring often.

"A flexible structure enables greater scaling of new - and expiry of outdated - methods to meet guidelines."

Clearer rewording from bruce_bailey: "A flexible structure enables greater scaling of new methods to meet guidelines. It also allows for the expiration of outdated methods to meet guidelines."

<bruce_bailey> +1

+1

"A flexible process enables guidelines to keep pace with technology."

"A flexible process of updating guidelines enables the overall guidance to keep pace with technology."

<bruce_bailey> A flexible process of updating methods enables the overall guidance to keep pace with technology.

+1

"Flexible participation – particularly of people with disabilities – empowers a community and enables more inclusive insights."

"Scaling: Silver can consider multiple referring contexts, multiple use cases, and iteration and addendums over time when designing a system and taxonomy that is as future friendly as it is user-centric."

<Cyborg> Silver applies to...

"Scaling: Silver applies to multiple referring contexts, multiple use cases, and iteration and addendums over time when designing a system and taxonomy that is as future friendly as it is user-centric."

<Cyborg> Silver applies to multiple contexts, multiple use cases, is iterative, future-friendly and user-centric

<Cyborg> yes two lists in a single list. can be split.

Scaling: Silver should apply to multiple contexts and multiple use cases. Silver should be iterative, future-friendly, and user-centric.

<Cyborg> is or must?

<Cyborg> must?

<Jan> will be?

<bruce_bailey> designed to be?

<Cyborg> designed to be sounds goo

<Cyborg> good

<Cyborg> intends to be

<bruce_bailey> +1 to intends to be

<Jan> +1 intends to be

+1

Scaling: Silver intends to apply to multiple contexts and multiple use cases. Silver intends to be iterative, future-friendly, and user-centric.

<bruce_bailey> +1

<Cyborg> i always find double tos a bit awkward.

<Cyborg> intends to apply to...

<Cyborg> might want to massage that a bit...

<Cyborg> We expect Silver to apply to multiple contexts and use cases. Silver intends to be iterative, future-friendly and user-centric.

<Cyborg> We intend Silver to apply to...

<Cyborg> if you put the intend before Silver in the first sentence it sounds better

<bruce_bailey> +1

Governance: Accessibility guidance and all supporting documentation should be as forward looking and future friendly as possible – anticipating common scenarios like new technology. If possible, they should also consider the introduction of new modalities like surface reaction and ultrahaptics. Utilize tools that allow interested parties to predict when issues important to them are being discussed. Maintain a backlog that reflects issues along with thei[CUT]

<Cyborg> what about IoT?

<Cyborg> isn't it also kind of a culture-shift away from WCAG to DAG?

<Cyborg> if so, is that bluntly stated anywhere?

<bruce_bailey> +1 to removing opening sentence (or two)

<Cyborg> governance statement

Evolving Technology: As content technology evolves, it must be re-evaluated against assistive technology for compatibility. Likewise, as assistive technology evolves or emerges, it must be evaluated against the backward compatibility of various content technology. Silver needs a flexible design that will allow for updates as new technologies emerge, assistive technologies improve, and changing technologies produce new barriers for people with disabilities.

<Zakim> bruce_bailey, you wanted to suggest governance paragraph comes after evolving technology

As content technology evolves, it must be re-evaluated against assistive technology for compatibility. Likewise, as assistive technology evolves or emerges, it must be evaluated against the backward compatibility of various content technology.

Accessibility guidance and all supporting documentation should be as forward looking and future friendly as possible – anticipating common scenarios like new technology. If possible, they should also consider the introduction of new modalities like surface reaction and ultrahaptics.

<Zakim> bruce_bailey, you wanted to ask if "future friendly" in two paragraphs?

<Cyborg> new version?

Accessibility guidance and all supporting documentation should anticipate common scenarios like new technology and the introduction of new modalities.

<bruce_bailey> +1

<Jan> +1

<Cyborg> can we please see the new one? i'm confused

Silver needs a flexible design that will allow for updates as new technologies emerge, assistive technologies improve, and changing technologies produce new barriers for people with disabilities. Accessibility guidance and all supporting documentation should anticipate common scenarios like new technology and the introduction of new modalities. As content technology evolves, it must be re-evaluated against assistive technology for compatibility.

Likewise, as assistive technology evolves or emerges, it must be evaluated against the backward compatibility of various content technology.

<Charles> dropping off

<Cyborg> Silver needs a flexible design that can be updated as new technologies emerge, assistive technologies improve, and changing technologies produce new barriers for people with disabilities.

+1

Accessibility guidance and all supporting documentation should anticipate common scenarios like new technology and the introduction of new modalities like surface reaction and ultrahaptics.

<AngelaAccessForAll> sorry, I have to drop

<Cyborg> in case i forgot

trackbot, end meeting

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: johnkirkwood, Charles, LuisG, JF, KimD, jeanne, kirkwood, Cyborg, mikeCrabb, Shawn, Lauriat, AngelaAccessForAll, Makoto, JanMcSorley, Jennison, bruce_bailey, shari
Present: johnkirkwood Charles LuisG JF KimD jeanne kirkwood Cyborg mikeCrabb Shawn Lauriat AngelaAccessForAll Makoto JanMcSorley Jennison bruce_bailey shari
No ScribeNick specified.  Guessing ScribeNick: Lauriat
Inferring Scribes: Lauriat

WARNING: No "Topic:" lines found.

Found Date: 08 Feb 2019
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)