Last CallLast Call Pool

Design Stage

Speed of progress at the cost of technological exclusion — no-code, UI libraries, AI tools and web accessibility

September 17, 2025 11:50 AM

Long Lecture

🇬🇧 English

Wisła

About

In my presentation, I will discuss how the rapid advancement of web technologies leads to compromises in creating accessible user experiences. I will talk about no-code tools and the way they may impact inclusive design. I will also mention UI libraries and issues that they cause when used without prior consideration. I will make an argument for AI excluding many users from the technological race due to a steep learning curve. Lastly, I will offer some ideas on addressing these issues.

‍

Talk by

Photo of Wojtek Kutyła

Independent Web Accessibility Specialist at Human Thing Ltd

Watch the full talk

Watch this WaysConf session, then continue with related talks or explore the current programme.

Explore the 2026 agenda More WaysConf recordings

From the recording

Talk in brief

This talk argues that faster production through no-code tools, UI libraries, and AI can quietly increase technological exclusion when teams stop examining the output. Non-semantic markup, weak information architecture, generic components, and inaccessible generated interfaces transfer the cost of speed to disabled people and others at the edge of the process. The speaker connects these failures with workload, deadlines, skill shortages, and organizational incentives rather than blaming individual designers. The proposed response is reflective practice: learn the fundamentals, identify who bears each shortcut, sometimes choose correctness before velocity, and use collective action to make accessible work normal.

Key takeaways

01
Faster tools can reduce critical attention
Automation accelerates output, but it can also distance practitioners from the structure and consequences of what they ship.
Watch from 4:30
02
Semantic structure remains essential
Generated layouts built from undifferentiated containers can break heading navigation, information hierarchy, and assistive-technology access.
Watch from 9:39
03
Accessibility debt has organizational causes
Heavy workload, unrealistic deadlines, missing skills, and pressure to demonstrate progress create conditions where exclusion becomes predictable.
Watch from 20:40
04
Every shortcut transfers a cost
Teams should ask who will struggle because of a choice, since the person paying for speed is often absent from the delivery conversation.
Watch from 26:20
05
Doing it right can later become fast
Accessible practice initially requires learning, but repeated correct work builds fluency and makes quality a normal part of delivery.
Watch from 26:39

Video chapters

0:20A long view of web accessibility
The speaker introduces experience across organizations and concern about the current pace of change.
4:20Acceleration without enough reflection
AI and other productivity tools are examined as influences on memory, judgment, and design attention.
9:20How generated interfaces exclude
Non-semantic HTML and damaged information architecture show the practical cost of unexamined output.
14:59The web's promise of access for everyone
The talk contrasts the inclusive ideal of the web with the experience many products currently provide.
20:19Deadlines, workload, and missing capability
Systemic pressures explain why teams repeatedly choose short-term delivery over accessible foundations.
25:39Identifying who pays for speed
The ethical question becomes concrete by tracing the people who bear the consequences of shortcuts.
26:39Choosing right before fast
Learning accessible practice may slow early work but creates fluency and reliability over time.
32:22Questions, examples, and collective hope
The closing discussion moves from accessible examples toward how coordinated action changes systems.

Read edited transcript highlights

These concise notes were edited from automatic captions and checked against the talk structure. They are not a verbatim transcript.

Automation can weaken inspection

The concern is not simply that AI or no-code tools exist. It is that speed can remove the pause in which a practitioner understands and questions the result. When the tool supplies structure, copy, or code, the team may accept output it could not explain. Accessibility failures then become harder to notice because the people shipping the interface feel less ownership of its underlying behavior.

Watch from 4:20

A screen is more than visible arrangement

An interface can appear complete while its document structure is unusable. Containers without semantic meaning, broken heading levels, and weak information architecture obstruct people who navigate through assistive technology. The example shows why visual similarity is an inadequate quality check: the underlying relationships must also communicate purpose and order.

Watch from 9:20

Exclusion is produced by the operating environment

Practitioners work under heavy loads, short deadlines, and expectations to return from every learning opportunity with immediate deliverables. Teams may also lack accessibility skills or access to specialists. These conditions do not excuse inaccessible work, but they explain why individual goodwill is insufficient. The organization must create time, standards, and support for quality.

Watch from 20:19

The absent user still pays

A shortcut always has an effect somewhere downstream. The person who struggles with the resulting interface is rarely present when the team trades correctness for speed. Asking who bears that cost changes the discussion from abstract compliance to product responsibility. It makes exclusion a consequence of a specific choice rather than an unfortunate property of technology.

Watch from 25:39

Correct practice develops its own velocity

Learning accessible methods can make early work slower because teams must acquire unfamiliar skills and reconsider familiar patterns. With repetition, the fundamentals become routine. The speaker argues that doing work correctly is not permanently opposed to speed; over time, competence allows teams to move quickly without repeatedly creating barriers that require expensive repair.

Watch from 26:39

Explore WaysConf 2026

View the agenda

Get tickets