- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Mon, 01 Nov 2021 15:43:54 +0000
- To: 'WCAG' <w3c-wai-gl@w3.org>
- Message-Id: <em3b0ded84-6f76-44f6-bd7e-73c34347c066@motoko>
I agree that the square brackets around the normative references act as a non-colour identifier for the links (provided that there's no instances of those brackets appearing around words that aren't links). P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke ------ Original Message ------ From: "Matt Garrish" <matt.garrish@gmail.com> To: "'WCAG'" <w3c-wai-gl@w3.org> Sent: 01/11/2021 12:12:12 Subject: RE: Issues with specification formatting >I got some useful information on where to take the respec issues last >week at TPAC, but I’m curious if anyone here has an opinion about >whether the normative and informative links in W3C specifications fail >the use of color SC? This issue was raised in our horizontal review >here: https://github.com/w3c/epub-specs/issues/1837 > > > >My understanding is that the use of brackets around these should be >sufficient to identify them, so I don’t see the need to raise this as >an issue, but I’d be interested to hear if anyone disagrees. > > > >Matt > > > >From: Matt Garrish <matt.garrish@gmail.com> >Sent: October 21, 2021 9:21 AM >To: 'Hidde de Vries' <hidde@w3.org> >Cc: 'Storr, Francis' <francis.storr@intel.com>; 'John Foliot' ><john@foliot.ca>; 'Patrick H. Lauke' <redux@splintered.co.uk>; 'WCAG' ><w3c-wai-gl@w3.org> >Subject: Issues with specification formatting (was RE: Updating 2.x >support materials redesign release) > > > > > this thread is specifically about the redesign of support materials >(Techniques and Understanding), which are (on purpose) in a different >style than the specifications / ReSpec > > > >Thanks, understood! I’m not specifically asking for solutions within >this work (renaming the subject to avoid hijacking that thread), but >it’s more a general question of how this group has handled >accessibility within the documents that respec produces, given that any >issues will likely run the gamut of W3C specifications. Is the advice >just to refile any issues raised in our specs against the respec issue >tracker and assume that whoever needs to weigh in will? Or is there >another process for dealing with accessibility issues? > > > >Matt > > > >From: Hidde de Vries <hidde@w3.org> >Sent: October 20, 2021 5:42 PM >To: Matt Garrish <matt.garrish@gmail.com> >Cc: Storr, Francis <francis.storr@intel.com>; John Foliot ><john@foliot.ca>; Patrick H. Lauke <redux@splintered.co.uk>; WCAG ><w3c-wai-gl@w3.org> >Subject: Re: Updating 2.x support materials redesign release > > > >Hi Matt, > > > >>On 19 Oct 2021, at 16:21, Matt Garrish <matt.garrish@gmail.com> wrote: >> >> >> >> > so is there a conversation about color choice vs. internal >>consistency of design? >> >> >> >>Jumping in from the epub side, it would be very helpful to figure out >>how to deal with accessibility issues in the respec >>output/organizational styles. We should be fixing issues for all >>specifications otherwise we break any hope of conformity of >>appearance/structure. >> > > >Sorry for the confusion - this thread is specifically about the >redesign of support materials (Techniques and Understanding), which are >(on purpose) in a different style than the specifications / ReSpec, >drawing from the WAI website redesign visual styles. > > > >Best, > >Hidde > > > >— > > >Web Accessibility Specialist ・ https://w3.org/people/hidde ・ Web >Accessibility Initiative (WAI) at World Wide Web Consortium (W3C) > > >
Received on Monday, 1 November 2021 15:44:08 UTC