Abstract
Digital accessibility is not merely a technical feature but a right that enables all people, regardless of their abilities, to use the Internet without barriers. This article examines the foundations of web accessibility under the World Wide Web Consortium (W3C) standards, breaking down the four guiding principles (POUR), and offering an evaluation methodology and a technical glossary.
1. Introduction to Web Accessibility
Web accessibility is defined as the quality that allows people with various disabilities (visual, auditory, motor, or cognitive) and those with temporary difficulties to navigate and interact with digital sites and tools effectively. In a context where technology advances rapidly, digital exclusion becomes a significant social barrier.
The international reference standard is the Web Content Accessibility Guidelines (WCAG), developed by the Web Accessibility Initiative (WAI) of the W3C,. These guidelines not only benefit people with disabilities but also improve the general user experience and optimize search engine positioning. Current versions, such as WCAG 2.1 and 2.2, are backward compatible and aim to cover emerging needs, such as mobile accessibility,.
2. The Four Fundamental Principles (POUR)
The WCAG are structured around four principles that act as pillars for inclusive design. If any of these are not met, people with disabilities will not be able to use the web.
2.1. Perceptible
Information and user interface components must be presented in such a way that users can perceive them with their available senses,.
• Text Alternatives: All non-text content (images, graphics) must have a text alternative that serves the same purpose. For example, a screen reader will read the description “a brown dog playing” instead of simply indicating “image”,.
• Time-Based Media: Recorded audio and video content require transcripts, synchronized captions, or audio descriptions to avoid excluding users with hearing or visual impairments,,.
• Use of Color and Contrast: Information must not be conveyed solely through color. Additionally, there must be sufficient contrast between text and background (minimum ratio of 4.5:1 for normal text) to ensure readability,.
2.2. Operable
User interface components and navigation must be usable; that is, the interface cannot require interaction that the user cannot perform,.
• Keyboard Accessibility: All content must be functional using a keyboard, without requiring a mouse. This is crucial for people with motor or visual impairments,.
• No Keyboard Traps: Keyboard focus must not get “trapped” in a component without the ability to exit.
• Focus Indicator: There must be a clear visual indicator (such as a border or color change) showing which element has the keyboard focus,.
• Sufficient Time: Users must be provided with enough time to read and use content, allowing them to pause or stop automatic movements.
2.3. Understandable
Information and the operation of the user interface must be clear and predictable,.
• Readability and Predictability: Language should be clear, avoiding unnecessary jargon, and the design must be consistent throughout the site,.
• Input Assistance: Forms must have clear labels, precise instructions, and mechanisms to identify and correct errors, such as audible and visual alerts,.
• Cognitive Accessibility: People with intellectual disabilities must be considered by offering environments that are easy to understand, avoiding stress derived from complex instructions or unpredictable environments,.
2.4. Robust
Content must be robust enough to be interpreted reliably by a wide variety of user agents, including current and future assistive technologies,.
• Compatibility: This is achieved through the use of valid code (HTML5, CSS) that allows assistive technologies (such as screen readers) to access content across different platforms and browsers,.
• Semantic Markup: It is essential to give non-standard design elements a proper name, role, and value so that assistive tools can interpret them correctly.
3. Conformance Levels and Evaluation
The guidelines establish three levels of conformance:
• Level A: The minimum necessary for a site to be accessible; without it, absolute barriers exist,.
• Level AA: The recommended standard and required by most international legislation; meets the needs of most users,.
• Level AAA: The highest level, ideal for specific contexts, but difficult to implement across all types of content,.
To ensure compliance, an evaluation methodology is recommended, consisting of automatic evaluation (software), manual evaluation (experts), and user testing with real users with disabilities,.
4. Hypothetical Example: “The Digital Invoice”
Imagine a utility service that sends monthly invoices via email.
Scenario A (Inaccessible): The user receives an email with an attachment named “invoice_jan.pdf”. Upon opening it, it is a scanned image of the paper document inside a PDF.
• Perceptible Failure: A blind user using a screen reader will only hear “image” or nothing at all, as the text is not real text but pixels,.
• Operable Failure: If the user tries to copy the account number using the keyboard, they cannot select the text.
Scenario B (Accessible – Solution): The company implements an “Accessible PDF” or “Tagged PDF” system.
• Solution: The document now contains an invisible layer of tags that defines the structure (headings, tables, lists).
• Result: When the blind user navigates with their screen reader:
- The software announces “Heading Level 1: January Invoice”.
- Upon reaching the consumption table, the reader indicates which row and column they are in (e.g., “Column Amount: 50 dollars”).
- The company logo has alternative text describing it.
- The color contrast between the amount text and the background meets the 4.5:1 ratio, aiding users with low vision.
5. Glossary of Terminology
Below are definitions of key terms used in the field of digital accessibility, based on the consulted sources:
• Cognitive Accessibility: Properties of environments, processes, and texts that make them easy to understand, benefiting people with difficulties in comprehension, memory, or information processing.
• Easy Read: Methodology for creating and validating documents with the aim of facilitating comprehension for people with reading difficulties.
• Screen Reader: Assistive technology software that reads screen content aloud, primarily used by people who are blind or have low vision.
• Tagged PDF: A PDF file that includes a logical structure layer (tags) allowing assistive technologies to interpret the reading order and semantics of the document (headings, tables, images).
• POUR: Acronym for the four principles of accessibility: Perceptible, Operable, Understandable, and Robust.
• Assistive Technology: Devices or software (such as Braille keyboards, screen magnifiers, or voice control) that help people with disabilities interact with the digital environment,.
• Keyboard Trap: A situation where a user navigating with a keyboard enters a component or area of the page and cannot exit it using only the keyboard.
• Alternative Text (Alt Text): A brief textual description added to an image or non-text content that conveys the same information or serves the same purpose.
• W3C (World Wide Web Consortium): An international community that develops open standards to ensure the long-term growth of the Web.
• WCAG (Web Content Accessibility Guidelines): Technical international standard that explains how to make web content accessible,.
References
• Agesic. (2022, August). Metodología de Evaluación de accesibilidad: Programa de accesibilidad en entornos digitales. GUB.UY. [Source 194-218]
• Crawford Technologies. (n.d.). Comprender el formato PDF accesible: estrategias sostenibles para las comunicaciones con los clientes. [Source 17-68]
• Fundación Qualis. (n.d.). Guía de pautas de accesibilidad web. [Source 73-84]
• itgrarte fundación. (2019, November 8). Los 4 principios de la Accesibilidad Web. [Source 189-193]
• Luján Mora, S. (n.d.). Resumen de WCAG 2.0, 2.1 y 2.2. Accesibilidad Web. [Source 237-239]
• Ministerio de Asuntos Económicos y Transformación Digital. (n.d.). Guía Técnica para la verificación de criterios WCAG 2.1 – Principio 1: Perceptible. Observatorio de Accesibilidad, Portal de la Administración Electrónica. [Source 85-188]
• Tejeda Tena, J. M., & CEDEC. (2020, January 28). Discapacidad intelectual y accesibilidad cognitiva. Cedec – INTEF. [Source 1-16]
• The Good Manager. (2021). El 4º principio WCAG: Robusto. [Source 69-72]
• Torresburriel Estudio. (2024, July 2). Navegación por teclado: cómo asegurar la usabilidad sin un ratón. [Source 219-236]
• Web Accessibility Initiative (WAI). (2025, June 3). Sumario de WCAG 2. W3C. [Source 240-253]