<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Justin,<div><br></div><div>Thanks for the info. The Wordpress StackExchange site did far better with only 2 reported errors: <a href="http://weba.im/219">http://weba.im/219</a></div><div><br></div><div>As always, an an automated eval does not really get the job done in regards to assessing accessibility, since many tests cannot be automated. Just thought that the accessibility of the platform would be important to keep in mind as one of the factors going into the decision.</div><div><br></div><div>Thanks,<br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><span class="Apple-style-span" style="font-size: medium; "><span class="Apple-style-span" style="font-size: 12px; "><div>Everett Zufelt<br></div><div><a href="http://zufelt.ca">http://zufelt.ca</a></div><div><br></div><div>Follow me on Twitter<br><a href="http://twitter.com/ezufelt">http://twitter.com/ezufelt</a><br><br>View my LinkedIn Profile<br><a href="http://www.linkedin.com/in/ezufelt">http://www.linkedin.com/in/ezufelt</a></div><div><br></div></span></span></div></div></span></div></span></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On 2011-01-31, at 5:44 PM, Justin Ellison wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Everett,</div><div><br></div><div>I have no idea what control would be given as far as presentation, but to be fair the site you tested isn't what will become the StackExchange site. It's more appropriate to run your WAVE tool on <a href="http://wordpress.stackexchange.com/">http://wordpress.stackexchange.com</a> or another real StackExchange site.</div>
<div><br></div><div>Justin<br><br><div class="gmail_quote">On Mon, Jan 31, 2011 at 4:16 PM, E.J. Zufelt <span dir="ltr"><<a href="mailto:lists@zufelt.ca">lists@zufelt.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word">I've only been casually following this thread, but I thought I'd chime in on accessibility.<div><br></div><div>Using the WAVE accessibility evaluation tool I found at least 70 errors on the URL posted in the below message. The results can be seen at <a href="http://weba.im/218" target="_blank">http://weba.im/218</a></div>
<div><br></div><div>Now, it is possible that not all of these are true errors, the tool can give false positives and false negatives. However, the number was large enough for me to not bother manually assessing the page (something required even when using an automated tool.</div>
<div><br></div><div>This brings me to my point. While we do not have a perfectly accessible d.o, we at least have the ability to improve accessibility problems when they are noticed. I doubt we would have the same freedom on an external service.</div>
<div><br></div><div>Now, I am not saying that this means that we should definitely not use an external service, but this should be given appropriate consideration when making decisions about how to best implement a solution for our inclusive community.</div>
<div><br></div><div>Thanks,<br><div>
<span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="word-wrap:break-word">
<span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="word-wrap:break-word">
<div><span style="font-size:medium"><span style="font-size:12px"><div>Everett Zufelt<br></div><div><a href="http://zufelt.ca/" target="_blank">http://zufelt.ca</a></div><div><br></div><div>Follow me on Twitter<br><a href="http://twitter.com/ezufelt" target="_blank">http://twitter.com/ezufelt</a><br>
<br>View my LinkedIn Profile<br><a href="http://www.linkedin.com/in/ezufelt" target="_blank">http://www.linkedin.com/in/ezufelt</a></div><div><br></div></span></span></div></div></span></div></span></span><br>
</div><div><div></div><div class="h5">
<br><div><div>On 2011-01-31, at 4:57 PM, Josh Koenig wrote:</div><br><blockquote type="cite"><div>Stew,</div><div><br></div><div>Thanks for starting this thread. This is important stuff:</div><div><br></div><div><a href="http://area51.stackexchange.com/proposals/2978/drupal-answers" target="_blank">http://area51.stackexchange.com/proposals/2978/drupal-answers</a></div>
<div><br></div>I want to put my support behind this proposal and explain my thinking in doing so.<div><br></div><div>The Drupal community is already growing faster than Drupal's infrastructure can easily support. With the release of D7 and all the other associated projects getting off the ground, <a href="http://drupal.org/" target="_blank">drupal.org</a> is increasingly often a bottleneck or blocker. We have wonderful hosts from OSUOSL, but the human resources needed to develop, maintain and manage our own infrastructure (which is a 24x7x365 job) are limited.</div>
<div><br></div><div>We have to pick our battles. I much would rather see energy, effort, attention and money poured into continuing to improve our git and module infrastructure — which is much more deeply intrinsic to the health and future of the project — and accept that even though we *can* build our own StackOverflow (@eaton proved this already) that doesn't necessarily mean it's the best use of limited resources, or the best thing for the project.</div>
<div><br></div><div>Drupal can theoretically/technically solve a lot of its own problems, but I think we often suffer from a "not built here" prejudice as a result. In the realm of getting good quality answers to Drupal questions out to the most people possible, I can't see how a StackExchange site would do anything but help. I would love to see the community embrace something really cool and useful from the wider Internet as a way to promote the project.</div>
<div><br></div><div>Finally, I should say that I *do not* think a StackExchange answers site replaces anything. It's not an issue queue, and it's not a replacement for the dialogue that exist in the forums. I would say it's a new resource, something that can help the 10s of 1000s of people who will be trying to wrap their mind around Drupal in the coming year. </div>
<div><br></div><div>Cheers</div><div>-josh</div>
</blockquote></div><br></div></div></div></div></blockquote></div><br></div>
</blockquote></div><br></div></body></html>