Skip to content

Coding Practice

Locate an Element Using a CSS Selector in Google Chrome

When you work with Pa11y you may get errors as I described in an earlier blog post:

1
2
3
4
Error: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.13:1. Recommendation:  change background to #0a8927.
   ├── WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
   ├── html > body > div > div:nth-child(4) > div:nth-child(1) > div > div:nth-child(2) > a
   └── <a href="https://www.goodreads.com/user/show/26287713-johnny-graber" class="btn btn-success">More on Goodreads</a>

Improve the Accessibility of Your Web Application

Last month I attended the NDC Oslo 2020 online workshop Front End Web Fundamentals hosted by Amy Kapernick (@amys_kapers). In my first post on this workshop I wrote about the tools we used and resources that can help you to create better web applications.

Today I focus on accessibility. I am not an accessibility expert, yet the most errors you make are easy to find and do not need much time to fix. It will not replace an accessibility expert when you are required by law to follow certain levels, but it will make their work a lot simpler if the most common mistakes are already fixed.

The main reason to I wrote this post is to remember the different steps I had to take. Your challenges may be different, but if you follow the same structure, you should be able to tackle them as well.

Little Git Tricks: Switch to SSH Authentication

Over the last weeks I had a lot of problems with Git credentials in combination with Azure DevOps. Whenever I worked with a repository, my Git client asked for username and password. It got so annoying that I started to switch to SSH authentication and since then that problem never showed up again.

I focus on Azure DevOps in this post, but GitHub offers the same features in a slightly different location.

How to Change the HTTPS Certificate in IIS Express

Visual Studio creates a self-signed certificate for your web application that allows you to access your site over HTTPS. As long as you do not need to change anything, this magical configuration works like a charm. Unfortunately, when you need to change something, it is incredibly hard and the magic turns into a curse.