Transcription of BADCamp presentation available at https://archive.org/details/BakeAccessibilityIntoYourProject

gistfile1.txt

Kevin Miller:	OK, how many people here are accessibility activists? People who work with people using assistive technology. Okay, a handful? 15%? How many of you consider yourselves developers? People who work with JavaScript, PHP, stuff like that? Anything else that I missed in terms of the category, I probably missed several. Designers, themers, okay. You guys are important too. What we’re going to talk about today, I don't think I have to tell this group what accessibility is; but just to give an understanding of the spectrum of what accessibility is and where we are today and I’m coming from a Higher-Ed perspective where we tell our users, before we give them access to our content management system is that accessibility is a legal responsibility.
I.e. Section 508, requires that our website is accessible but it’s also a moral obligation. It’s not just about we’re trying to CYA we won’t get sued. It’s about not being jerks, about being nice to people- or at least trying to be nice to people and sometimes we fail and we acknowledge that and we move on. We also like to say that accessibility is a gradient. There’s not 100%, there can be 100% but a lot of times there is a middle ground where content might be. And we’re always trying to strive but we don’t let ourselves feel bad because we’re not getting 100%.
(Audio Glitch) ....people who have a wide range of visual acuity. For example lived with a woman for many years who required- was not legally blind but still required a vast array of assistive technologies to solve visual acuity problems that were not easily solved by one technology. So a combination of screen magnifiers plus positioning herself appropriately and turning up the contrast on the projector. It’s also about color blindness or low contrast for example. What is this? This is the status report page in Drupal uses colors to visually separate a thing that is good versus a thing that needs attention. For users that with different colorblindness that can’t differentiate this. I will say they use element invisible for [Screeber 0:02:46] users to say this row is okay this row is not okay. 
And some iconography to help with colorblindness but that’s also something that we have to think about as well as people who require high contrast and low contrast environments. Deafness hard of hearing or even users who are watching say a video in a second language, it’s very helpful for them even though this is not isn’t strictly an accessibility thing, to have a readable version of the video available to them. Because it might be easier for them to translate it in their head. Users who have motor skill issues or issues with hover state. Timed interactions i.e. you have to click on this link if you don’t, if your hover intents wrong you lose your status. 
Or for example people who have a temporary condition like carpal tunnel in which they have to use a variety of different devices that slows them down. And also users with different cognitive abilities. Users with epilepsy who might be susceptible to -especially photosensitive epilepsy. There’s over 3,000 cases of people a year who have seizures caused by strobing affects of different lighting conditions. In people with dyslexia who might be helped by font choice and letting between lines, spacing et cetera. 
So, again I think this audience is pretty quick I have a link of listed resources here that I think are very good. Kathryn which is excellent because it also has videos of interviews with people who use assistive technology. And you can get all of these at Kevee K-E-V-E-E dot org. Slash Badcamp. Which gives you this presentation. So the problem right now is that existing tools kind of suck for institutions that want to ensure their content’s accessible. They depend upon reporting and usually they generate reports and those reports have a problem where content’s published and then they get scanned by a scanner and then you get a report a month later. Well that problem has been on your website for a month. 
Also it’s hard for users to be like, “ I have to go back and remember that page, edit it,” And it also - the reports are also useless in an environment where users don't’ interact with the code. For example, a report from Cynthia says [high software 0:05:29] all of this is mumbo jumbo to my users. They don’t know what alt attribute is. They don’t know Compliance Level A Criterion 1.1 is about - they don’t understand what this report is. They don't even know what an alt attribute is. We call it an image description in this specific field. So those reports are not very helpful t them.  And these reports are divorced from the editing environment. Different Drupal sites have different approaches to inserting images. Different approaches to turning a paragraph into a header, linking to a YouTube video. 
So you don't want to report that’s generic. You want a report that specifically talks about what you users can and cannot do in your site. You have a link to a YouTube video; the YouTube video has no captioning. Here’s a specific person you might need to talk to in a group who can help you with captioning. Or you’re not using a- this is a paragraph but you just made it bold, and treated it visually like a header it really should be a header to do that you select it, and in our specific WYSIWYG editor you make a header. Feedback on accessibility should be whetted and built into the editing environment. Because of this, we started a project about 4 years ago called Quail Quail used to be an acronym but I just thing quail are cute so that’s why we called it that. 
So it’s a quailjs.org is the website. It’s a jQuery but also very soon it will so be compatible with [Cherrio 0:07:18] for no JS plug in. And what it allows you to do is take a JQuery object of an element on a page or multiple selectors you can have content area plus a sidebar that a user can control and say, ‘that area I want you to run Quail against is and here’s the guideline that I want to use.’ The guideline can be a pre-defined guideline like wcag2.0 level a or a guideline that’s customized by you. I only want to run these 5 tests because that’s all our users can really do. And it supports a variety of different events that can be called when a test is failed. But the most common one is ‘if a test is failed, give me the element that it failed on and I’ll do something with it.’
Quail also comes with 250 tests. I’m just scrolling through them to make me feel good. So these tests are different kinds so for example the [inaudible 0:08:27] accessibility example and image missing and alt attribute that’s a selector. Meaning we can use a simple JQuery selector to find missing images and alt attributes. It doesn’t require a lot of rocket science. And tests can be grouped into tags so we can categorize them for users. And we also have severity or testability level. So one is this is 100% testable. If it’s missing an alt attribute, it’s missing an alt attribute. A paragraph that is not a paragraph but should be a header, it’s easy to test for that. So another test for things like ‘the reading level of this paragraph is too high for your intended audience’ we have to fudge that a little bit so that it might be a moderate error or a suggestion. 
Something we’re highlighting to the user were you should manually evaluate this. But we can’t actually program adequately to you tell that this is the problem. So Quail is just basically a collection of tests and a framework to group those tests together. Severity, we have severe, moderate, and suggestions. And Quail comes with definitions for WCAG2.0 A/AA/AAA. A/AA/AAA for 1.0 and Section 508 and the way we approach it is that a test might be in one or more multiple guidelines. We have it linked in this document from kevee.org/badcamp. You can see a Wiki article on GetHub of what all the tests are that we provide. And how they align with Sections in each published guideline and what the gaps are. Because there are some gaps. 
Quail is great but it only really works if you’re a developer and know how to integrate it. We started working on the accessibility module basically right after the last Drupal [con 0:10:39]. So it’s available at drupal.org/project/accessibility. And caveat its still in development. There’s no full release. We hope to have the 1st Beta out in a week or so. Big thanks to Jessebeach for helping get the ball rolling on the module and also getting the name space because accessibility was actually moduled make your site look good on WML cellphones from 2005. And had been abandoned and no one got the issue so we were like, ‘can we get that.’ And she really helped out with that. 
What we get the accessibility module is a lot. And it’s available in D7 and D8. There’s a few minor differences but it mostly works unless something happened recently to break it. The core accessibility module just allows you to create tests, customize messages and it also has features integrations so you can export those. And I’m going to do a quick overview and then actually we’ll install this on a site and then I’ll do a tech demo and it will all blow up and then I’ll get embarrassed. There’s a core module that let’s you say, ‘I want to use this guideline and I want feedback for users to say this for these kinds of tests.’ Then there’s a content module that checks content. So you can actually say for a page type in the body field ‘I want to give people feedback on this field’ and the nice thing is it only gives them feedback on a field they can edit. 
So if I’m a user, to use the University example, in the English department I’m logged into the CMS and viewing the History department’s website if I can’t edit that page I'm not going to be shown feedback on accessibility because I can’t edit that page. There’s no reason to. But there are permissions to allow people to view all accessibility feedback regardless of their level of access. It’s nice because it is context sensitive and sensitive to the user.  WYSIWYG module to integrate TinyMCE, CKEditor 3, CKEditor 4. CKEditor 3 and TinyMCE are for the WYSIWYG module, CKEditor 4 works for CKEditor Module. And this I were it gets into that confusing spit about WYSIWYG. We don’t currently support the CKEditor for WYSIWYG module yet but there’s an issue in the queue for that. 
Accessibility reporting actually lets you generate reports. Reports are just done through views so you can make your own custom reports for people. If you want to see content in a list and how many errors there are, where those errors are, you can generate a report. Testswarm integration so if you are a themer or a developer you can basically define those tests in your site or use features to import those tests. Testswarm which is a front-end unit testing tool can actually give you feed back and say, ‘here’s how much percentage of your site’s accessible.’ We actually use this on Drupala11y.org, which is probably going to load very slowly. We build DrupalA every night. 
We run testswarms against Drupal A Core and w get a number of how many accessibility problems there are, where the theme is that that problem was, what item it was and what element called it. And how many pages that element pops up in. So that’s all available through testswarm integration. Finally accessibility themer which is like Devel Themer, if any of you have used- the theme people have used that. It’s also another semi-transparent thing that floats on the bottom of the page. When you turn it on instead of accessibility content just giving you feedback on a portion like the content. This gives you feedback on the entire page. So you can have some tests and as you’re working get feed back in-line. Let’s go ahead and do a demo. 
I have a website here which is the best website in the world. We’re doing pretty good on time. Are there any questions before I do this? I think I went maybe a little fast? Okay. I just created one piece of content and I'm going to – I’ve enabled the accessibility module which is kind of the core module that there’s all depending on and I’m going to enable WYSIWYG and Content Accessibility for now. So the first thing we can do is under Configuration, there’s a new Accessibility section.  One is Accessibility Test and the other’s rules about content accessibility. So first I'm going to enable some tests. Because we don’t just willy nilly start showing people feedback we want you to add tests that you think apply to your site. 

Initially I go there’s no tests that are found yet, so I can import some tests and these are all tests that are provided by Quail Later on I’ll show you how to developers can find additional tests that they’d like. We’re starting to work on this for tests that are really Drupal-specific like ‘you used element invisible wrong’ or ‘you should use element invisible button. 'In order to input tests, I can search m guideline and say, ‘show me tests that align with one of the publish guidelines.’ I can go by category. This is one of my favorites. You used an acronym and you didn’t mark it up with the "abbr” or “acronym” tag. So, I am going to add this test to my site. So I just import it. And let’s go ahead and find some others so I’m going to look for any test that's considered severe. 
Here’s all the severe errors I'm just going go to look for the paragraphs, ‘paragraphs must not be used as headers.’ You’re making a paragraph a one line paragraph bold and alts, because why not? Unfortunately we still have tests for things like area elements for image maps but you’d be surprised- image elements must have an alt attribute. I’m going to import those 2 tests. If you import a lot use Batch API so that it will handle it. And test are Drupal 7 or Drupal 8 entities. So that means you can manage fields on tests and there’s not multiple test types of those single bundle entity. But you can add addition fields in here like maybe an image field with screenshots for your users or a link to a YouTube video to help them fix that problem. 
So that’s nice. You can customize how tests are rendered. But by default they come with standard error description which this this text area where you can describe the problem. So if I click on the test tab or the default page when you click accessibility from configuration, these are all my tests. I can deactivate tests if I want to keep their configuration around but not show them to users. I’m going to go ahead and edit the image elements must have an alt attribute. And I can customize- there’s a default message which comes in and anybody who would like to help us with the default message in my butchering in the English language would be more than appreciated. It’s all in a profile so it’s easily translatable. 
I can change it from instead of ‘image elements must have an alt attribute’ to ‘dude, did you not learn anything in the CMS training?’ So I could deactivate this test if I’m working on it and I don’t want to show it to my users. The description I will say, I’m so embarrassed, click here, never make a link. “You should know better.’ Okay. We actually have a test that says, ‘you said click here’ or other suspect links so. It would have caught me! Now I have a test called, “dude, did you not learn anything in the CMS training?’ So I’ve defined my test and the next thing I need to do it tell it, what pieces of content do you want to test.
I'm just going to pop over to Admin Structure, Content Types and I’ll Manage Fields on Articles so any- we don't bother checking accessibility on an image field because there’s no mark up in that field. So it’s any field that has mark up, which by default is a text area or long text in summary field. But there is an API if you have custom field definitions that accept mark up, you can say this field can also have accessibility turned on. So I'm going to edit the body field of articles and there’s a new ‘check this field for accessibility’ checkbox. I can check it. And there’s also options, this doesn't work yet, where you can even say disable the submit button if an error exists in this field at this level.
If there’s any tests that are marked with ‘severe’ in that field. It will put a message above the submit button and disable it. The problem is that we’re trying to make the UI that’s actually accessible for that kind of feedback. So I'm going to save that configuration on my body. And finally under Config, Accessibility in Content, I can change a few user interface settings. I can say automatically check a page when a user with appropriate permission views it. I can show a toggle for users to turn that feedback on and off and I can even customize the message for that toggle so ‘turn me on’ ‘turn me off’ or ‘check this page’ or what have you.
Now if I go Home, you’ll see I have an image with no alt attributes so I click it it says ‘ Dude, did you not learn anything?’ and here’s a paragraph ‘paragraphs must most be used as headers.’ And we’ve done a lot of testing on should be use popovers? We’ve kept the interface of having a console at the bottom just because you might have multiple errors with the same element. And in our AT testing this was the most appropriate easy to mark up with [our variables 0:22:42] and users really liked this option. So I can then hide the tests and then turn them back on if I’d like to. 
Speaker 1:	Which module is that that gets you the –
Kevin Miller:	Content Accessibility   - actually the accessibility module itself has those interface tools because it’s used in other places. But the content accessibility is the one that let me say ‘ body fields check them for accessibility tests.’
Speaker 1:	Is it the one that put that thing up there? Like at the bottom.
Kevin Miller:	Yea, so it puts that thing at the bottom when you click a element with an error and it also highlights the element you’re looking at with another icon. 
Speaker 2:	 So when you have it set to test certain fields how does the program know-
Kevin Miller:	What it basically does is I am too tired to remember the exact code, but when fields get rendered I say, ‘does the field setting have that turned on?’ if so, it just applies an extra class in a wrapper around that field. And Quail just says, ‘dollar dot accessibility content check’ and it checks anything with that class.
Speaker 2:	Okay.
Kevin Miller:	Yea. So the field is just getting an extra classify to it and then Quail- the accessibility content module just says ‘Quail check any element with this class applied to it.’
Speaker 2:	 So if you’re in a theme and you redo all the fields and output like you remove all the wrapper mark up-
Kevin Miller:	-it will still. Because it’s using an alter hook it will still put its own wrapper around it. Because it puts a – I’d have to look back in the code – but it actually comes in after all of that.  
Speaker 2:	Okay.
Kevin Miller:	Yea. If you’d like later we could open up Sublime and look. That’s great because a user can get feedback this also works if you’re listing content in views or whatever it doesn’t really care. And also you’ll notice when I click this, I see also the status and the machine name of this test. I can disable those by going to Accessibility, Accessibility Tests and Manage Display. And there’s a display mode - I can change the default display mode or there’s a display mode just for that console. You could have some fields that are really only for your internal team to read. Now, let’s go ahead and integrate WYSIWYG integration. I’m going to go my- on this site I'm just using the straight CKEditor module. 
So ender Content Authoring and CKEditor, I’m going to edit my profile and under Editor Appearance, add the, there’s little check box button that I’m going to add. That’s all I have to do. Now if I go home, go to my article an edit it, there’s a check box I check it, I get the same interface. When I click it uses whatever motile API even though 10EMC’s motile API is really terrible, the motile API for CKEditor is pretty good and uses whatever the editor’s motile API is to show them feedback. I could say for example in this paragraph say, ‘Creatures that live in a unicorn’s forest, learn a little...”I’m going to make ‘magic’ an acronym-
Speaker 3:	Now are you able to hide the machine name in that?
Kevin Miller:	Yea, you would use the display settings for accessibility tests.  I should probably make it disable that my default. It doesn’t make sense. So now, when I check I see it says, ‘hey this paragraph has an acronym, you should probably fix that.’ And again we can customize this to say, ‘to fix an acronym in CKEditor select it and click the acronym button.’  So that’s WYSIWYG integration. Now –
Speaker 4:	Can you get the same enforcement in terms of they can’t save if –
Kevin Miller:	That’s the thing we’re dealing with right now is handling because of the way that- especially TinyMCE unfortunately but also CKEditor 3 inserts content into its parent text area, and capturing the event handling around that is a little bit tricky. So those are kind of the barriers. In those situations we might end up doing something like, checking just when the user hits Submit because we just have no other- if we do it on- there’s just not a really good event that we can look at in these WYSIWYG editors. Where we could preemptively prevent the user. But we could do it, the user clicks the button, then we check, then we say ‘sorry you can’t. Which is not the best solution.’
Speaker 4:	I’m guessing this might require something like an accessibility workbench moderation module. But I want them to be able to save drafts [crosstalk 0:28:07] publish.
Kevin Miller:	Yea, right now it’s whatever the submit element is. But I think those are things that we still need to work on. And to be honest, I’m thinking that that preventing submit thing will probably just not make it into Beta because I rather it not block [inaudible 0:28:28] so we can do it right. Let’s go ahead, I’m just going to disable- just so we can see how it looks. I'm going to enable Theme Accessibility for themers and I'm going to jump over to the page.tbl file of [bartic 0:28:56] because I hate [kittens 0:28:59] and I'm going to delete the alt attribute from the icon on top of the page. Because I’m both inserting accessibility problems and hacking core, that’s double the fun. 
So now, I see an Accessibility Theming check box in the lower right hand corner, I put it on the lower right because [inaudible 0:29:26] is on the lower left. When you check that it doesn’t check just one area, it checks the entire page including content. So I get things like ‘hey, again there’s an acronym in here’ also ‘there’s a image missing an alt attribute.’ It’s basically the same approach accessibility theming just checks the entire page instead of just one small piece of the page.
Speaker 5:	I’m sorry I missed when you get the two messages, both messages on the [inaudible 0:30:04]
Kevin Miller:	So this [crosstalk 0:30:06]. That’s pretty much all that module does. And again it’s just using whatever tests you defined in your site. You can export tests as features so if you want to put them into like a dead environment for your themers you can do that. Where are we? 1:30. Let’s go ahead and do reporting which of course I didn’t install views on this so... we’ll see how fast the wireless is. Look at all my stuff. Okay, so I’m going to go ahead and enable the reporting module. Accessibility Reports. Turn off the theme one. So now the one problem is because Quail runs on the browser, it’s only going to check content that users look at. So if you have a problem on the page an no one actually goes and looks at the page, then you won’t get any feedback on that page. 
But other than that, what happens is when a user views any field where you have said ‘put this field into accessibility reports’, I’m going to go the body field of my article content type. ‘Report on accessibility problems in this field,’ so you might tweak reporting to be one field and not another. Whenever a user views content with that field – there’s a little Ajax column on the back to say ‘hey server these are the problems. That I’ve found.’ We’re just basically using the user’s browser to test that for us. There is a default view called accessibility report, you can feel free to clone this and customize it. And now I see that here’s a report, there’s one page with one field and there’s 3 different accessibility tests. There was one error one error and zero errors for this one.  
So that’s one way to approach it. But since it’s all views and relationships and views, you can customize this. Do aggregation, et cetera. And the way that it determines if its going to even make the user do that or not, there’s a permission for those users. You can say ‘give anonymous users the permission to report back accessibility problems.’ And therefore when your anonymous users are viewing content, you’re also checking your content. Yes.
Speaker 6:	This is one of those things I’m not sure it’s legally in there but there doesn’t seem to be any thing that’s a good row header in this table. My understanding from the w3 was that as long as the mark up’s correct it’s fine. But if you’re having a screen reader, if you’re on the 3rd row and you’re having the screen reader read the title for that row and well it’s the same as the title for the 2nd row, how will they distinguish between the two rows?
Kevin Miller:	You mean the title “last unicorn” under this title?
Speaker 6:	No no. I mean in the Severity column you go down from severe to severe and the screen reading was reading “the last unicorn’s” severe and then “the last unicorn’s severe”
Kevin Miller:	 Correct. But these are th-s so we don't necessarily need scoping because there’s only one th and it’s not row scoping going on with multiple combined columns. I agree that this is a total cop out but this is [inaudible 0:34:39] table not mine. Call them, [Merlin 0:34:47] of Chaos. We should do more testing on this. There are ways to do row scoping, which I think might be better because if you have 3 different- well that’s going to confusing too. If you had this be a row header it would make any sense. Then you’d say severe, you’d hear the word, you could use the key command to check the table header and be like what column am I in severity and then jump over and see which field.
Speaker 6:	 I was thinking like maybe you’d have “the last unicorn” being a row that goes all the way across. And then next row, the first cell would be “dude, did you not learn anything [crosstalk 0:35:33] do that in views?
Kevin Miller:	Yea you would use grouping. 
Speaker 6: 	That’s true.
Speaker 7:	Thank you.
Kevin Miller:	Alright. So at this point, I think we should probably- I probably skipped over something that somebody wanted to talk about.  Any questions? We have about 10 minutes time.
Speaker 8:	Well, I had a couple of questions the first one is this is great and I’m doing to definitely use this but when we don’t make sites for government entities but if I were working for a government entity would you suggest that [inaudible 0:36:13] also? Or are you suggesting only use this for...what-
Kevin Miller:	No.
Speaker 8:	-What would your whole toolbox –
Kevin Miller:	Our approach to that, I am the first to say I'm a terrible screen reader user. I’m primarily uncomfortable with Chromebox and with Jaws I'm always like, my the time my finger gets on the keyboard I'm completely confused. But we do actually have a person who is a AT tester is she is extremely proficient in a variety of existing technologies. The way we approach it and originally this was in Drupal 6 it was the accessible content module. We only care about content because our approach was we should have as many automated- when you have 300 authors, this is our situation, 300 authors, 15,000 pieces of content and nobody funded to review any of that...
...And even if they could people could just ignore them, reporting doesn’t work and you really need to automatically give them feedback. Content’s a little bit easier to do automated testing on. So let’s do this automated testing to give our users feedback or even if they ignore it, they’re getting that learning experience. That’s actually how I learned to finally spell the world ‘received’ right. Was the red underline. So do that so then your team can focus on making sure you have appropriate land marking. Making your theme as accessible as possible. Investing time into real human AT user testing in a variety of contexts and spaces.  So you can say, our theme our user interaction all the elements that our authors can’t screw up, mostly, are as good as we can get them or we are very comfortable with them.
And even though this isn’t a solution for everything, use the accessibility module to give content authors feedback to help drive them. And it should be used in combination with appropriate WYSIWYG selection, appropriate filters. For example we still use a filter that does WYSIWYG input format that says ‘if the image is mixing an alt, even if it somehow makes it through, just remove it.’ And the author’s like, ‘Ahh! My image is gone!’ And all this drama comes. It should be used in combination with a variety of other tools and approaches.
Speaker 8:	We had [inaudible 0:39:01] authors that will just let you know they make the same mistakes. It’s nice to hear if someone else has the same problems [inaudible 0:39:08] would you recommend for someone who has doesn't have someone on staff, are there 3rd party testers that you go to if you were really serious about it and had to-
Kevin Miller:	Yea, and there are consultants that do this type of thing. I haven’t had to be in the market for that for a while but I'm pretty sure there are some other user testing services out there as well. Or looking at the community and saying, ‘hey does anybody know?’ Sometimes I’ve heard of people volunteering or users who were saying I’m frustrated with your site’ engaged as ‘hey can we pay you to not only fix that problem but help us as well.
Speaker 8:	Thank you.
Kevin Miller: 	Mmhmm (affirmative). Yes.
Speaker 9:	I have to say thank you very much it’s way cool. I’m looking – is there any kind of tool that I can review say review all the images on the site and look at whether their alt tags are appropriate or not?
Kevin Miller:	Yea, so having that sort of ‘give me a list of all images, the pages their on, and the alts that’s next to them?’ 
Speaker 9:	Yes.
Kevin Miller:	That's a very commonly requested feature. The answer is not yet. We can maybe think about putting that into the reporting module to say tease out the image and then put that into a different cell in the table and we can report on it. But right now it’s been more about –we have this loose framework. Quail is [inaudible 0:40:45] Drupal and get something and then that would be a more Drupal-specific solution. That is something that a lot of people have been asking for.
Speaker 9:	Thank you.
Kevin Miller:	Mmhmm (affirmative). Yes.
Speaker 10:	Are there tests in there for poorly formed tables?
Kevin Miller:	Yes, there is a ton. For example if you don’t have table headers or you have- there’s a lot of [heuristics 0:41:14] that look at things like, you bolded the first cell in a row, you are probably trying to mean that that cell was a header that was scoped to the row. So let’s look at that and see should it be [inaudible 0:41:30]. And also multiple table headers with different call spans. They’re also tests to see if somebody is using table as layout, which is a very interesting one that took a while to get right. But it’s pretty good and there’s 600 700 test files that are included with Quail to look at all these things and we keep adding more. Yea.
Speaker 11:	So this works when you install it on the server you want to test on, and that’s the only place you can test that. That you install it on the server that you’re testing on?
Kevin Miller:	Yea, you have to put in your Drupal site
Speaker 11:	Okay so it can’t go out and find another Drupal server…
Kevin Miller:	You can’t ghost scan at other servers – so really quick because we 3 minutes out- there were 2 things that I’d like to touch on. So first, how you can help. You’ll never hear a module maintainer say that maybe. ‘File issues, I want more issues.’ And ‘break things.’ Some of these are going to be Quail issues not the module like false positives we’re always looking at false positive use cases. But we also have a really exciting future where Quail has a new project called Cheney because that’s how we name things. Cheney is new user face interface for Quail that I think is pretty exciting and that will be coming out soon as well as Covey.io which Covey is what you call a group of Quail that’s for people who are unfortunate enough to not use Drupal to do kind of the same thing for a site. 
Build kind of a package of Quail with tests and enter one line of JavaScript and then it can figure out where your content is. And no Nodejs support which dovetails into what you were talking about. So the dev branch of Quail right now is almost ready to be rolled into something that can be built not only for jQuery but also Cheerio and you can us that and know Nodejs to test another server. But it would have to be node, just because it’s JavaScript.