Latest posts:

Posted on:

Identify Input Purpose (WCAG 1.3.5) on mobile applications

Autocomplete and correct keyboard layout when filling out forms are simple and powerful helpers to make less errors when filling out forms. They benefit everybody, but they are even more appreciated by people with different disabilities. Web support is there for years, but what about native mobile applications?

Posted on:

I will miss WCAG 4.1.1 a bit, but it’s retirement will allow us to focus on more important problems

I’ve learned that WCAG can’t be changed a lot and that only additions are allowed. Now I’ve read that WCAG 2.2 will have the 4.1.1 success criterion (parsing) removed. My first reaction was – why and how will we work with problems in HTML then? On the other hand we should probably be happy we can focus on other problems that are more related directly to accessibility.