Agenda for Silver meeting of Friday 19 November 2021

agenda+ No meeting next week, 26 November for U.S. holiday
agenda+ Writing Testable WCAG 3.0 Outcomes
<https://docs.google.com/document/d/1sugAtqie_x1XqHDZo1Im7ftDNllWeRV_ty4PULeoTV0/>
agenda+ Resolving Conformance Issues

   - Minutes from 12 November
   <https://lists.w3.org/Archives/Public/public-silver/2021Nov/0025.html> with
   where we left off on Issue 304
   - 304 <https://github.com/w3c/silver/issues/304> - conformance claims
   need feedback mechanisms
   - 352  <https://github.com/w3c/silver/issues/352>- multiple conformance
   models vs simplicity
   - 386  <https://github.com/w3c/silver/issues/386>- if we allow 95% to
   pass, people will stop at 95%. Proposal for addressing minor errors
   - 394  <https://github.com/w3c/silver/issues/394>- the effort of proving
   conformance can overshadow development.
   - 425  <https://github.com/w3c/silver/issues/425>- will it be possible
   for multiple means of measurement to determine if the website conforms?
   - 448  <https://github.com/w3c/silver/issues/448>- a small minority of
   pages with "critical errors" should still pass. Important to large and
   dynamic sites.
   - 457  <https://github.com/w3c/silver/issues/457>- wants flexible
   conformance for 3rd party, but doesn't want multiple conformance models
   - 460  <https://github.com/w3c/silver/issues/460>- flexibility for
   conformance is desperately needed.  Incentive for adoption.
   - 470  <https://github.com/w3c/silver/issues/470>- process approach
   allows orgs to focus on making core tasks accessible. More clarity on
   defining process.
   - 494  <https://github.com/w3c/silver/issues/494>- how will content-free
   applications like CMS be evaluated and scored?


Conference call info <https://www.w3.org/2017/08/telecon-info_silver-fri> -
Reminder to please sign up to scribe
<https://www.w3.org/WAI/GL/task-forces/silver/wiki/Scribe_List>!