Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the UserInterface Source: ISO/IEC/IEEE 42010:2022 Source reference: https://www.iso.org/standard/74393.html Additional information: Accessibility in the context of usability refers to the design and implementation of a software system that ensures equal access and usability for all users, including those with disabilities or impairments. It focuses on creating an inclusive user experience by removing barriers and providing accommodations to enable individuals with disabilities to perceive, understand, navigate, and interact with the system effectively. Example: Title: Accessibility Architecture Decision Record (ADR) LOST view: Digital Solution Architecture Decisions Catalogue view Identifier: http://data.europa.eu/dr8/egovera/AccessibilityGoal EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal ABB name: egovera:AccessibilityGoal EIRA concept: eira:ArchitectureBuildingBlock Last modification: 2023-07-06 dct:identifier: ADR-20230606091024752 dct:title: Architecture Decision Record about UserInterface eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons. eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how. eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)] eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.