Fwd: Hi, forwarding to Makoto and Jan: REVIEW - Reflow Understanding proposed changes (due by March 5)

皆さん、

縦書きのリフローとスクロールに関連するWCAG解説書に大幅な変更があり、私のところにレビュー依頼が来ています。WCAG
2.2本体ではなく解説のほうです。

まだちゃんと見ていないのですが以下の記述が気になっています。

Similarly, users reading content written in a language where one scrolls
horizontally to read (such as traditional Chinese or Japanese) it is not
desired to also need to vertically scroll back-and-forth to read.

なぜ気になっているかというと、山口啄さんが問題提起した縦組で可変数の段組み #77
<https://github.com/w3c/jlreq-d/discussions/77>
は、縦書きのときは増減可能な段組みを使って縦書きなのに縦スクロールという可能性を指定しています。

しかし、縦書きなのに縦スクロールというのはまだWCAGの解説書に書いてもらう段階ではないようにも思います。どうしましょう？

村田 真
---------- Forwarded message ---------
From: Julie Rawe <jrawe@understood.org>
Date: 2025年2月26日(水) 1:21
Subject: Re: Hi, forwarding to Makoto and Jan: REVIEW - Reflow
Understanding proposed changes (due by March 5)
To: MURATA <eb2mmrt@gmail.com>
Cc: Jan McSorley <mcsorleyjan@gmail.com>


Hi, Makoto and Jan. At today's AG meeting, Alistair mentioned the Reflow
review comments that are due March 5th. He said:

   - It is a complete rewrite of the Understanding document for Reflow.
   - Everything from the Intent heading and the sections after that are
   essentially new or wholly revised.
   - There are a number of ways to provide feedback. First general
   indication of support. Second provide comments on things you'd like to
   change. Third, provide specific editorial feedback in Suggestions, if
   possible.

Hope this information helps, thanks.

On Thu, Feb 20, 2025 at 4:18 PM Julie Rawe <jrawe@understood.org> wrote:

> Hi, Makoto and Jan, I hope you're doing well!
>
> Based on our email conversation last month about WCAG 2.2 and vertical
> languages, I wanted to make sure that Makoto is aware of all the changes
> that have been proposed to WCAG 2.2's SC 1.4.10 Reflow. The two-week
> review period started yesterday and ends March 5. The rest of this email
> thread has more detail, including a link to the github issue if you want to
> add your comments.
>
> Hope this is helpful, thanks!
>
>
>
> ---------- Forwarded message ---------
> From: Michael Gower <michael.gower@ca.ibm.com>
> Date: Wed, Feb 19, 2025 at 4:29 PM
> Subject: Re: REVIEW - Reflow Understanding proposed changes (due by March
> 5)
> To: WCAG list <w3c-wai-gl@w3.org>
> Cc: WCAG2 Backlog <public-wcag2-issues@w3.org>
>
>
> FYI, the preview link in the email failed to work. It is also offered in
> the PR itself, but here is a direct link
>
> https://deploy-preview-4055--wcag2.netlify.app/understanding/reflow
>
>
>
> *From: *Michael Gower <michael.gower@ca.ibm.com>
> *Date: *Wednesday, February 19, 2025 at 11:20 AM
> *To: *WCAG list <w3c-wai-gl@w3.org>
> *Cc: *WCAG2 Backlog <public-wcag2-issues@w3.org>
> *Subject: *[EXTERNAL] REVIEW - Reflow Understanding proposed changes (due
> by March 5)
>
> The following email outlines the updates proposed by the WCAG 2 Task
> Force. It provides a two-week window for Working Group members to review
> non-normative WCAG 2 updates. This review period only contains changes with
> the guidance for 1. 4. 10
>
> The following email outlines the updates proposed by the WCAG 2 Task
> Force. It provides a two-week window for Working Group members to review
> non-normative WCAG 2 updates.
>
> This review period only contains changes with the guidance for 1.4.10
> Reflow, in the following pull request:
>
> https://github.com/w3c/wcag/pull/4055
>
> The Understanding document has been wholly rewritten, and several
> techniques modified. We anticipate going through more than one review
> period on this change, since it is so substantive. For this review, we are
> asking for feedback in several broad ways:
>
>    1. Use the preview link
>    <http://The%20latest%20updates%20will%20be%20visible%20via%20this%20preview%20link%20of%20the%20understanding%20doc>
>    to review the updated Understanding document.
>    2. If you believe it can be published in its current state, give a
>    thumbs up on the Pull Request description.
>    3. Provide broad comments in the Issue conversation regarding the
>    update. Identify areas you like, or that you feel need work, or
>    considerations you believe are missing. These will be immediately as part
>    of this PR or captured for future updates.
>    4. Provide specific suggestions to improve language. To do so through
>    the github suggestion process:
>
>
>    1. From the Files changed view, load the diff for the reflow.html
>       document (it will be unrendered by default).
>       2. Find the line you wish to suggest a modification for
>       3. Activate the + symbol beside it, then press Ctrl/Cmd+g to add a
>       suggestion
>
> *How to participate in future task force work*
>
>    - Attend Friday call
>    <https://www.w3.org/groups/tf/wcag2x-backlog/calendar/>.
>    - Participate asynchronously in GitHub discussions
>    <https://github.com/w3c/wcag/discussions>.
>    - Self-assign issues on the project board
>    <https://github.com/orgs/w3c/projects/56/views/1>.
>    - Subscribe to Listserv: public-wcag2-issues@w3.org.
>
> *Completed changes*
>
> A table showing all merged changes by date
> <https://github.com/orgs/w3c/projects/56/views/7> is available.
>
>
>


-- 
 --
慶應義塾大学政策・メディア研究科特任教授
村田 真