<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Accessibility on rostrum.blog</title>
    <link>https://www.rostrum.blog/tags/accessibility/</link>
    <description>Recent content in Accessibility on rostrum.blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 30 Dec 2020 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.rostrum.blog/tags/accessibility/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Accessible colour contrasts with {coloratio}</title>
      <link>https://www.rostrum.blog/2020/12/30/coloratio/</link>
      <pubDate>Wed, 30 Dec 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2020/12/30/coloratio/</guid>
      <description>This blog’s theme: insufficient contrast!  tl;dr I made a small R package called {coloratio} to evaluate colour-contrast ratios for accessibility. Then I found out that {savonliquide} already exists to do this.
 Accessible charts The UK government’s website, GOV.UK, was developed with user needs and accessibility in mind. I’ve been using {ggplot2} to recreate the simple, accessible chart styles suggested for use on GOV.UK by the Government Statistical Service.</description>
    </item>
    
    <item>
      <title>Translate R to English with {r2eng}</title>
      <link>https://www.rostrum.blog/2020/11/14/hello-r2eng/</link>
      <pubDate>Sat, 14 Nov 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2020/11/14/hello-r2eng/</guid>
      <description>tl;dr I created the work-in-progress {r2eng} package (source, site) to help translate R expressions to speakable English. Inspired by Amelia McNamara and with a huge amount of help from Chung-hong Chan.
 Communication is hard Amelia McNamara (site, Twitter) gave a talk at the useR! 2020 conference called ‘Speaking R’. Watch the video on YouTube, or take a look at the slides.
To summarise greatly: R code should be speakable so that we can teach, learn and communicate with minimal friction.</description>
    </item>
    
    <item>
      <title>{altcheckr}: check image alt text from R</title>
      <link>https://www.rostrum.blog/2019/12/08/altcheckr/</link>
      <pubDate>Sun, 08 Dec 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2019/12/08/altcheckr/</guid>
      <description>tl;dr I’ve made a small R package called {altcheckr} that checks the accessibility of images on web pages. It has functions that (1) scrape attributes from HTML  elements on a web page and (2) apply simple rules to indicate the suitability of the alt text provided. To use:
remotes::install_github(&amp;quot;matt-dray/altcheckr&amp;quot;) images &amp;lt;- alt_get(&amp;quot;https://www.bbc.co.uk/news&amp;quot;) alt_check(images) I’m not an expert and the package has not been user tested.
 Accessibility A web site is accessible if everyone can engage with its content.</description>
    </item>
    
    <item>
      <title>How do you pronounce {dplyr}?</title>
      <link>https://www.rostrum.blog/2019/09/20/say-package/</link>
      <pubDate>Fri, 20 Sep 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2019/09/20/say-package/</guid>
      <description>Get that oesophagus involved, why not? (Public Domain)  tl;dr It’s ‘d-ply-r’ according to Hadley himself… maybe.
What does it sound like when your computer tries to pronounce R package names? Is this an accessibility issue?
 Deep liar Sometimes I hear a word being spoken and think ‘oh wait, is that how it’s actually pronounced?’
I know people struggle with pronouncing R package names. They’re often hard to parse.</description>
    </item>
    
    <item>
      <title>How accessible is my post about accessibility?</title>
      <link>https://www.rostrum.blog/2018/07/12/accessible-accessibility/</link>
      <pubDate>Thu, 12 Jul 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2018/07/12/accessible-accessibility/</guid>
      <description>The accessibility empathy lab at the Government Digital Services building  Digital accessibility I wrote about an accessibility workshop at the recent Sprint 18 conference.
I’ve since been to a more in-depth workshop with Government Digital Service (GDS), who have just launched the latest version of their ‘testing for accessibility’ guidance in the Service Manual and also the GOV.UK Design System, which contains reusable GOV.UK styles, patterns and components with accessibility in mind.</description>
    </item>
    
    <item>
      <title>Accessibility workshop at #Sprint18</title>
      <link>https://www.rostrum.blog/2018/05/12/accessibility-workshop-at-sprint18/</link>
      <pubDate>Sat, 12 May 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2018/05/12/accessibility-workshop-at-sprint18/</guid>
      <description>Sprinting Sprint events are a chance for the government digital, data, design and technology community to:
 look back on the work we’ve been doing to transform government and to look forward at what we need to do
 Kevin Cunnington (@kevincunnington), Director General of the Government Digital Service (GDS), outlined this in a recent blog post.
This year’s major themes were transformation, innovation and collaboration. The event was held at the Southbank Centre and Royal Festival Hall in London, with 40 speakers, 19 workshops and over 700 delegates representing 40 departments and agencies.</description>
    </item>
    
  </channel>
</rss>