<?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 Ioannis Kosmidis</title>
    <link>http://www.ikosmidis.com/tags/accessibility/</link>
    <description>Recent content in accessibility on Ioannis Kosmidis</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 14 Oct 2020 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://www.ikosmidis.com/tags/accessibility/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Accessibility of HTML pages from R Markdown</title>
      <link>http://www.ikosmidis.com/post/blog-accessibility/</link>
      <pubDate>Wed, 14 Oct 2020 00:00:00 +0000</pubDate>
      <guid>http://www.ikosmidis.com/post/blog-accessibility/</guid>
      <description>Accessibility Over the years, I faced situations where I needed to make content (lecture notes, manuscripts, consultancy reports, etc.) as accessible as possible to effectively communicate with colleagues, clients, and students with particular accessibility requirements.&#xA;All those “accessibility encounters” of mine left me with a pile of unstructured notes and advice to my self to which I often refer. Well, I decided to blog about parts of it in case anyone else finds it useful.</description>
    </item>
  </channel>
</rss>
