- From: Shawn Lauriat <lauriat@google.com>
- Date: Fri, 21 Jan 2022 11:27:23 -0500
- To: Silver TF <public-silver@w3.org>
- Message-ID: <CAGQw2hmq3OsH=h8NcaH+ku=EWFaObqjHHhS1y1w=K4s5sBgfPQ@mail.gmail.com>
Minutes from today's call
<https://www.w3.org/2022/01/21-silver-minutes.html>
Summary:
- Organization of work <https://github.com/w3c/silver/wiki>: An overview
of the newly organized wiki and use of Github
- Integrating ATAG and UAAG into WCAG 3
<https://docs.google.com/document/d/1MCQG_MIaEyC3nfwkWGoDWS6XQzMykXeC7qOOjj8AG8M/edit>
(continuing discussion)
- Question: How to make it clear (Issue 503) that when a barrier needs
to be addressed to clearly identify if it is user agent or content author
responsibility?
Group seems overall on board with not specifying responsibility, but
specifying opportunity and method for user agent, authoring tool, content
author, etc. Need examples to work through, though noted several
illustrative examples in the discussion.
- Question: Are we willing to commit to writing each method to target
just one of Content, UA or AT?
Seems like we won't necessarily have clear lines between these, but
examples will help. Noted the slightly ancient Language of page
example
<https://docs.google.com/document/d/18JyGF-AK8Qgq7DPyVlDYmxoj6814rORxuCf0l0oSb7U/edit>
with authoring tool method, and Suzanne will write up another.
On Thu, Jan 20, 2022 at 5:10 PM Shawn Lauriat <lauriat@google.com> wrote:
> agenda+ Organization of work <https://github.com/w3c/silver/wiki>
> agenda+ Integrating ATAG and UAAG into WCAG 3
> <https://docs.google.com/document/d/1MCQG_MIaEyC3nfwkWGoDWS6XQzMykXeC7qOOjj8AG8M/edit> (continuing
> discussion)
> agenda+ WCAG 2.x to WCAG 3 Migration process
> <https://docs.google.com/document/d/1aCRXrtmnSSTso-6S_IO9GQ3AKTB4FYt9k92eT_1PWX4/edit#heading=h.usv6j46q7db>
> gap to fill: research
>
> Conference call info <https://www.w3.org/2017/08/telecon-info_silver-fri>
>
Received on Friday, 21 January 2022 16:27:49 UTC