<?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>DEV Community: Samuel Enyi</title>
    <description>The latest articles on DEV Community by Samuel Enyi (@samuel_enyi_0f46ef94a1918).</description>
    <link>https://dev.to/samuel_enyi_0f46ef94a1918</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%2F1615896%2Fc6310aff-b6f3-4b36-8687-e484f3f76a7b.jpg</url>
      <title>DEV Community: Samuel Enyi</title>
      <link>https://dev.to/samuel_enyi_0f46ef94a1918</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/samuel_enyi_0f46ef94a1918"/>
    <language>en</language>
    <item>
      <title>Building Accessible Data Tables: Best Practices</title>
      <dc:creator>Samuel Enyi</dc:creator>
      <pubDate>Sat, 15 Jun 2024 09:18:06 +0000</pubDate>
      <link>https://dev.to/samuel_enyi_0f46ef94a1918/building-accessible-data-tables-best-practices-4bgc</link>
      <guid>https://dev.to/samuel_enyi_0f46ef94a1918/building-accessible-data-tables-best-practices-4bgc</guid>
      <description>&lt;p&gt;E-commerce: Accessible Data Tables.&lt;br&gt;
We evaluated several e-commerce sites and found that most of them feature data tables. This is likely because data tables effectively organize and present large amounts of information clearly. Notably, over 80% of these data tables were not properly implemented using accessible coding best practices. Learn more about accessible data tables […]&lt;/p&gt;

&lt;p&gt;The post &lt;a href="https://accessmeter.com/articles/building-accessible-data-tables/"&gt;Building Accessible Data Tables: Best Practices&lt;/a&gt; appeared first on &lt;a href="https://accessmeter.com"&gt;Accessmeter LLC&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Tables with Both Column &amp;amp; Row headers&lt;br&gt;
Failing Example:&lt;br&gt;
Code:&lt;br&gt;
The following code snippet shows a data table with both row and column headers:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
  Quarterly Sales Data
  &lt;thead&gt;
    &lt;tr&gt;
      &lt;th&gt;&lt;/th&gt;
      &lt;th&gt;Week 1&lt;/th&gt;
      &lt;th&gt;Week 2&lt;/th&gt;
      &lt;th&gt;Week 3&lt;/th&gt;
      &lt;th&gt;Week 4&lt;/th&gt;
      &lt;th&gt;Week 5&lt;/th&gt;
    &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
    &lt;tr&gt;
      &lt;td&gt;1st Quarter&lt;/td&gt;
      &lt;td&gt;100&lt;/td&gt;
      &lt;td&gt;150&lt;/td&gt;
      &lt;td&gt;80&lt;/td&gt;
      &lt;td&gt;200&lt;/td&gt;
      &lt;td&gt;530&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;2nd Quarter&lt;/td&gt;
      &lt;td&gt;120&lt;/td&gt;
      &lt;td&gt;130&lt;/td&gt;
      &lt;td&gt;100&lt;/td&gt;
      &lt;td&gt;180&lt;/td&gt;
      &lt;td&gt;530&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;3rd Quarter&lt;/td&gt;
      &lt;td&gt;80&lt;/td&gt;
      &lt;td&gt;95&lt;/td&gt;
      &lt;td&gt;70&lt;/td&gt;
      &lt;td&gt;150&lt;/td&gt;
      &lt;td&gt;395&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;4th Quarter&lt;/td&gt;
      &lt;td&gt;90&lt;/td&gt;
      &lt;td&gt;110&lt;/td&gt;
      &lt;td&gt;85&lt;/td&gt;
      &lt;td&gt;160&lt;/td&gt;
      &lt;td&gt;445&lt;/td&gt;
    &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Result:&lt;br&gt;
Quarterly Sales Data&lt;br&gt;
Week 1  Week 2  Week 3  Week 4  Week 5&lt;br&gt;
1st Quarter 100 150 80  200 530&lt;br&gt;
2nd Quarter 120 130 100 180 530&lt;br&gt;
3rd Quarter 80  95  70  150 395&lt;br&gt;
4th Quarter 90  110 85  160 445&lt;br&gt;
This table is a failing example because it lacks &lt;/p&gt;
&lt;th&gt; elements to define the row headers. While screen readers will correctly associate each data cell with its column headers, they will not properly associate the data cells with their corresponding row headers.

&lt;p&gt;Passing Example&lt;br&gt;
Code:&lt;br&gt;
The following code snippet shows a data table with both row and column headers:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
  Quarterly Sales Data
  &lt;thead&gt;
    &lt;tr&gt;
      &lt;th&gt;&lt;/th&gt;
      &lt;th&gt;Week 1&lt;/th&gt;
      &lt;th&gt;Week 2&lt;/th&gt;
      &lt;th&gt;Week 3&lt;/th&gt;
      &lt;th&gt;Week 4&lt;/th&gt;
      &lt;th&gt;Week 5&lt;/th&gt;
    &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
    &lt;tr&gt;
      &lt;th&gt;1st Quarter&lt;/th&gt;
      &lt;td&gt;100&lt;/td&gt;
      &lt;td&gt;150&lt;/td&gt;
      &lt;td&gt;80&lt;/td&gt;
      &lt;td&gt;200&lt;/td&gt;
      &lt;td&gt;530&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;th&gt;2nd Quarter&lt;/th&gt;
      &lt;td&gt;120&lt;/td&gt;
      &lt;td&gt;130&lt;/td&gt;
      &lt;td&gt;100&lt;/td&gt;
      &lt;td&gt;180&lt;/td&gt;
      &lt;td&gt;530&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;th&gt;3rd Quarter&lt;/th&gt;
      &lt;td&gt;80&lt;/td&gt;
      &lt;td&gt;95&lt;/td&gt;
      &lt;td&gt;70&lt;/td&gt;
      &lt;td&gt;150&lt;/td&gt;
      &lt;td&gt;395&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;th&gt;4th Quarter&lt;/th&gt;
      &lt;td&gt;90&lt;/td&gt;
      &lt;td&gt;110&lt;/td&gt;
      &lt;td&gt;85&lt;/td&gt;
      &lt;td&gt;160&lt;/td&gt;
      &lt;td&gt;445&lt;/td&gt;
    &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Result:&lt;/p&gt;

&lt;p&gt;Quarterly Sales Data&lt;br&gt;
Week 1  Week 2  Week 3  Week 4  Week 5&lt;br&gt;
1st Quarter 100 150 80  200 530&lt;br&gt;
2nd Quarter 120 130 100 180 530&lt;br&gt;
3rd Quarter 80  95  70  150 395&lt;br&gt;
4th Quarter 90  110 85  160 445&lt;br&gt;
This table is a passing example because there is a &lt;/p&gt;


&lt;/th&gt;
&lt;th&gt; element to define the row and column headers and a &lt;/th&gt;
&lt;tbody&gt; element to define the table body. Screen readers will properly associate each data cell with its appropriate row and column headers.

&lt;p&gt;Let’s Wrap It Up&lt;br&gt;
The most common errors we often find when testing websites featuring data tables are improper associations of each cell with their corresponding column and row headers. Users with disabilities may find these kinds of tables difficult to comprehend.&lt;/p&gt;

&lt;p&gt;Since most charts and graphs used to convey data on e-commerce sites can be made accessible by providing text alternatives in the form of data tables, it becomes very necessary to make these tables accessible.&lt;br&gt;
Leave Questions below, I will get to it in a moment.&lt;/p&gt;


&lt;/tbody&gt;

</description>
      <category>articles</category>
      <category>a11y</category>
      <category>webaccessibility</category>
    </item>
    <item>
      <title>Web: Your Accessibility FAQ Guide</title>
      <dc:creator>Samuel Enyi</dc:creator>
      <pubDate>Fri, 14 Jun 2024 16:44:06 +0000</pubDate>
      <link>https://dev.to/samuel_enyi_0f46ef94a1918/web-your-accessibility-faq-guide-2b71</link>
      <guid>https://dev.to/samuel_enyi_0f46ef94a1918/web-your-accessibility-faq-guide-2b71</guid>
      <description>&lt;p&gt;Ensuring that your website is accessible to all users, including those with disabilities, is not only a legal obligation but also a way to enhance user experience and expand your audience. This FAQ session aims to address some of the most common questions and provide practical advice on making your website more accessible. While the […]&lt;/p&gt;

&lt;p&gt;The post &lt;a href="https://accessmeter.com/faqs/web-accessibility-faq/"&gt;Web: Your Accessibility FAQ Guide&lt;/a&gt; appeared first on &lt;a href="https://accessmeter.com"&gt;Accessmeter LLC&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>faqs</category>
      <category>a11y</category>
      <category>webaccessibility</category>
    </item>
  </channel>
</rss>
