Definition: Accessibility is an IT non-functional requirement that ensures the system or application can be used by people with disabilities or impairments. This includes providing features such as screen readers, keyboard navigation, and alternative text for images. The goal of accessibility is to make sure that everyone, regardless of their abilities, can access and use the system or application. This requirement is important for compliance with accessibility laws and regulations, as well as for creating an inclusive and user-friendly experience for all users. Source: TOGAF Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html Additional information: According to the TOGAF specification, Accessibility is a non-functional requirement that refers to the ability of a system or application to be used by people with disabilities. This includes individuals with visual, auditory, physical, or cognitive impairments. Accessibility is an important consideration for any system or application, as it ensures that all users can access and use the system or application effectively. This requirement is particularly important for systems or applications that are used by the public, as they must comply with accessibility standards and guidelines set by regulatory bodies. To meet the Accessibility non-functional requirement, the system or application must be designed and developed with accessibility in mind. This includes providing alternative ways of accessing information, such as text-to-speech or screen readers for visually impaired users, and ensuring that the system or application is navigable using only a keyboard for users with physical impairments. The system or application must also comply with accessibility standards and guidelines, such as the Web Content Accessibility Guidelines (WCAG) and the Americans with Disabilities Act (ADA). Compliance with these standards and guidelines ensures that the system or application is accessible to all users, regardless of their abilities. In summary, the Accessibility non-functional requirement requires that the system or application be designed and developed with accessibility in mind, and comply with accessibility standards and guidelines to ensure that all users can access and use the system or application effectively. Example: One example of an IT non-functional requirement for accessibility could be that the website or application must be designed to be compatible with screen readers and other assistive technologies commonly used by people with disabilities. This could include ensuring that all images have alt text descriptions, using clear and concise language, and providing keyboard shortcuts for navigation. Additionally, the website or application should be designed with a high contrast color scheme and large, easy-to-read fonts to accommodate users with visual impairments. LOST view: Digital Solution Non-Functional Requirements Catalogue view Identifier: http://data.europa.eu/dr8/egovera/AccessibilityRequirement EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement ABB name: egovera:AccessibilityRequirement EIRA concept: eira:ArchitectureBuildingBlock Last modification: 2023-05-16 dct:identifier: http://data.europa.eu/dr8/egovera/AccessibilityRequirement dct:title: Accessibility Non-Functional Requirement