<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Salvatore La Spata · Blog</title>
    <link>https://salvatorelaspata.net/en/blog/</link>
    <atom:link href="https://salvatorelaspata.net/en/rss.xml" rel="self" type="application/rss+xml" />
    <description>Notes on SAP BTP, CAP, accessibility and whatever I build at the weekend. Sometimes in Italian too.</description>
    <language>en</language>
    <item>
      <title>An accessible portfolio: what I changed for WCAG 2.2</title>
      <link>https://salvatorelaspata.net/en/blog/accessible-portfolio</link>
      <guid isPermaLink="true">https://salvatorelaspata.net/en/blog/accessible-portfolio</guid>
      <description>Contrast computed for two themes, a focus ring that never hides, 44 px targets, filters that speak up and opt-out motion: my site, rebuilt for WCAG 2.2 AA.</description>
      <pubDate>Mon, 28 Sep 2026 00:00:00 GMT</pubDate>
      <category>Accessibility</category>
      <category>Frontend</category>
    </item>
    <item>
      <title>OData is not REST (and that's fine)</title>
      <link>https://salvatorelaspata.net/en/blog/odata-is-not-rest</link>
      <guid isPermaLink="true">https://salvatorelaspata.net/en/blog/odata-is-not-rest</guid>
      <description>$metadata, query options, $batch, ETags and deep insert: what changes for a REST team meeting OData in SAP, and when a plain endpoint is the better choice.</description>
      <pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate>
      <category>SAP BTP</category>
    </item>
    <item>
      <title>Accessible web applications for visually impaired and blind users</title>
      <link>https://salvatorelaspata.net/en/blog/web-accessibility-wcag</link>
      <guid isPermaLink="true">https://salvatorelaspata.net/en/blog/web-accessibility-wcag</guid>
      <description>How to apply WCAG, ARIA and best practices to make interfaces fully usable with screen readers and assistive technologies</description>
      <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
      <category>Accessibility</category>
      <category>Frontend</category>
    </item>
  </channel>
</rss>
