Implementing accessible card components
The card is one of the most common components in a UI (user interface). A card groups the information about a single item or topic. You use cards when a page shows several items at once.
Software Engineer & Accessibility Specialist
Dark mode
I build accessible software that works the way people do
I combine web accessibility expertise with modern frontend engineering and AI-assisted workflows.
The card is one of the most common components in a UI (user interface). A card groups the information about a single item or topic. You use cards when a page shows several items at once.
AI-generated code (code generated with Artificial Intelligence) often fails to meet WCAG (Web Content Accessibility Guidelines). That part is no surprise. Most websites do not meet WCAG either, so the training data is full of inaccessible code.
HTML tables have a bad reputation. People often see them as bad for accessibility, bad practice, and outdated.
I saw a post on LinkedIn about how some modal accessibility is broken because they trap focus, failing the Web Content Accessibility Guidelines (WCAG) success criterion 2.1.2 No Keyboard Trap. This is wrong, but it’s easy to understand how someone would reach this conclusion.
The WebAIM Million 2026 is a report that takes data from the top one million websites every year. The home page of each site is analysed automatically, which doesn’t produce a full picture of all possible accessibility issues. But it is reliable because it removes human biases and returns raw data that allows us to make comparisons and spot trends.
Accessibility affects almost every stage in a project. This is usually explained as accessibility being necessary before, during, and after making the project. This is an elegant way to explain how accessibility needs to be considered in the planning phase, during development, and as part of Quality Assurance (QA) when the project is already live.
When remediating accessibility issues in an existing project, making additions is usually accepted without hesitation. If asked to add text alternatives, visual elements, instructions, or captions to a video, there is rarely a conflict. Even applying complex ARIA (Accessible Rich Internet Applications) patterns is never frowned upon.