<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Allon Dery</title>
    <description>The latest articles on Forem by Allon Dery (@allon_a11y).</description>
    <link>https://forem.com/allon_a11y</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3501540%2Fb19c022b-6ab9-4993-9d22-d04946313d3b.jpg</url>
      <title>Forem: Allon Dery</title>
      <link>https://forem.com/allon_a11y</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/allon_a11y"/>
    <language>en</language>
    <item>
      <title>Accessibility: Looking for Honest Feedback</title>
      <dc:creator>Allon Dery</dc:creator>
      <pubDate>Sun, 14 Sep 2025 14:23:30 +0000</pubDate>
      <link>https://forem.com/allon_a11y/accessibility-looking-for-honest-feedback-3mm0</link>
      <guid>https://forem.com/allon_a11y/accessibility-looking-for-honest-feedback-3mm0</guid>
      <description>&lt;p&gt;Hi everyone,&lt;/p&gt;

&lt;p&gt;Over the past weeks I’ve been auditing and fixing accessibility issues on my own website. I’d estimate that I’ve resolved around 90% of the issues I initially identified, but of course, testing your own site always comes with a blind spot. That’s why I’d love to hear from this community.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What I’ve done so far:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Fixed color contrast issues based on WCAG 2.2 guidelines&lt;/li&gt;
&lt;li&gt;Improved keyboard navigation and focus states&lt;/li&gt;
&lt;li&gt;Adjusted heading structure for clearer hierarchy&lt;/li&gt;
&lt;li&gt;Ensured reflow and zoom work properly on small screens&lt;/li&gt;
&lt;li&gt;Tested with VoiceOver for basic screen reader compatibility&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I know many of you have sharp eyes for accessibility details that can be easy to miss. I’d really value your feedback:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Do you notice any barriers still present?&lt;/li&gt;
&lt;li&gt;Are there areas where the user experience could be further improved for assistive technology users?&lt;/li&gt;
&lt;li&gt;Anything I might have overlooked entirely?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you’re open to taking a look, I’d greatly appreciate any feedback on &lt;a href="https://www.bureautoegankelijkheid.nl/" rel="noopener noreferrer"&gt;my accessibility audit process&lt;/a&gt;. All criticism is welcome, the more critical and detailed, the better. I see this as a chance to learn and to keep raising the standard of accessibility in practice.&lt;/p&gt;

&lt;p&gt;Thanks in advance for your time.&lt;/p&gt;

</description>
      <category>help</category>
      <category>a11y</category>
      <category>discuss</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
