Accessibility statement

On this page I describe the current accessibility status of the site, what I do to improve it, and how you can contact me if you run into problems.

Measures to support accessibility

I, Kim Branzell, want branzell.kim to be usable for as many people as possible.

To support accessibility, I:

  • Plan and design content with accessibility in mind from the start
  • Use semantic HTML and ARIA only when it is needed
  • Try to keep navigation, layout, and interaction patterns consistent across pages
  • Test pages with a keyboard and fix focus and tab order issues
  • Aim for clear link text and meaningful headings
  • Write alt text for images that carry information
  • Avoid autoplaying audio and flashing content
  • Use automated accessibility tools as a first check and follow up with manual testing

Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. WCAG has three levels of conformance: Level A, Level AA, and Level AAA.

  • Target standard: WCAG 2.2 Level AA
  • Current status: Partially conformant

Partially conformant means that some parts of the content do not fully meet all Level AA success criteria yet.

Known issues and areas for improvement

I am aware that some parts of the website may still cause problems:

  • Some older posts may not yet follow the same heading structure and link text patterns as newer content
  • Some code samples, embeds, or third-party widgets may not be fully accessible
  • There may be occasional contrast issues where colors have not yet been updated

If you find anything that blocks you, I want to know so I can fix it.

Feedback

I welcome feedback on the accessibility of my website.

Please contact me if you:

  • cannot access parts of the site
  • find content that is hard to understand with assistive technology
  • notice any other accessibility barrier

You can reach me here:

I try to respond within 2–3 business days.

If your request is about a specific page, it helps if you include:

  • the page URL
  • what you tried to do
  • which browser, device, and assistive technology you used (if any)

Technical specifications

The accessibility of my website relies on the following technologies working together with your browser and any assistive tools you use:

  • HTML
  • WAI-ARIA
  • CSS
  • JavaScript

These technologies are needed for the website to follow the accessibility standards I aim for.

Assessment approach

I assess the accessibility of branzell.kim by:

  • Reviewing new content and features with accessibility in mind
  • Using automated tools to flag common issues
  • Doing manual checks, such as keyboard testing and structural review of pages

Date and future updates

  • This statement was created on 22 November 2025 using the W3C Accessibility Statement Generator Tool and then edited by me.
  • I plan to review and update this statement at least once per year, or when I make larger changes to the site.