WCAG
15/09/2025
7 min reading time
15/09/2025
7 min reading time
15/09/2025
7 min reading time
WCAG (Web Content Accessibility Guidelines) are international digital accessibility standards that define how to create websites and applications accessible to people with disabilities. Developed by the W3C consortium, they form the foundation of a modern approach to inclusive digital design.
Table of contents
WCAG (Web Content Accessibility Guidelines) is a set of technical guidelines aimed at ensuring equal access to digital content for all users, regardless of their physical or cognitive abilities. These standards apply not only to users who are blind or visually impaired, but also to individuals with hearing impairments, motor limitations, cognitive disorders, or neurological conditions.
In the context of Polish legislation, WCAG has formed the legal basis for digital accessibility in the public sector since 2019. As of June 2025, the regulations will also apply to a significant portion of the private sector.
The first version introduced as mandatory in Poland for the public sector. It focuses on the basic aspects of accessibility, with particular emphasis on mobile devices and users with cognitive impairments.
The latest version, mandatory for the commercial sector from June 28, 2025. It introduces nine new criteria, including:
A key feature of WCAG 2.2 is backward compatibility—websites that meet the new standards automatically remain compliant with WCAG 2.1.
Information and user interface components must be presented in a way that is accessible to different senses:
Alternative text for images - every image must have descriptive alternative text or be marked as decorative. This is crucial for screen reader users.
Color contrast requirements - minimum 4.5:1 for normal text and 3:1 for large text. Enhanced contrast AA requires even higher values.
Captions and transcripts - all audio and video materials must have extended captions and transcripts for users with hearing impairments.
Resizable text - the text must be able to be enlarged to 200% without losing functionality, and at 400% zoom it must not require scrolling in two directions.
All interface components and navigation must be accessible to different modes of interaction:
Keyboard navigation - full keyboard navigation without focus traps. Focus indicators must be clearly visible. Skip links allow quick navigation between sections.
Timing controls - users must have control over temporary content. Auto-playing content can be paused or disabled.
Seizure prevention - no elements flashing more than 3 times per second, which could trigger epileptic seizures.
Input methods - support for various data entry methods, including voice control and eye tracking technologies.
Information and interface operation must be understandable to users with different cognitive abilities:
Language identification - the language of the website and individual sections must be programmatically specified for assistive technologies to function correctly.
Predictable navigation - predictable, uniform, and consistent navigation and page layouts. Elements must not change context without warning the user.
Input assistance - clear form labels, instructions for filling them out, and understandable error messages with suggestions for correction.
Error prevention - mechanisms preventing errors in critical processes such as financial transactions or the submission of legal documents.
The content must be compatible with various assistive technologies, both now and in the future:
Semantic HTML markup - using the correct HTML elements according to their semantic meaning instead of visual styling.
ARIA implementation - correct use of Accessible Rich Internet Applications attributes for complex interface components.
Assistive technology compatibility - testing with popular screen readers such as NVDA, JAWS, VoiceOver, and Dragon NaturallySpeaking.
Future-proof code - code resistant to technological changes and compatible with emerging technologies in the field of accessibility.
Basic accessibility requirements that every website should meet. This includes fundamental aspects such as alternative text and keyboard navigation.
Legally required level of compliance in Poland. Ensures good accessibility for most users with disabilities. Includes Level A requirements plus additional criteria for contrast, navigation, and functionality. (most common)
The highest level of availability, difficult to fully implement in practice. Recommended only for specialized applications where availability is critical.
Accessibility is based on semantic HTML markup using appropriate elements:
html
<header>, <nav>, <main>, <article>, <section>, <aside>, <footer> <h1>-<h6> w logicznej hierarchii <button>, <a>, <input> z odpowiednimi atrybutami
A set of attributes that extend HTML semantics:
role - definition of the role of an elementaria-label - available element namearia-describedby - additional descriptionaria-hidden - concealing elements from assistive technologiesWCAG 2.2 introduces new requirements for responsiveness:
Future version of standards, currently under development:
Compliance with WCAG is not only a legal requirement, but also an investment in:
Research shows that investments in accessibility bring:
WCAG is a fundamental standard of modern web development. It is not just a technical legal requirement, but reflects the philosophy of inclusive design, which makes the internet accessible to everyone.
Proper implementation of WCAG requires a holistic approach—from the design phase, through development, to testing and maintenance. It is an investment that benefits not only users with disabilities, but everyone who uses our digital products.
In the context of upcoming legal changes in Poland, understanding and implementing WCAG is becoming a key competency for any team involved in creating digital solutions.
Questions?