Re: Call for Consensus (CfC): APA Comment on css-multicol-1

+1

JF

On Tue, May 4, 2021 at 8:52 AM Janina Sajka (janina@rednote.net) <
janina@rednote.net> wrote:

> +1
>
> Janina Sajka writes:
> > Colleagues:
> >
> > This is a Call for Consensus (CfC) to the Accessible Platform
> > Architectures (APA) Working Group testing whether we have group
> > consensus on comments and an Accessibility Considerations section
> > request to the CSS Working Group regarding their css-multicol-1
> > specification as follows:
> >
> > <beginning of suggested comment>
> >
> >    Per [request for a11y-review](
> https://github.com/w3c/a11y-request/issues/2) of the [Multi-column Layout
> Module Level 1](
> https://www.w3.org/TR/css-multicol-1/#the-multi-column-model):
> >
> >  APA agrees with the concerns Rachel brought forth and has nothing more
> to add to those concerns.
> >
> >    However, APA does request an Accessibility Considerations section be
> added, which acknowledges potential issues and references WCAG. Statement
> could read:
> >
> >    "Setting container height and line length can pose challenges for
> people with visual or cognitive disabilities. See [WCAG Success Criterion
> 1.4.10 Reflow](https://www.w3.org/WAI/WCAG21/Understanding/reflow.html)
> and
> >    [WCAG 1.4.8 Visual Presentation](
> https://www.w3.org/WAI/WCAG21/quickref/#visual-presentation) to
> understand user needs."
> >
> >    At the end of Section 2 of the spec, a note is already present about
> accessibility issues occurring if the column's height exceeds the viewport
> height. Adding a page anchor at this point to lead down to the new
> >    Accessibility Concerns section would likely be helpful to folks
> exploring the spec. It could read:
> >
> >    "See Accessibility Concerns for additional details."
> >
> >    Also, please add the label `a11y-needs-resolution` to this issue.
> >
> >    <end suggested comment>
> >
> > ***Action to Take***
> >
> > This CfC is now open for objection, comment, as well as statements of
> > support via email. Silence will be interpreted as support, though
> > messages of support are certainly welcome.
> >
> > If you object to this proposed action, or have comments concerning this
> > proposal, please respond by replying on list to this message no later
> > than 23:59 (Midnight) Boston Time, Wednesday 5 May.
> >
> > NOTE: This Call for Consensus is being conducted in accordance with the
> > APA Decision Policy published at:
> >
> > http://www.w3.org/WAI/APA/decision-policy
> >
> > Janina and Becky
> >
> > --
> >
> > Janina Sajka
> >
> > Linux Foundation Fellow
> > Executive Chair, Accessibility Workgroup:     http://a11y.org
> >
> > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> > Chair, Accessible Platform Architectures      http://www.w3.org/wai/apa
> >
>
> --
>
> Janina Sajka
> https://linkedin.com/in/jsajka
>
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup:       http://a11y.org
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Co-Chair, Accessible Platform Architectures     http://www.w3.org/wai/apa
>
>
>

-- 
*John Foliot* | Senior Industry Specialist, Digital Accessibility

"I made this so long because I did not have time to make it shorter." -
Pascal "links go places, buttons do things"