- From: Shane McCarron <shane@spec-ops.io>
- Date: Thu, 14 Jul 2016 08:13:41 -0500
- Cc: Marcos Caceres <marcos@marcosc.com>, spec-prod <spec-prod@w3.org>
- Message-ID: <CAJdbnOAFckoe4CmAdGDkO4dTR1-aRtdQbuX4PnXx=2E8L9T8eA@mail.gmail.com>
BTW I have suggested we also add some a11y checking to this. I don't yet know what that will be. I am asking the APA and ARIA groups for input on it. But I wonder if there shouldn't also be a check for an a11y considerations section. I have raised an issue against specberus to discuss that with the relevant players. [1] Please feel free to comment here or against that issue. [1] https://github.com/w3c/specberus/issues/465 On Thu, Jul 14, 2016 at 8:06 AM, Wendy Seltzer <wseltzer@w3.org> wrote: > On 07/14/2016 02:54 AM, Marcos Caceres wrote: > > Hi ReSpec Users, > +cc PING > > > > > As part of the W3C's transition to TLS docs on /TR/, we've added a > > simple linter to ReSpec to check that the URLs in your `respecConfig` > > are using TLS. > > > > The linter is disabled by default right now. You can enable it by > > adding the following to your `respecConfig`: > > > > ``` > > lint: true, > > ``` > > > > You can access the warnings through the ReSpec pill on the top-right, > > as per usual. If no warnings show up there, you are all good :) > > > > The linter also warns if you don't have a Privacy and/or Security > > Considerations section in your spec, with a helpful link to a > > questionnaire that can help you write such sections. > > Thanks Marcos, that's great! > > --Wendy > > > > > Once the W3C transitions to TLS on /TR/ (in ~2 weeks), we will enable > > the linter by default to help you easily fix such warnings. > > > > Kind regards, > > Marcos > > > > > -- > Wendy Seltzer -- wseltzer@w3.org +1.617.715.4883 (office) > Policy Counsel and Domain Lead, World Wide Web Consortium (W3C) > https://wendy.seltzer.org/ +1.617.863.0613 (mobile) > > > -- Shane McCarron Projects Manager, Spec-Ops
Received on Thursday, 14 July 2016 13:14:38 UTC