<?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</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>&lt;div id=&#34;accessibility&#34; class=&#34;section level2&#34;&gt;&#xA;&lt;h2&gt;Accessibility&lt;/h2&gt;&#xA;&lt;p&gt;Over the years, I faced situations where I needed to make content&#xA;(lecture notes, manuscripts, consultancy reports, etc.) as accessible&#xA;as possible to effectively communicate with colleagues, clients, and&#xA;students with particular accessibility requirements.&lt;/p&gt;&#xA;&lt;p&gt;All those “accessibility encounters” of mine left me with a pile of&#xA;unstructured notes and advice to my self to which I often refer. Well,&#xA;I decided to blog about parts of it in case anyone else finds it&#xA;useful.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
