<?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: itsvicki</title>
    <description>The latest articles on DEV Community by itsvicki (@itsvicki).</description>
    <link>https://dev.to/itsvicki</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%2F275013%2F08468747-6392-4512-8086-fd0d661f247b.JPG</url>
      <title>DEV Community: itsvicki</title>
      <link>https://dev.to/itsvicki</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/itsvicki"/>
    <language>en</language>
    <item>
      <title>Accessibility tools I wish I knew about sooner</title>
      <dc:creator>itsvicki</dc:creator>
      <pubDate>Fri, 21 Aug 2020 19:01:37 +0000</pubDate>
      <link>https://dev.to/itsvicki/accessibility-tools-i-wish-i-knew-about-sooner-7b3</link>
      <guid>https://dev.to/itsvicki/accessibility-tools-i-wish-i-knew-about-sooner-7b3</guid>
      <description>&lt;p&gt;World Wide Web Consortium (W3C) do a great job of not only tirelessly researching ways of making the web better, but also go to great lengths to explain advice in the form of Web Content Accessibility Guidelines (WCAG). &lt;/p&gt;

&lt;p&gt;As good as these guidelines are, including their &lt;a href="https://www.w3.org/WAI/WCAG21/quickref/?currentsidebar=%23col_customize"&gt;how to Meet WCAG (quick reference)&lt;/a&gt;, here are some tools which I've found great to break these guidelines down. &lt;br&gt;
&lt;em&gt;Do note that automated tools can only go so far and not a replacement for understand the guidelines.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Browser plugins
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;To quote &lt;a href="https://chrome.google.com/webstore/detail/nocoffee/jjeeggmbnhckmgdhmgdckeigabjfbddl"&gt;NoCoffee&lt;/a&gt;, "vision problems are more pervasive than most of us realise. Upwards of 285 million people worldwide are visually impaired. Many more have low or moderate visual difficulties". NoCoffee can help understand problems such as: Low Acuity, Low Contrast Sensitivity, Colour-blindness, visual snow, glare ghosting and cataracts, Nystagmus or Obscructed visual field&lt;/li&gt;
&lt;li&gt;As engineers it's sometimes preferable to develop in Chrome. However in the case of Mac; VoiceOver works best with Safari and not so great with Chrome. For those times when you want to quickly check how a screen reader would perceive something &lt;a href="https://chrome.google.com/webstore/detail/chromevox-classic-extensi/kgejglhpjiefppelpmljglcjbhoiplfn?hl=en"&gt;ChromeVox&lt;/a&gt; is an option. &lt;em&gt;Although I would always recommend re-checking with a recommended browser + screen reader at the end&lt;/em&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://www.deque.com/axe/devtools/"&gt;AXE do a range of great tools&lt;/a&gt; to verify accessibility, including &lt;a href="https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/"&gt;axe for Firefox&lt;/a&gt; or &lt;a href="https://chrome.google.com/webstore/detail/axe/lhdoppojpmngadmnindnejefpokejbdd"&gt;axe for Chrome&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://khan.github.io/tota11y/"&gt;tota11y&lt;/a&gt; "helps visualise how your site performs with assistive technologies... In many cases, developers must have some prior accessibility knowledge in order to make sense of the results. Instead, tota11y aims to reduce this barrier of entry by helping visualize accessibility violations (and successes), while educating on best practices." &lt;/li&gt;
&lt;li&gt;Within &lt;a href="https://developers.google.com/web/tools/chrome-devtools/accessibility/reference#audits"&gt;Chrome DevTools&lt;/a&gt; there is the ability to audit a page's accessibility. Chrome states that it helps to determine if: "a page is properly marked up for screen readers. The text elements on a page have sufficient contrast ratios."&lt;/li&gt;
&lt;li&gt;Probably one people are more familiar with, &lt;a href="https://chrome.google.com/webstore/detail/wave-evaluation-tool/jbbplnpkjmmeebjpijfedlgcdilocofh"&gt;WAVE Evaluation Tool&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  HTML validators
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="http://squizlabs.github.io/HTML_CodeSniffer/"&gt;HTML_CodeSniffer&lt;/a&gt; "is a client-side script that checks HTML source code and detects violations of a defined coding standard. HTML_CodeSniffer is written entirely in JavaScript, does not require any server-side processing and can be extended by developers to enforce custom coding standards by creating your own 'sniffs'."&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Colour
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://www.paciellogroup.com/resources/contrastanalyser/"&gt;Colour Contrast Analyser&lt;/a&gt; is a great accessibility tool for when you need to do pixel picking to test colour contrast ratios. It also simulates certain visual impairments, including colourblindness&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://contrast-triangle.com"&gt;The Contrast Triangle&lt;/a&gt; which helps breakdown link contrast guidelines&lt;/li&gt;
&lt;li&gt;People who have colorblindness are sensitive to certain colors such as reds and greens. &lt;a href="http://www.colororacle.org/"&gt;Color Oracle&lt;/a&gt; is one tool that can be used to test web page designs for effective color usage. Color Oracle is a free colorblindness simulator that can be used for Windows, Mac, or Linux. It applies a color filter on the web page that simulates how a person with colorblindness may see a design. Testers and designers can use the tool to determine whether colors used in the design may cause issues for people who have colorblindness&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Keyboard accessibility
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A &lt;a href="https://webaim.org/techniques/keyboard/#testing"&gt;guide&lt;/a&gt; to most of the common online interactions, the standard keystrokes for the interaction, and additional information on things to consider during testing&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Code snippets
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Deque University have a growing &lt;a href="https://dequeuniversity.com/library/"&gt;code library&lt;/a&gt; where you can find complete code snippets for common snippets&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Hope that helps!&lt;/p&gt;

</description>
      <category>a11y</category>
      <category>html</category>
      <category>css</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Tools to succeed</title>
      <dc:creator>itsvicki</dc:creator>
      <pubDate>Thu, 30 Jul 2020 20:02:02 +0000</pubDate>
      <link>https://dev.to/itsvicki/tools-to-succeed-2f1m</link>
      <guid>https://dev.to/itsvicki/tools-to-succeed-2f1m</guid>
      <description>&lt;p&gt;The web has never been as capable as it is today and will be tomorrow. &lt;br&gt;
As software engineers we have so many options, almost too many, and it can be daunting. This post is just to share some of the tools I've found great at managing to remember the basics but keep with the current.&lt;/p&gt;

&lt;h2&gt;
  
  
  Our good old friend, data structure &amp;amp; algorithms
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;"This is the coding implementations of the &lt;a href="https://books.adrianmejia.com/dsajs-data-structures-algorithms-javascript/"&gt;DSA.js&lt;/a&gt; book and the repo for the NPM package.&lt;br&gt;
In this repository, you can find the implementation of algorithms and data structures in JavaScript. This material can be used as a reference manual for developers, or you can refresh specific topics before an interview. Also, you can find ideas to solve problems more efficiently."&lt;br&gt;
&lt;a href="https://github.com/amejiarosario/dsa.js"&gt;https://github.com/amejiarosario/dsa.js&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  AlgoExpert
&lt;/h2&gt;

&lt;p&gt;There are many of these types of sites around, and for some, they would rather not pay for it so do do some research of which would suit you best. &lt;br&gt;
But for me, the user interface is what really worked. It's clear to see what topics there is to cover, how far through and easy to work on coding questions.&lt;br&gt;
&lt;a href="https://www.algoexpert.io"&gt;algoexpert.io&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep up to date with podcasts
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.bemyeyes.com/podcasts/introducing-13-letters-the-accessibility-podcast"&gt;13 letters - an accessibility podcast&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://frontendhappyhour.com"&gt;Front End Happy Hour&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://blog.codepen.io/radio/"&gt;CodePen Radio&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://changelog.com/jsparty"&gt;JS party&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Keep up to date with email
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://javascriptweekly.com"&gt;JavaScript weekly&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://react.statuscode.com"&gt;React status&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Node.js was an absolute turning point in development, there is no denying that. But &lt;a href="https://github.com/denoland/deno"&gt;Deno&lt;/a&gt; is the one to watch now, as explained by the creator, Ryan Dahl in &lt;a href="https://www.youtube.com/watch?v=M3BM9TB-8yA"&gt;10 Things I Regret About Node.js&lt;/a&gt;. &lt;a href="https://denoweekly.com"&gt;Deno weekly&lt;/a&gt; is another great one.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Keep up to date with twitter
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://twitter.com/sxywu"&gt;sxywu&lt;/a&gt; who does some inspiring work with &lt;a href="https://sxywu.com"&gt;"data-driven art and visualizations"&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href="https://twitter.com/addyosmani"&gt;Addy Osmani&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://twitter.com/ryanflorence"&gt;Ryan Florence&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://twitter.com/kentcdodds"&gt;Kent C. Dodds&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://twitter.com/codepo8"&gt;Chris Heilmann&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://twitter.com/mpjme"&gt;mpj&lt;/a&gt; creator of &lt;a href="https://www.youtube.com/channel/UCO1cgjhGzsSYb1rsB4bFe4Q"&gt;FunFunFunction&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href="https://twitter.com/JavaScriptDaily"&gt;JavaScript Daily&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;br&gt;&lt;br&gt;
Thanks for reading! 🙌&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>webdev</category>
    </item>
    <item>
      <title>A different kind of introduction to Accessibility</title>
      <dc:creator>itsvicki</dc:creator>
      <pubDate>Mon, 02 Dec 2019 21:42:27 +0000</pubDate>
      <link>https://dev.to/itsvicki/introduction-to-accessibility-2l73</link>
      <guid>https://dev.to/itsvicki/introduction-to-accessibility-2l73</guid>
      <description>&lt;p&gt;For those of us who are more visual learners - a quick introduction to Accessibility. &lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2F5la2mpr6xkuudczdde8j.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2F5la2mpr6xkuudczdde8j.jpg" alt="Introduction to Accessibility - what is it - transcript at bottom of page"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2Fcg9w7cb680u9agogywdh.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2Fcg9w7cb680u9agogywdh.jpg" alt="The ability spectrum - we all benefit - transcript at bottom of page"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2Fq4djggmtku2epj5jnmzy.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2Fq4djggmtku2epj5jnmzy.jpg" alt="Types of disabilities - transcript at bottom of page"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2Fu1j83ua2ur2em1vesbq0.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2Fu1j83ua2ur2em1vesbq0.jpg" alt="How software creates equal opportunities - transcript at bottom of page"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;--&lt;/p&gt;

&lt;p&gt;Transcript&lt;/p&gt;

&lt;h1&gt;
  
  
  Introducing Accessibility - Ally
&lt;/h1&gt;

&lt;h2&gt;
  
  
  What is it?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;It comes in all shapes &amp;amp; sizes&lt;/li&gt;
&lt;li&gt;It's necessary &amp;amp; non-negotiable&lt;/li&gt;
&lt;li&gt;It's an ongoing design requirement&lt;/li&gt;
&lt;li&gt;It's not limited to physical disabilities&lt;/li&gt;
&lt;li&gt;It's made up of objective &amp;amp; subjective guidelines&lt;/li&gt;
&lt;li&gt;It's the right &amp;amp; ability to access the same information&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The ability spectrum
&lt;/h2&gt;

&lt;p&gt;&lt;em&gt;From permanent - situation&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Permanent - such as legally blind, deaf or physically disabled&lt;br&gt;
 -&amp;gt; temporary - such as having an ear infection, broken arm or eye infection&lt;br&gt;
  -&amp;gt; -&amp;gt; situational - such as a new parent, at a concert or library&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;a.k.a we all benefit from accessibility&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;You can thank accessibility for..&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;...those handy next stop reminders on the bus &amp;amp; train&lt;/li&gt;
&lt;li&gt;...those captions so you can still watch the news in a noisy bar&lt;/li&gt;
&lt;li&gt;...those extra page hits because search engines discovered your transcripts&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Types of disabilities
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Colour-blind / blind / low vision&lt;/li&gt;
&lt;li&gt;Deafblind / deaf&lt;/li&gt;
&lt;li&gt;Cognitive / speech / reading / seizures&lt;/li&gt;
&lt;li&gt;Motor / multiple disabilities&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Software + assistive technology
&lt;/h2&gt;

&lt;p&gt;We all live in a pretty &lt;strong&gt;incredible&lt;/strong&gt; time where software creates equal opportunities when creators simply follow standards&lt;/p&gt;

&lt;p&gt;Application [in/output]&lt;br&gt;
 [in/output] transformed into an accessibility tree [in/output]&lt;br&gt;
 [in/output] assistive technology [in/output]&lt;br&gt;
 [in/output] user [in/output]&lt;/p&gt;

&lt;p&gt;&lt;em&gt;screen readers&lt;/em&gt; are the most commonly discussed assistive technology&lt;br&gt;
...but there is also technology to translate into/from &lt;strong&gt;braille display&lt;/strong&gt;&lt;br&gt;
...&lt;em&gt;magnify text&lt;/em&gt;&lt;br&gt;
...&lt;em&gt;head wands&lt;/em&gt;, &lt;em&gt;mouth sticks&lt;/em&gt; &amp;amp; &lt;em&gt;oversized trackball mouse&lt;/em&gt;&lt;br&gt;
...&lt;em&gt;single switch&lt;/em&gt; &amp;amp; &lt;em&gt;sip-and-puff&lt;/em&gt; switch&lt;br&gt;
...&lt;em&gt;adaptive keyboard&lt;/em&gt;&lt;br&gt;
...&lt;em&gt;eye-tracking&lt;/em&gt; &amp;amp; &lt;em&gt;voice recognition&lt;/em&gt; technology&lt;/p&gt;

&lt;h2&gt;
  
  
  Cognitive disabilities
&lt;/h2&gt;

&lt;p&gt;always keep in mind...&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;"don't beat around the bush"&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Be direct, help avoid mistakes &amp;amp; be clear on how to fix them&lt;/li&gt;
&lt;li&gt;Don't expect users to understand implied meaning&lt;/li&gt;
&lt;li&gt;Give adequate time for everyone&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;still be creative!&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Balance use of text alternatives like video &amp;amp; illustrations&lt;/li&gt;
&lt;li&gt;...or use bright colours to keep attention &amp;amp; interest&lt;/li&gt;
&lt;li&gt;Keep text &amp;amp; layout simple - white space is your friend&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>a11y</category>
      <category>technology</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
