<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by J. Renée Beach on Medium]]></title>
        <description><![CDATA[Stories by J. Renée Beach on Medium]]></description>
        <link>https://medium.com/@jessebeach?source=rss-4b72ff6a800f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zDKT-ELV0jw-BalQSPgRzg.jpeg</url>
            <title>Stories by J. Renée Beach on Medium</title>
            <link>https://medium.com/@jessebeach?source=rss-4b72ff6a800f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:43:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jessebeach/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Accessibility (A11y) Rally]]></title>
            <link>https://medium.com/@jessebeach/accessibility-a11y-rally-1951012abc5d?source=rss-4b72ff6a800f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1951012abc5d</guid>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[J. Renée Beach]]></dc:creator>
            <pubDate>Tue, 28 Nov 2017 22:51:16 GMT</pubDate>
            <atom:updated>2017-11-28T22:51:16.189Z</atom:updated>
            <content:encoded><![CDATA[<p>Ramping up on a new codebase takes time. So does gaining mastery in a new field of technology. For a product team, addressing accessibility issues can involve unfamiliar techniques and technology. For the accessibility team, it takes time to gain familiarity with a product’s codebase.<br> <br>An accessibility rally is a focused collaboration between product team members and the accessibility team. In one day, we’ll improve the semantic attribution of a product’s HTML structure — with changes proposed that day — and design solutions to more complex interactive issues. Improvements that might have taken weeks before now take a few days or even hours. <br> <br>What to expect from this collaboration:</p><ol><li>Prior to the rally, the accessibility team will collect a backlog of issues that can be addressed on the day of the rally.</li><li>One to two engineers from the product team will participate for a half or full day collaboration.</li><li>On the day of the rally, we will all write code and propose change. Issues that can’t be addressed the day of the rally will be taskified with a plan for a solution.</li><li>The accessibility team will be available for reviews and follow-up testing.</li><li>Product team members will learn advanced techniques in accessibility development. We will also demonstrate how to test the product in popular assistive technology clients.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1951012abc5d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dealing with focus and blur in a composite widget in React]]></title>
            <link>https://medium.com/@jessebeach/dealing-with-focus-and-blur-in-a-composite-widget-in-react-90d3c3b49a9b?source=rss-4b72ff6a800f------2</link>
            <guid isPermaLink="false">https://medium.com/p/90d3c3b49a9b</guid>
            <category><![CDATA[web-accessibility]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[J. Renée Beach]]></dc:creator>
            <pubDate>Sat, 22 Apr 2017 23:01:51 GMT</pubDate>
            <atom:updated>2017-04-22T23:01:51.555Z</atom:updated>
            <content:encoded><![CDATA[<p>I ran into a situation a while back while build a table grid component. I need to know when focus left the containing grid component. But the grid itself never receives focus. Its cells are focused. In other words, given a cell focused inside the containing grid, when the next focused element on the page was NOT inside the grid.</p><p>Let’s just consider page traversal with the tab key for now. When the tab key is pressed, the following events are fired: keydown, blur, focus, keyup. The keydown and blur events target the element being tabbed from; the focus and keyup event events target the element being tabbed to. I put together a silly little pen to illustrate this behavior:</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fcodepen.io%2Fjessebeach%2Fpen%2FpPbVzy&amp;src=https%3A%2F%2Fcodepen.io%2Fjessebeach%2Fembed%2Fpreview%2FpPbVzy%3Fheight%3D600%26slug-hash%3DpPbVzy%26default-tabs%3Djs%2Cresult%26host%3Dhttp%3A%2F%2Fcodepen.io%26embed-version%3D2&amp;type=text%2Fhtml&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/64619f55d37e298a2d6648657cc94f30/href">https://medium.com/media/64619f55d37e298a2d6648657cc94f30/href</a></iframe><p>When a user is tabbing around cells within a grid, the tabbed from element and the tabbed to element will be contained in the grid. React provides us with a helpful bit of polyfilled behavior here. Ordinarily, the focus and blur events in the DOM dot not bubble. React will bubble these events through its event model. So we can listen for focus and blur events at the root of a component and react to these events fired on its child nodes.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e4adc1dda8835c425c40aee59f4580e4/href">https://medium.com/media/e4adc1dda8835c425c40aee59f4580e4/href</a></iframe><p>The gist illustrates a React Component that returns a div element with onFocus and onBlur listeners. The component has one state property: isManagingFocus. What the component does when it is managing focus is not relevant here. What the gist intends to demonstrate is how we can toggle the value of the boolean state property isManagingFocus based on blur and focus events that the children of the grid component will fire.</p><p>The component should:</p><ol><li>Toggle isManagingFocus to true when an element inside the grid gains focus</li><li>Maintain isManagingFocus as true as long as an element inside the grid has focus</li><li>Toggle isManagingFocus to false when no element inside the grid has focus.</li></ol><p>This behavior is achieved by waiting a “tick” on a blur event before toggling the isManagingFocus state to false. By a tick, I mean the next processing cycle in the main thread. We an wait a tick by using setTimeout to delay the state setting. The blur and focus events will happen in the same tick (under normal circumstances), allowing the component to cancel its reaction to the blur event if a focus event occurs in the next moment and clears the timeout. If no focus event from an element within the grid occurs (if the user has traversed out of the grid component), then the blur event will be processed in the next tick and the grid component will toggle isManagingFocus to false.</p><p>Any time we use setTimeout/clearTimeout to manage order of operations, it feels icky. I freely admit this. It seems like a hack and admittedly this approach is that. But the DOM gives us scant tools to respond to focus and blur events. We’re often left with timing hacks and interpreting secondary effects to understand where focus is on the page and where it’s going to next. If anyone’s come up with a better approach in React to track focus within and across components, I’d love to read about it in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90d3c3b49a9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My biggest takeaway from the second Offline Camp in Santa Margarita, CA — plus toast!]]></title>
            <link>https://medium.com/@jessebeach/my-biggest-takeaway-from-the-second-offline-camp-in-santa-margarita-ca-d0dd930cd02b?source=rss-4b72ff6a800f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0dd930cd02b</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[offline-camp]]></category>
            <category><![CDATA[offline-first]]></category>
            <dc:creator><![CDATA[J. Renée Beach]]></dc:creator>
            <pubDate>Tue, 08 Nov 2016 05:11:31 GMT</pubDate>
            <atom:updated>2017-01-10T17:30:51.200Z</atom:updated>
            <content:encoded><![CDATA[<p>During the midday session of the second day of the <a href="http://offlinefirst.org/camp/">camp</a>, I joined a session to talk about design patterns to express the states of being offline, syncing, etc.</p><p>What are we talking about when we talk about being “offline”? Here’s an example. Imagine you’re on a flight that is about to take off. You visit a web page on your phone — a newspaper site for instance — and as you’re reading, the cabin crew asks you to put your phone into airplane mode. You do this and continue reading your article. The plane takes off and you soon finish your article. You click the next article link at the bottom of the page. What happens? Does the next article load? Are you interrupted with a page that tells you can’t load that resource because you are now offline?</p><p>Well, if the web site developers have implemented offline patterns that pre-load articles and cached them to your device while you still had a network connection on the ground, then you’ll happily navigate to the next article even though you’re in the air and offline.</p><p>Back at the session, my primary concern was contributing to the work to ensure that the group didn’t end up with a purely visual pattern proposal. I wanted the concepts to have a firm semantic foundation that can be expressed in non-visual media as well. From the discussion, we developed 3 concepts that identify areas of semantic relevance for offline experiences.</p><h3>Conceptualizing offline experiences</h3><h4>Freshness</h4><p>Freshness refers to the age of information that is stored on your device. If you visited the newspaper website in our example above, cached some articles and then turn off the network, then those articles will begin to “age” in a sense. Until you turn your network back on and the website can query for new articles or updates to cached articles, your information will become stale. Freshness is relative to the type of information. A newspaper article might become stale after a few hours if the story is currently developing. A Wikipedia article, by contrast, might remain fresh for weeks or months.</p><p>Designers should express freshness, relative to their content types, in the UI. This might be accomplished through indications of <em>last updated time</em> or <em>last synced time.</em></p><h4>Reach</h4><p>The concept of reach describes you’re ability to fetch information to your device. You might reach into a connected external hard drive, or a local LAN network; you might reach into a peer-to-peer or a private virtual network. Most often, we’re reaching out to the internet for information. If the source of information retrieval and the source’s reachable status are critical to user decision making, then those states should be surfaced to the user.</p><p>Several icons have emerged to express this state, such as the cloud with an arrow pointing up into it (an example of reaching into the cloud). In terms of semantics, I proposed the states of: <em>reachable, unreachable, unknown</em>.</p><h4>Assurance</h4><p>We spent a lot of time exploring metaphors to describe the anxiety of not knowing if something you’re writing online has saved. Did it save to my computer locally? Did you save to an online location? If I refresh the tab, will my text disappear? Do I need to press a save button or does save happen automatically?</p><p>We had a difficult time coming up with the term <em>assurance</em>. We explored metaphors of correspondence — sending letters through the mail without knowing if they have arrived; gossip — the pressure one feels to tell a secret and the moment of joy one experiences when the secret is divulge; storage and hoarding — the anxiety one feels when wealth or valuables have accumulated in one place and the dread of disaster and loss builds.</p><p>Ultimately, we decided that the anxiety of loss and release is resolved through assurance that one’s property is safe and delivered. Today, we tend to express assurance through words like <em>synced</em> or <em>saved</em>. Saved is a well known concept and a good one to reuse. In the future, when content might live in multiple places, across distributed networks and at different version points, we will need a richer language to produce a sense of assurance in our users. We did not develop iconography or terms to express this idea beyond synced or saved.</p><h3>Expressing offline syncing to the end user</h3><p>The last design issue we discussed is how to express the ability of a site to cache a site offline and the progress of this activity. We came up with the <em>progress toast</em> pattern. A toast is a notification that rises from the bottom of the screen…like a slice of toast in a toaster! By combining the toast unit with a progress bar, we can express the ability of a site to cache itself offline and the progress of this activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/505/1*Gc2Yhqvx80nuEHIwPI8Prg.png" /><figcaption>A simple illustration of a progress toast notification. The left-side depicts a collapsed toast that indicates 50% progress in cacheing the site offline. The right side depicts an expanded toast. In the expanded area, there is an explanation of what offline access provides and a link to settings.</figcaption></figure><p>Activating the toast bar expands it, providing a space to explain the operation and perhaps link to settings that allow a user to control the offline experience. The contents of the toast will depend on the specific needs of the application.</p><h3>Summary</h3><p>As you are designing your website or web application and thinking about how it will behave under spotty or unavailable network conditions, try framing the problem in terms of <em>freshness</em>, <em>reach</em>, and <em>assurance</em>. How will you express to your users that the content is up to date, safe and available across their network?</p><p>And don’t forget the (progress) toast!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0dd930cd02b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beware smushed off-screen accessible text]]></title>
            <link>https://medium.com/@jessebeach/beware-smushed-off-screen-accessible-text-5952a4c2cbfe?source=rss-4b72ff6a800f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5952a4c2cbfe</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[J. Renée Beach]]></dc:creator>
            <pubDate>Tue, 11 Oct 2016 23:29:52 GMT</pubDate>
            <atom:updated>2016-10-14T17:30:40.779Z</atom:updated>
            <content:encoded><![CDATA[<p>My colleague, Matt King, encounters a lot of friction when using web UIs. Matt uses a screen reader to access the web. A screen reader expresses through speech and sound the text and controls of an interface. He and I work together on the accessibility team at Facebook. Whenever we are collaborating together, we inevitably find little gotchas. Over a few sessions, Matt mentioned that the string of text “Show more reactions” was being smushed together and read as “Showmorereactions”. <br> <br>This is something Matt had noticed before, but it had never been so obvious. For example, the two phrases “News Feed” and “NewsFeed” sound very similar when read aloud. I checked the HTML for the element on my computer and found that the words had spaces between them. We then wondered if the folks who developed this feature had used a character that looks like whitespace, but really isn’t — some exotic HTML entity or something. But the source code revealed normal space. I accessed the node’s text content through the DOM and the resulting string had spaces. As far as I could determined, the spaces between “show”, “more” and “reactions” were there right up to the moment that Matt heard them pronounced by the screen reader.<br> <br>The one detail you need to know about this UI element is that it is not visible on the screen. We use a technique known as “invisible content”. It’s documented here on the Web AIM site: <a href="http://webaim.org/techniques/css/invisiblecontent/">http://webaim.org/techniques/css/invisiblecontent/</a><br> <br>Basically, the technique smushes, clips, de-flows and hides content so that it is only perceptible to assistive technology like a screen reader. Our implementation looked like this:</p><pre>.accessible_elem {<br>  clip: rect(1px 1px 1px 1px); /* IE 6/7 */<br>  clip: rect(1px, 1px, 1px, 1px);<br>  height: 1px;<br>  overflow: hidden;<br>  position: absolute;<br>  width: 1px;<br>}</pre><p>I had a hunch that this little class was the source of the bad behavior. I removed it from the element and asked Matt to test. A moment later he declared it fixed! Next I put the class back and started removing properties one by one to see which one was the root of the issue: clip, overflow, position, height…width. I pulled out the width property and the spaces were present again.<br> <br>Matt and I puzzled over why when a nearby colleague, Brett Lavalla, who had been listening to us debug this issue, offered a suggestion. Try white-space nowrap.</p><pre>white-space: nowrap;</pre><p>He guessed that the zero-width element forced the content to wrap to one word per line. When the screen reader pulled the content of the element to announce it, it received something like:</p><pre>&quot;ShowLFMoreLFReactions&quot;</pre><p>Where “LF” stands for line feed. The line feeds are not interpreted as spaces, so the phrase gets smushed into one long word. The white-space property forces the content to render on one line. We add this one-line change to our accessible text utility class.</p><pre>.accessible_elem {<br>  clip: rect(1px 1px 1px 1px); /* IE 6/7 */<br>  clip: rect(1px, 1px, 1px, 1px);<br>  height: 1px;<br>  overflow: hidden;<br>  position: absolute;<br>  white-space: nowrap; /* added line */<br>  width: 1px;<br>}</pre><p>This is a good example of polish in accessible user interfaces. Was the interaction usable before? Yes, even though the interaction could be difficult and annoying depending on the smushed phrase. In the same way we’re constantly looking to adjust colors, alignment and sizing of our visual UIs to make them more usable, we should always be looking for ways to polish our aural (spoken) UIs to the same levels of quality.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5952a4c2cbfe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quail accessibility testing framework: 2015 project conclusion report]]></title>
            <link>https://medium.com/@jessebeach/quail-accessibility-testing-framework-2015-project-conclusion-report-11285d65d044?source=rss-4b72ff6a800f------2</link>
            <guid isPermaLink="false">https://medium.com/p/11285d65d044</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[es6]]></category>
            <dc:creator><![CDATA[J. Renée Beach]]></dc:creator>
            <pubDate>Mon, 25 Jan 2016 08:15:30 GMT</pubDate>
            <atom:updated>2016-01-25T08:15:30.400Z</atom:updated>
            <content:encoded><![CDATA[<p>So much code, so much change. So what now?</p><p>For Quail, 2014 was <a href="https://medium.com/@jessebeach/quail-accessibility-testing-framework-2014-project-report-d64f7d6275d7">a year of hacking and getting things to work</a>. In contrast, 2015 was the year I finally got the time to refactor. And honestly, it was the year when I was finally able to do this work. I learned at lot of things in 2015: how Selenium works and with Mocha; how Node works, how NVM works…and NPM, Babel, ES6, building CLI interfaces, writing Chai assertion methods…and most of all, <a href="https://github.com/facebook/jscodeshift">code modding</a>. The high level stats:</p><blockquote>1409 files changed, 44576 insertions(+), 25663 deletions(-)</blockquote><p>All in all, Quail got rewritten from the ground up.</p><p>In May 2015, I joined Facebook’s accessibility team. I joined a team of dedicated, talented, and inspiring folks. The accessibility team is located organizationally within the front end infrastructure team. Not only did my real education in accessibility development begin at Facebook, but so did my education in front end infrastructure. I learned how to write code that writes code. And that’s when Quail really started to evolve.</p><p>You can find Quail on NPM under the <a href="https://www.npmjs.com/org/quailjs">@quailjs org</a>. I’ve pulled it apart into three projects:</p><ol><li><a href="https://github.com/quailjs/quail">Quail</a>, the assessments</li><li><a href="https://github.com/quailjs/quail-core">Quail core</a>, the libs that run the assessments</li><li><a href="https://github.com/quailjs/quail-cli">Quail CLI</a>, the command line interface to develop and run Quail</li></ol><p>My intent here is to allow third-party orgs to write assessments and roll them into custom Quail builds. To allow for arbitrary assessment inclusion, Quail is now assembled using module exports and requires. And with this module support, we now also have ES6/7 transpiling through Babel. You can write assessments using the latest JavaScript idioms.</p><p>My hope in refactoring Quail to use modern coding practices is to entice developers to join the project. The web needs an open-source accessibility testing tool that integrates with our development practices. And like anything complex, it can’t be built by a single person.</p><p>In the next round updates, I’ll be focused on the assessments themselves. There are a lot of open issues: <a href="https://github.com/quailjs/quail/labels/new-test">new tests</a> (58) and <a href="https://github.com/quailjs/quail/labels/partially%20implemented">partially implemented tests</a> (17).</p><p>Also, I think it’s time to set up a Slack Channel for Quail, so here’s that :) <a href="https://quailjs.slack.com/">https://quailjs.slack.com</a> It’s a bit lonely in there, so please, join in!</p><p>So, if you’re an accessibility developer or expert, now is definitely the time to get involved. Let’s make Quail useful and usable in 2016 so that we can help developers make the web accessible to everyone!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11285d65d044" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The happy case of pronouns and HTML]]></title>
            <link>https://medium.com/@jessebeach/the-happy-case-of-pronouns-and-html-d0b5f0fbc55e?source=rss-4b72ff6a800f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0b5f0fbc55e</guid>
            <category><![CDATA[gender]]></category>
            <category><![CDATA[html5]]></category>
            <dc:creator><![CDATA[J. Renée Beach]]></dc:creator>
            <pubDate>Wed, 16 Dec 2015 19:32:40 GMT</pubDate>
            <atom:updated>2015-12-16T19:37:39.749Z</atom:updated>
            <content:encoded><![CDATA[<p>The thing about the internet is, we own its definition, expression and message. That’s the royal we, the hard-to-pin-down collective we all together form. I love so much when this amorphous sprite of unity coalesces suddenly to correct an inequality. On Dec 15, <a href="https://github.com/alice">Alice Boxhall</a> noted a disparity in the use of gendered pronouns in the WHATWG HTML spec.</p><h3>Alice Boxhall on Twitter</h3><p>Just did a find in page for &quot; he &quot; and &quot; she &quot; on https://html.spec.whatwg.org/ . 53 &quot;he&quot;, 2 &quot;she&quot;, and the latter refer to a cat and a princess.</p><p>After reading this I thought, “Well certainly this spec must be in a public repo somewhere.” So I found the repo and proposed a Pull Request to swap all the male pronouns for female pronouns. It was done with some good amount of cheek given that some of the changes introduced inconsistent gender pronouns for known historical figures, such as Nero.</p><p><a href="https://github.com/whatwg/html/pull/405#discussion-diff-47692464">Gender refactor by jessebeach · Pull Request #405 · whatwg/html</a></p><p>I wanted to point out just how imbalanced the situation was. Within hours, <a href="https://github.com/foolip">Philip Jägenstedt</a> and <a href="https://medium.com/u/a02b8edf73ed">Ian Hickson</a> had reviewed the Pull Request (and I immediately regretted my cheekiness =D ). The comments they proposed were constructive and much to my delight, the PR itself was greeted with enthusiasm. Hurray internet!</p><p>I promised to review the comments and update the PR later that evening. In those ensuing hours, <a href="https://medium.com/u/ae686741747e">Ⓣab Ⓐtkins-Ⓑittner</a> jumped into the fray and proposed changing the male pronouns to gender-neutral pronouns: they, them, themselves.</p><p><a href="https://github.com/whatwg/html/pull/407">Remove unnecessary gendering. by tabatkins · Pull Request #407 · whatwg/html</a></p><p>And I must say, I much prefer neutral pronouns to gendered pronouns. They (should?) offer fewer contentions for debate and overall, my gender-queer nature just prefers to avoid the issue of gendering where possible and especially in technical documents.</p><p>I closed up my PR and encouraged Tab to reopen their PR, which they’d closed thinking mine, having come first chronologically, had super-position (I assume).</p><p>And there the issue sat over night from my perspective. In the passing time, <a href="https://github.com/zcorpan">Simon Pieters</a> proposed changing the gender pronouns of the “Fisherman” example.</p><p><a href="https://github.com/whatwg/html/pull/409">Change the genders to female in the fisher example by zcorpan · Pull Request #409 · whatwg/html</a></p><p>We ultimately got two commits — <a href="https://github.com/whatwg/html/commit/c3c407eecaaac49e771ce05e43a7fc1a5a92333c">c3c407</a> and <a href="https://github.com/whatwg/html/commit/24ce41625178883da76cb3deccfb8c01644eaa88">24ce41</a> — and a to-be-committed PR — <a href="https://github.com/whatwg/html/pull/409">PR#409</a> , a continuation of PRs <a href="https://github.com/whatwg/html/pull/405">#405</a> and <a href="https://github.com/whatwg/html/pull/407">#407</a> — that begin to correct the imbalance of gender representation in the spec. Representation in academic and technical documents will always involve debate and negotiation. Critically, a community that is willing to acknowledge and act to correct the discrepancies is one that will adapt with our evolving understanding of gender and gender expression.</p><p>I’ve not worked with the HTML crowd before this interaction. My experience has been wholly positive and for this I thank the folks involved. The engagement and respect is truly appreciated.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0b5f0fbc55e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quail accessibility testing framework: 2014 project report]]></title>
            <link>https://medium.com/@jessebeach/quail-accessibility-testing-framework-2014-project-report-d64f7d6275d7?source=rss-4b72ff6a800f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d64f7d6275d7</guid>
            <dc:creator><![CDATA[J. Renée Beach]]></dc:creator>
            <pubDate>Tue, 30 Dec 2014 02:58:06 GMT</pubDate>
            <atom:updated>2015-02-03T04:14:01.800Z</atom:updated>
            <content:encoded><![CDATA[<h3>Quail accessibility testing framework: 2014 project conclusion report</h3><p>What we achieved and where we’re going next</p><h2>Project report</h2><p>Late in 2013 the <a href="https://github.com/quailjs">Quail</a> project and the <a href="https://www.kinggemeenten.nl/">Kwaliteits Instituut Nederlandse Gemeenten</a> (KING) organization of the Netherlands joined together to improve automated testing of accessibility support on web pages. KING brought resources and knowledge to Quail and without their support, this project would not have improved at such a rapid pace.</p><p>KING have pledged to continue their support of Quail and to that end have hired a full time developer, <a href="https://www.linkedin.com/in/wilcofiers">Wilco Fiers</a>, to work on Quail core and tests.</p><p>The volunteer team of the open source Quail project are also fully invested and excited to see this work evolve into the de facto testing tool for accessibility on the web.</p><p>We’ve been hard at work over the past 11 months on numerous improvements. Here is the high level view of that work.</p><h3>KING’s contributions</h3><p>The <a href="https://www.kinggemeenten.nl/">Kwaliteits Instituut Nederlandse Gemeenten</a> (KING) has been instrumental funding development of Quail through 2014. Our collaboration began almost a year ago in the early winter of 2013.</p><p>In 2014 KING funded <strong>785 hours</strong> of development among 6 developers. We’d like to thank <a href="https://www.linkedin.com/in/peterdroogmans">Peter Droogmans</a> and <a href="https://www.linkedin.com/in/theodorebiadala">Théodore Biadala</a> for their contributions to the project as most excellent hired muscle!</p><p>They incorporated Quail into their Simply Accessible (‘Gewoon Toegankelijk’ in Dutch) platform. This platform comprises an accessibility tool and monitor developed by the Dutch government to help government organizations work on improving the accessibility of their website. Simply Accessible is an initiative from the Quality Institute of Dutch Municipalities and the Ministry of the Interior and Kingdom Relations. The project was lead by the Quality Institute. During the build (16 months), the project team consisted of 6 team members, including the Quail developers.</p><p>In the last quarter of 2014 the tool was launched as part of an accessibility campaign. Over 200 Dutch government organizations participated. In a period of a few weeks more than 1,000 webpages have been tested with Quail.</p><p>Since January 2015 Quail — as part of the Dutch accessibility monitor — is being used to test Dutch government websites on a large scale. Currently over 70,000 pages a day are being tested.</p><p>In addition to funding developers, KING provided structure and direction for feature development. The shift towards analysis by WCAG Success Criteria was championed by the KING team.</p><p>KING facilitated a collaboration with the CKEditor team and we’ll see in 2015 an integration that brings Quail into this popular client-side content editor for real-time accessibility assessment of content. The plugin has been made available to all Dutch government organizations for free. (2,000+ organizations) — a generous donation by the CKEditor team! In march a campaign will be launched to help organizations implement the plugin.</p><p>KING also funded a week-long co-working opportunity for Jesse Beach in The Hague. We had the opportunity to plan out the 2015 (look for the upcoming post!) roadmap for Quail!</p><h2>What we achieved</h2><p>Much and more has changed under the hood in Quail from version 2.1 I like to look at <strong>git diff —shortstat</strong> to give me a sense of the gross code changes over time:</p><p>1138 files changed, 23828 insertions(+), 42954 deletions(-)</p><p>Many of the deletions are simply third-party dependencies moved out of the repository in favor of including them during a build step. And yes, we moved quail to a build model using grunt in order to run necessary setup tasks during installation and development.</p><p>In terms of new tests we addressed 28 issues corresponding to WCAG Techniques. We also have support for evaluating 60 WCAG Success Criteria. In practice, we have associated tests with individual Success Criteria and we report the results of those tests against the criteria. We have not yet implemented a targeting, wholistic evaluation of the criteria. This will be addressed below in what the project failed to achieve and why.</p><p>In addition to new tests and evaluative constructs, we improved the underlying architecture of the core Quail code. Previously, the Quail architecture had been modeled after a jQuery plugin. Much of the code was procedural and the execution synchronous. State management was achieved through simple data structures at high levels in the application.</p><p>Although Quail is not yet entirely divorced from its dependency on jQuery, we have moved much of the test processing into encapsulated classes that manage state and execution in smaller chunks capable of running independently and asynchronously.</p><p>A large part of the work went into building a test running tool that utilizes Phantom.js to mock a browser and evaluate web pages against Quail tests. Quail produces a lot of data and we had to overcome scale issues with Phantom and well as invent ways to reduce the data output without sacrificing fidelity.</p><p>So what does Quail give you now? We run 212 tests and evaluate 60 Success Criteria against a web page in under a second. The test results are written in out to file in JSON format that can then be further processed.</p><h2>Missed goals</h2><p>At the outset of the Quail/KING collaboration, we set a goal of filling test coverage gaps in Quail. Most significant were media tests. Now, it turns out that existing tools like headless browsers have as of yet poor support for modern media technology like HTML video and audio. So our ability to test these features is limited. We also simply ran out of time. Many of the architectural improvements took longer than anticipated as they are wont to do in software development.</p><p>We also learned much and more about the WCAG Success Criteria: namely, they are really difficult to evaluate. I lovingly refer to their evaluation as the “logical combinatorix of Success Criteria” . Each criteria is like a word problem that must be unraveled and address idiosyncratically. We spent two months trying to do this for just 3 of them. Ultimately, we had to take a step back in the interest of finishing the project and just return test results for cases we associated with each criteria. This, to me, is a very high level evaluation as it provides a kind of spectrum of compliance for the criteria. But it does not, in the strictest terms, evaluate the criteria as they are meant to be.</p><p>Going forward, I think Quail needs to bring feedback to the guideline authors and find a way to improve the text of the guidelines in order to make them more machine evaluable. I’ve take steps to find and meet the right people to start these conversations.</p><h2>What’s next for Quail</h2><p>On the whole, I am incredibly impressed with how much important and significant work we finished over the past 9 months. We are a small team working mostly in off-hours. Building a testing suite, as I have learned, is not a simple undertaking. The core value of Quail is its test suite and we have come a long way to exposing those tests to clients that wish to implement them. Of course, we still have big strides to take to get to the point of making Quail an integral component of a continuous integration chain.</p><p>So what’s up next for Quail?</p><h3>Documentation</h3><p>Development greatly outpaced our ability to keep documentation up to date. Honestly I was scrambling most weekends just to get Phantom to run 250 asynchronous tests and get the megabytes of data out of the runs and into files without the whole thing imploding.</p><p>But now that Phantom.js and other scale issues are tamed, we need to go back and update our docs so that others can begin implementing the improved version of Quail.</p><h3>CKEditor integration</h3><p>We are in early discussions with the CKEditor team about integrating Quail tests into their editor through the plugin system. Stay tuned for the exciting developments to come!</p><h3>Command line support</h3><p>I want Quail to be a developer tool and to that end, we must make it work within the tools chains that developers prefer. I already have workarounds locally for running Quail from a command line. I will soon be making these available through the repository to enable faster testing and better integration with other projects.</p><h3>A Quail sprint in Boston!</h3><p>Automated accessibility testing is the only way we are going improve access to our products’ features and information. Given the complexity of the systems we are building, we cannot rely on human quality assurance testing to catch regressions and gaps in our code.</p><p>To get there faster, I want to leverage the knowledge and expertise of any and all coders who can lend time to this project. I believe in the open source model; I’ve spent years developing open and free code. Now it’s time to expand the Quail project to more contributors.</p><p>In the coming months, I will be organizing a weekend-long sprint in Boston to bring together developers, designers and accessibility experts to push this project forward by significant leaps. Look to this Medium account for the announcement!</p><p>As always, the state of the project is best represented in our <a href="https://github.com/quailjs/quail">repository</a> and the <a href="https://github.com/quailjs/quail/issues">issue queue</a>.</p><p>Help us build a more accessible web for everyone!</p><p><strong>Hero image credit</strong></p><p>van Swanevelt, Herman (c.1600 — 1655), 1645, <strong><em>Italian Landscape with Bridge</em></strong>, <a href="http://commons.wikimedia.org/wiki/File%3AVan_Swanevelt%2C_Herman_-_Italian_Landscape_with_Bridge_-_Google_Art_Project.jpg">via Wikimedia Commons</a></p><h3>Edits</h3><p>February 2, 2015 — (Jesse Beach) Added additional details to the <strong>KING’s contributions</strong> section.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d64f7d6275d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quail — Automated accessibility testing framework; Second milestone report]]></title>
            <link>https://medium.com/@jessebeach/quail-automated-accessibility-testing-framework-second-milestone-report-b5d8df4452e?source=rss-4b72ff6a800f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5d8df4452e</guid>
            <dc:creator><![CDATA[J. Renée Beach]]></dc:creator>
            <pubDate>Sun, 02 Mar 2014 22:56:47 GMT</pubDate>
            <atom:updated>2014-03-02T22:56:47.503Z</atom:updated>
            <content:encoded><![CDATA[<h4>What we undertook, completed, learned and missed in our project’s first and second milestones.</h4><p>In my introductory post about the Quail project (<a href="https://medium.com/web-accessibility/c1a3a275fe1a">Open-source accessibility for the modern web</a>), I laid out our milestones and goals. We have reached the end of the <a href="https://github.com/kevee/quail/issues?milestone=2&amp;page=1&amp;state=open">second milestone</a>. The first milestone was short and concerned setup of the project. Of the 35 issues in the second milestone, we completed 28 (80%). The remaining 7 issues include 5 new tests and 2 framework improvements. The remaining work will be rolled into the next (third) milestone. We will get better at scoping work as we continue to get a better understanding of our group’s development velocity.</p><p>In addition to the issues, the project itself has matured. We will soon be moving development from Kevin Miller’s repository to repositories in a <a href="https://github.com/quailjs">dedicated organization (quailjs)</a> on Github. Kevin also arranged and hosted our first sprint on the tail-end of JSConf in San Diego in February.</p><p>Personally, I feel the work we are doing is on track for completion by mid-summer of 2014. Quail is fast becoming a powerful and flexible tool that developers can incorporate into their projects. And to encourage this, we have made Quail available through Node Packaged Module (NPM): <a href="https://www.npmjs.org/package/quail">https://www.npmjs.org/package/quail</a>.</p><p>I have enjoyed immensely working on this code. Often the bulk of my Sunday is spent refactoring and introducing new features to the codebase. The team we have assembled meshes very well and everyone is dedicated to building a solid and useful framework. I hope that more individuals will join us in our work and accelerate the pace of development.</p><p>If you have an interest in aiding this project, either as a developer or as an accessibility specialist (or both!), please use the <a href="https://github.com/kevee/quail/issues?milestone=3&amp;state=open">third milestone issue queue</a> to join us and engage. We especially need participation with writing new tests to expand our coverage of accessibility specifications. The <a href="https://github.com/kevee/quail/wiki/Writing-unit-tests-and-testing-accessibility-tests">how-to guide for creating an accessibility test in Quail</a> will get you started. Have a look through <a href="http://quailjs.org/#/accessibility-tests">the existing tests</a> to understand what has already been built.</p><p>With better and open tools, we can ensure that our web projects will be accessible to everyone.</p><p><strong>Hero image credit</strong></p><p>Author: Peter Paul Rubens (1577–1640)<br>Description : Polski: Chłopi zmierzający na targ. Summer, Royal Collection<br>Source/Photographer: Own work, PawełS</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5d8df4452e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open-source accessibility testing for the modern web]]></title>
            <link>https://medium.com/@jessebeach/open-source-accessibility-testing-for-the-modern-web-c1a3a275fe1a?source=rss-4b72ff6a800f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1a3a275fe1a</guid>
            <dc:creator><![CDATA[J. Renée Beach]]></dc:creator>
            <pubDate>Thu, 09 Jan 2014 18:50:14 GMT</pubDate>
            <atom:updated>2014-01-09T19:05:57.959Z</atom:updated>
            <content:encoded><![CDATA[<h4>Collaborating to improve Quail, an open-source web accessibility testing tool that will integrate with existing continuous integration processes and developer toolchains.</h4><h3><strong>Project description</strong></h3><p>As web development and content professionals, we all strive to build systems that are accessible to as many people as possible regardless of their ability. Developers employ numerous tools to ensure code quality in the life-cycle of a project — unit tests, feature tests, performance tests and code linters to name a few. For accessibility, there exists no open-source testing framework that integrates with modern development toolchains that allow for continuous integration.</p><p>The <a href="https://github.com/kevee/quail/">Quail Accessibility Information Library</a> is an open-source, MIT-licensed suite of tests that assess web page structure and content. The library is currently developed against WCAG and 508, but additional guidelines may be mapped to tests using a tagging system.</p><p>Starting in 2014, the <a href="https://github.com/kevee/quail/">Quail</a> development team, the <a href="http://www.kinggemeenten.nl/">Quality Institute Dutch Municipalities </a>(KING), <a href="https://acquia.com/">Acquia</a> and members of the <a href="https://drupal.org/">Drupal</a> and <a href="http://ckeditor.com/">CKEditor</a> communities will launch an effort to develop additional tests for better coverage against the WCAG guideline.</p><p>This collaboration will continue through the first half of 2014 as the Dutch team targets the launch of a government-wide testing platform for their web pages and content.</p><h3><strong>Participants</strong></h3><p>Several groups and individuals will participate in this effort at varying levels of involvement.</p><h4>Quail: Accessibility Information Library</h4><p><a href="https://github.com/kevee/quail/">Quail</a> was started by <a href="https://github.com/kevee">Kevin Miller</a> in 2009 as a PHP library specifically targeted at checking content accessibility within a CMS. Shortly after announcing Quail, he also developed the <a href="https://drupal.org/project/accessible_content">Accessible Content module</a> for Drupal, which has been used in several government and higher education websites to give content authors feedback. On the train from <a href="http://denver2012.drupal.org/">Drupalcon Denver</a> in March of 2012, Kevin re-wrote Quail as a jQuery plugin to help expand possible integrations to more projects. Quail continues to evolve through <a href="https://github.com/kevee/quail/graphs/contributors">volunteer contribution</a> and the leadership of Kevin.</p><h4>Quality Institute Dutch Municipalities (KING)</h4><p>The <a href="http://www.kinggemeenten.nl/">Quality Institute Dutch Municipalities</a> is committed to building accessible self-service tools and information for its citizens. It has elected to incorporate Quail into the development of a larger quality assurance platform for its web properties. The project team will provide architectural and development resources to Quail in order to increase test coverage as well as improve the instrumentation of the Quail project. It is through their generous support that we can accelerate the project’s development.</p><h4>Drupal and Acquia</h4><p>The <a href="https://drupal.org/">Drupal</a> project is <a href="https://drupal.org/about/accessibility">committed</a> to building accessible tools and formatting accessible content. The <a href="https://drupal.org/project/accessibility">Accessibility module</a> is a benchmark implementation of the Quail testing library. Drupal project leaders endorse the development of automated testing tools that improve the project’s user experience for everyone. We anticipate that many volunteer develops will contribute some time to this project.</p><p><a href="https://acquia.com/">Acquia</a> is a for-profit company with a commitment to fostering the Drupal project. The <a href="https://www.acquia.com/blog/announcing-office-cto-acquia">Office of the CTO</a> will provide strategy and consulting resources to participants of this project on an as-needed basis.</p><h4>CKEditor</h4><p>The <a href="http://ckeditor.com/">CKEditor</a> <a href="http://ckeditor.com/get-involved/our-team">development team</a> have a <a href="http://ckeditor.com/blog/CKEditor-WAI-ARIA-Usable-Accessibility">strong, committed history to accessibility</a>. They will provide architectural feedback to ensure that Quail tests can be employed to assess content accessibility within the CKEditor application.</p><h4>YOU</h4><p>Yes! You! If you are reading the announcement, you probably have an interest in improving accessibility on the web. And we all know that assessing conformance to accessibility standards is not simple. The guidelines are comprehensive and dense with information. So help us automate them into tools that you can use in your web project!</p><h3><strong>Roadmap</strong></h3><p>The full roadmap is outlined here: <a href="https://github.com/kevee/quail/issues/milestones">https://github.com/kevee/quail/issues/milestones</a></p><h4><strong>Milestone 1 — Establish this project</strong></h4><p>Due on January 10th, 2014</p><p>The first milestone concerns launching this project. Participant responsibilities will be established. Our project management tools will also be chosen and set up during this time.</p><p><a href="https://github.com/kevee/quail/issues?milestone=1&amp;state=open">List of issues for Milestone 1</a></p><h4><strong>Milestone 2 — Test development</strong></h4><p>Due on February 28th, 2014</p><p>The second milestone concerns the development of new tests targeted to the <a href="http://www.w3.org/TR/WCAG20/">WCAG specification</a>, specifically the <a href="http://www.w3.org/TR/WCAG20-TECHS/">Techniques</a>. The tests will cluster around assessment of individual page elements, testable with the current Quail framework.</p><p><a href="https://github.com/kevee/quail/issues?milestone=2&amp;state=open">List of issues for Milestone 2</a></p><h4><strong>Milestone 3 — Additional tests</strong></h4><p>Due on April 30th, 2014</p><p>The tests slated for third milestone concern the overall structure of a page in terms HTML specification. We will also address frames.</p><p><a href="https://github.com/kevee/quail/issues?milestone=3&amp;state=open">List of issues for Milestone 3</a></p><h4><strong>Further milestones</strong></h4><p>We will establish additional milestones and attribute issues to these efforts in order to structure the continued development of the Quail accessibility testing framework.</p><h3><strong>How to participate</strong></h3><p>Quail is an open-source suite of tests <a href="https://github.com/kevee/quail">hosted on Github</a>. We follow the standard <a href="https://help.github.com/articles/using-pull-requests">Pull Request model</a> against the <a href="https://github.com/kevee/quail/tree/dev/">dev branch</a>.</p><p>The first and major category of work for Quail involves the <strong>creation and refinement of tests</strong> that exercise conformance criteria of accessibility guidelines. For example, we need a test for <a href="http://www.w3.org/TR/WCAG20-TECHS/H56.html">WCAG Technique H56: dir attribute on an inline element</a>. Work is already underway <a href="https://github.com/kevee/quail/issues/72">discussing a solution</a>.</p><p>The second category of development work involves <strong>instrumentation</strong>. We could use guidance and code input from individuals who have experience structuring modules for inclusion in larger projects using tools such as <a href="https://npmjs.org/">NPM</a> and <a href="http://bower.io/">Bower</a>. We are already discussing <a href="https://github.com/kevee/quail/issues/94">publishing Quail as a Node module</a>.</p><p>If you have questions about participation, you may contact <a href="https://github.com/jessebeach">Jesse Beach</a> at jesse.beach (at) acquia (dot) com.</p><p><strong>Hero image credit</strong></p><p>Philips Koninck (Dutch, 1619 — 1688)<br><em>River Landscape</em>, about 1675, Watercolor and gouache<br>13.5 x 20 cm (5 5/16 x 7 7/8 in.)<br>The J. Paul Getty Museum, Los Angeles</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1a3a275fe1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>