WAS key terms

Frameworks explaining disability: medical model views disability as a defect to fix; social model sees barriers in society; biopsychosocial integrates both; human rights model emphasizes equality and participation.

A framework asserting that disability is caused by societal barriers (attitudes, environments, systems) rather than by an individual's impairment. Accessibility removes these barriers to enable full participation.

A perspective that treats disability as a health condition or deficit located in the individual, requiring medical treatment or cure. It often overlooks environmental and social factors that affect participation.

Obstacles that prevent people with disabilities from accessing content or functionality, including physical, sensory, cognitive, technological, and attitudinal barriers. Identifying and removing them is central to accessibility work.

Web Content Accessibility Guidelines, a standard from the W3C defining how to make web content accessible. It is organized under four principles (Perceivable, Operable, Understandable, Robust) with testable success criteria at levels A, AA, and AAA.

A testable requirement in WCAG that specifies what must be true for content to conform at a given level. Each has a number (e.g., 1.1.1) and is categorized by conformance level.

A rank (A, AA, or AAA) indicating the degree of WCAG compliance. Level A is the minimum; AA is commonly required by law and policy; AAA is the highest and not always achievable for all content.

The first WCAG principle: information and user interface components must be presentable to users in ways they can perceive, such as through text alternatives, captions, or adaptable layouts.

The second WCAG principle: user interface components must be operable, meaning users can interact via keyboard, have enough time, and are not subjected to seizures or navigation traps.

The third WCAG principle: information and operation of the user interface must be understandable, including readable text, predictable behavior, and input assistance to prevent and correct errors.

The fourth WCAG principle: content must be robust enough to work reliably with current and future user agents, including assistive technologies, often achieved through valid, semantic markup.

A textual substitute for non-text content (images, charts, controls) that conveys equivalent meaning and function, enabling screen reader users and others who cannot see the content to understand it.

The property that all functionality can be operated through a keyboard interface without requiring specific timings for individual keystrokes, benefiting keyboard-only users and many assistive technology users.

A success criterion requiring that any keyboard-operable user interface has a visible focus indicator, so users know which element currently has focus. Removing outlines without replacement violates it.

Using HTML elements according to their meaning (e.g.,

, , ) so browsers and assistive technologies can convey structure and roles automatically, reducing the need for ARIA.

The ordered structure of heading levels (h1–h6) that outlines page content. Proper nesting helps screen reader users navigate and understand relationships; skipping levels can confuse.

The HTML attribute (alt) on that provides a text alternative. It should describe the image's purpose; decorative images use empty alt (alt="") to be ignored by assistive technology.

Semantic HTML elements (header, nav, main, aside, footer, section with accessible name) that define page areas, enabling screen reader users to jump between regions efficiently.

The name of a user interface component as computed from author-provided labels (e.g., aria-label, , alt) and used by assistive technology to identify the control to the user.

Accessible Rich Internet Applications, a W3C specification providing attributes (roles, states, properties) to enhance accessibility of custom widgets and dynamic content when native HTML semantics are insufficient.

An ARIA attribute (role) that defines the type of widget or landmark (e.g., button, navigation) so assistive technology can announce its purpose. Native HTML elements have implicit roles.

A dynamic property (e.g., aria-expanded, aria-checked) that indicates the current condition of a widget, which must be updated via script as the user interacts.

An ARIA feature (aria-live) that announces dynamically updated content to screen reader users without moving focus. Politeness levels (off, polite, assertive) control urgency.

Additional descriptive information for a component, provided via aria-describedby or aria-description, supplementing the accessible name with context or instructions.

Assistive technology that converts digital text and interface elements into synthesized speech or braille, enabling blind and low-vision users to interact with computers and mobile devices.

Hardware or software that helps people with disabilities perform tasks, such as screen readers, magnifiers, switch controls, and speech recognition. Compatibility is essential for accessibility.

A structure created by browsers from the DOM that exposes roles, names, states, and properties to assistive technologies. Testing often involves inspecting this tree.

Using tools (e.g., axe, Lighthouse) to scan code for detectable WCAG violations. It catches only a subset of issues and must be supplemented by manual and user testing.

Human evaluation of accessibility using techniques like keyboard navigation, screen reader checks, and visual inspection, necessary to catch issues automated tools miss.

The numerical difference in luminance between foreground and background colors, expressed as a ratio (e.g., 4.5:1). WCAG sets minimum ratios to ensure readability for low-vision users.

An approach using flexible grids, media queries, and fluid images so content adapts to different screen sizes and zoom levels, supporting accessibility across devices.

A WCAG success criterion requiring content to be usable without two-dimensional scrolling at a width equivalent to 320 CSS pixels, benefiting users who zoom or use small screens.

The ability to enlarge content up to 200% without loss of content or functionality, a requirement under WCAG. It helps low-vision users read text and see details.

An organization's formal statement of commitment to accessibility, defining standards, responsibilities, and processes. It establishes accountability and guides consistent practice.

The structures, roles, and processes an organization uses to manage accessibility, including policies, training, monitoring, and remediation planning, ensuring sustained compliance.

A systematic evaluation of a digital product against accessibility standards, combining automated, manual, and user testing to identify barriers and inform remediation priorities.

The process of fixing accessibility defects identified in an audit, including code changes, content updates, and process improvements, often prioritized by severity and impact.

A public declaration describing a site's accessibility status, known limitations, and contact for feedback. It supports transparency and accountability to users.