Accessibility statement

Last updated: 17.3.2023.

Accessibility features

• You can navigate the whole website with just a keyboard. Yay!
• Skip to main content and jump back to the top links have been implemented.
• Images have a caption and an alternative text. A long description is provided with a <details> element when needed.
• The website is responsive to different viewports and levels of zooming.
• The pages are clearly structured using landmarks and navigation has been labeled.
• Every link is underlined and underlining hasn't been used in any other meaning. Link text describes where the link leads and in which language the content is in.
• Contrast has been checked with the WAVE tool. Also used my own eyes.
• At the time of last update (17.3.2023), there is no audio, animations or video present on the website. They would have alternative texts or transcriptions otherwise.
• Math is implemented using MathJax, or plain MathML. In Finnish an AsciiMath presentation of math is provided.

Failures to meet accesibility standards (WCAG 2.1)

• 1.4.10 Reflow (level AA) is not met with the codeblock highlighting.
  • Actions to fix: I have to find out how prism.js can be configured.
• 1.4.3 Contrast (Minimum) some images with text (mostly screenshots) on them also don't meet the requirements.
  • Images from different applications have a set of colors and contrast, so can't do anything about that.
  • Text in images is explained in plain text before or after the image.
• 2.3.3 Animation from Interactions (level AAA) might not be met. When links are hovered over or focused on, they have an easing out effect.
  • Actions: I have to find out if this might cause motion sickness.
• 2.4.5 Multiple Ways (level AA) is not met on every web page on this website.
  • Actions to fix: Implementing a sitemap. (Update on 17.3.2023: implemented the xml version, so a proper one isn't far away!)
• 3.1.2 Language of Parts (level AA) is not met when viewing pages that display posts with a certain tag.
  • Actions to fix: I don't know yet. I could include a <span> element that defines the language of every tag, but that feels cumbersome. Maybe there is a more elegant way of doing it.

Other accessibility concerns

I noticed that I have been using a made up <date> element, when I should been using <time datetime="[date time]">, which is kind of embarrassing. Well, it's almost fixed now. I should implement proper date handling for the blog post previews.

Also the list of fixes below really shows why a web development hobbyist shouldn't attempt a bilingual website, since the implemnetation is hard already. I should redesign my site.

Implemented accessibility fixes

List of fixes

• 3.1.2 Language of Parts (level AA) was not met on blog breadcrumbs with mixed languages. This is now fixed and mixed languages should work properly. Fixed on 17.3.2023.
• 3.1.2 Language of Parts (level AA) was not met on blog posts with mixed languages in headings. This is now fixed and mixed languages should work properly. Fixed on 8.10.2022.
• 3.1.2 Language of Parts (level AA) was not met on tags. Now there are separate tags in Finnish and English. Fixed on 11.10.2022.
• 1.4.3 Contrast (level AA) was not met with the codeblock highlighting. I implemented a prism-overrides.css file based on a CSS tricks article. Fixed on 16.1.2023.
• 3.1.2 Language of Parts (level AA) was not met on screen reader only text that's part of "Continue reading" text in the blog post previews. Fixed on 3.2.2023.

Testing

Testing has been done in Chrome and Firefox, since I moved to using Firefox.

I have used an automatic testing tool WAVE to audit my site. Be aware that automated tools only catch a small part of accessibility issues.

Parts of the site have also been tested with a screen reader NVDA by me.

Did you find an accessibility issue?

Please reach out to me in any way through the socials below.