{"id": "AGENTS.md::document-preamble", "title": "Document preamble", "text": "---\ntitle: \"Agent Instructions for Accessible Typography and Brand Communication\"\nversion: \"1.1\"\nauthor:\n name: \"Double-FW, Gareth Ford Williams\"\ndate: \"2026-11-06\"\nlicense: \"MIT\"\nlanguage: \"en\"\nrepository: \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\"\nartifact_type: \"knowledge-base/agent-guidance\"\nuse_case:\n - \"brand-design\"\n - \"communications-design\"\n - \"marketing-design\"\n - \"publishing-design\"\n - \"editorial-design\"\n - \"typography-evaluation\"\n - \"ai-agent-guidance\"\npurpose: \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\"\n---\n\n", "record_type": "agent_guidance_with_file_level_mit", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "AGENTS.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/AGENTS.md", "source_start_line": 1, "source_end_line": 21, "source_document_sha256": "69cd216f67c0ed7060ab381137f9305605b2a8c6fe9b7a89ea6d06770e9989d8", "text_sha256": "032ffb038d58927e404e90fa64387cfeee76f83ad6a962978d4201732e0b62ef", "heading_path": [], "metadata_json": "{\"artifact_type\": \"knowledge-base/agent-guidance\", \"author\": {\"name\": \"Double-FW, Gareth Ford Williams\"}, \"date\": \"2026-11-06\", \"language\": \"en\", \"license\": \"MIT\", \"purpose\": \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\", \"repository\": \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\", \"title\": \"Agent Instructions for Accessible Typography and Brand Communication\", \"use_case\": [\"brand-design\", \"communications-design\", \"marketing-design\", \"publishing-design\", \"editorial-design\", \"typography-evaluation\", \"ai-agent-guidance\"], \"version\": \"1.1\"}", "declared_source_license": "MIT", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "{\"name\": \"Double-FW, Gareth Ford Williams\"}", "source_document_intro": "---\ntitle: \"Agent Instructions for Accessible Typography and Brand Communication\"\nversion: \"1.1\"\nauthor:\n name: \"Double-FW, Gareth Ford Williams\"\ndate: \"2026-11-06\"\nlicense: \"MIT\"\nlanguage: \"en\"\nrepository: \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\"\nartifact_type: \"knowledge-base/agent-guidance\"\nuse_case:\n - \"brand-design\"\n - \"communications-design\"\n - \"marketing-design\"\n - \"publishing-design\"\n - \"editorial-design\"\n - \"typography-evaluation\"\n - \"ai-agent-guidance\"\npurpose: \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["AGENTS.md", "README.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "AGENTS.md::agents-md", "title": "AGENTS.md", "text": "# AGENTS.md\n\nThis repository is a knowledge base on accessible typography for UX and brand systems. This file defines the operating rules for AI agents, editors, and reviewers working in this repository.\n\nThis document is advisory and repository-local. It is not an executable policy engine, a deployment configuration, a compliance system, or a guarantee that any external service or human approval process exists. The repository does not currently include a runtime enforcement mechanism for these instructions, so they should be treated as a decision aid and review standard.\n\n", "record_type": "agent_guidance_with_file_level_mit", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "AGENTS.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/AGENTS.md", "source_start_line": 22, "source_end_line": 27, "source_document_sha256": "69cd216f67c0ed7060ab381137f9305605b2a8c6fe9b7a89ea6d06770e9989d8", "text_sha256": "efbffea8713d78f2b8120c616ada90ba3e8b26a8103c05a16585b2dd8732c04c", "heading_path": ["AGENTS.md"], "metadata_json": "{\"artifact_type\": \"knowledge-base/agent-guidance\", \"author\": {\"name\": \"Double-FW, Gareth Ford Williams\"}, \"date\": \"2026-11-06\", \"language\": \"en\", \"license\": \"MIT\", \"purpose\": \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\", \"repository\": \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\", \"title\": \"Agent Instructions for Accessible Typography and Brand Communication\", \"use_case\": [\"brand-design\", \"communications-design\", \"marketing-design\", \"publishing-design\", \"editorial-design\", \"typography-evaluation\", \"ai-agent-guidance\"], \"version\": \"1.1\"}", "declared_source_license": "MIT", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "{\"name\": \"Double-FW, Gareth Ford Williams\"}", "source_document_intro": "---\ntitle: \"Agent Instructions for Accessible Typography and Brand Communication\"\nversion: \"1.1\"\nauthor:\n name: \"Double-FW, Gareth Ford Williams\"\ndate: \"2026-11-06\"\nlicense: \"MIT\"\nlanguage: \"en\"\nrepository: \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\"\nartifact_type: \"knowledge-base/agent-guidance\"\nuse_case:\n - \"brand-design\"\n - \"communications-design\"\n - \"marketing-design\"\n - \"publishing-design\"\n - \"editorial-design\"\n - \"typography-evaluation\"\n - \"ai-agent-guidance\"\npurpose: \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["AGENTS.md", "README.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "AGENTS.md::agents-md-1-purpose-and-audience", "title": "1. Purpose and audience", "text": "## 1. Purpose and audience\n\nThis file applies to AI assistants and human contributors who:\n\n- write or revise typography guidance in this repository;\n- evaluate or compare typefaces, type systems, or editorial approaches;\n- draft brand, marketing, communication, or publishing recommendations based on the repository’s material; and\n- support review of content that affects readability, accessibility, or brand communication.\n\nIt does not authorize external publishing, deployment, legal claims, compliance assertions, or operational actions beyond the repository itself.\n\n", "record_type": "agent_guidance_with_file_level_mit", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "AGENTS.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/AGENTS.md", "source_start_line": 28, "source_end_line": 38, "source_document_sha256": "69cd216f67c0ed7060ab381137f9305605b2a8c6fe9b7a89ea6d06770e9989d8", "text_sha256": "c4c1d06e674f1c03d355e5010feb9bca7319bf7b3e573cb2f3f2a9ed005ef9d2", "heading_path": ["AGENTS.md", "1. Purpose and audience"], "metadata_json": "{\"artifact_type\": \"knowledge-base/agent-guidance\", \"author\": {\"name\": \"Double-FW, Gareth Ford Williams\"}, \"date\": \"2026-11-06\", \"language\": \"en\", \"license\": \"MIT\", \"purpose\": \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\", \"repository\": \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\", \"title\": \"Agent Instructions for Accessible Typography and Brand Communication\", \"use_case\": [\"brand-design\", \"communications-design\", \"marketing-design\", \"publishing-design\", \"editorial-design\", \"typography-evaluation\", \"ai-agent-guidance\"], \"version\": \"1.1\"}", "declared_source_license": "MIT", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "{\"name\": \"Double-FW, Gareth Ford Williams\"}", "source_document_intro": "---\ntitle: \"Agent Instructions for Accessible Typography and Brand Communication\"\nversion: \"1.1\"\nauthor:\n name: \"Double-FW, Gareth Ford Williams\"\ndate: \"2026-11-06\"\nlicense: \"MIT\"\nlanguage: \"en\"\nrepository: \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\"\nartifact_type: \"knowledge-base/agent-guidance\"\nuse_case:\n - \"brand-design\"\n - \"communications-design\"\n - \"marketing-design\"\n - \"publishing-design\"\n - \"editorial-design\"\n - \"typography-evaluation\"\n - \"ai-agent-guidance\"\npurpose: \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["AGENTS.md", "README.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "AGENTS.md::agents-md-2-scope", "title": "2. Scope", "text": "## 2. Scope\n\nThis repository is primarily a content and synthesis project. The instructions below therefore focus on:\n\n- evidence-based typography guidance;\n- clear separation of evidence, assumption, and inference;\n- readable and maintainable repository content; and\n- human accountability for consequential recommendations.\n\nThis file does not define application or deployment behaviour for a production system unless a future repository implementation explicitly adds it.\n\n", "record_type": "agent_guidance_with_file_level_mit", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "AGENTS.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/AGENTS.md", "source_start_line": 39, "source_end_line": 49, "source_document_sha256": "69cd216f67c0ed7060ab381137f9305605b2a8c6fe9b7a89ea6d06770e9989d8", "text_sha256": "daa96d26d2039980535498ee54624a96158e7e68cac61951cf250e8749e3ff6f", "heading_path": ["AGENTS.md", "2. Scope"], "metadata_json": "{\"artifact_type\": \"knowledge-base/agent-guidance\", \"author\": {\"name\": \"Double-FW, Gareth Ford Williams\"}, \"date\": \"2026-11-06\", \"language\": \"en\", \"license\": \"MIT\", \"purpose\": \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\", \"repository\": \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\", \"title\": \"Agent Instructions for Accessible Typography and Brand Communication\", \"use_case\": [\"brand-design\", \"communications-design\", \"marketing-design\", \"publishing-design\", \"editorial-design\", \"typography-evaluation\", \"ai-agent-guidance\"], \"version\": \"1.1\"}", "declared_source_license": "MIT", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "{\"name\": \"Double-FW, Gareth Ford Williams\"}", "source_document_intro": "---\ntitle: \"Agent Instructions for Accessible Typography and Brand Communication\"\nversion: \"1.1\"\nauthor:\n name: \"Double-FW, Gareth Ford Williams\"\ndate: \"2026-11-06\"\nlicense: \"MIT\"\nlanguage: \"en\"\nrepository: \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\"\nartifact_type: \"knowledge-base/agent-guidance\"\nuse_case:\n - \"brand-design\"\n - \"communications-design\"\n - \"marketing-design\"\n - \"publishing-design\"\n - \"editorial-design\"\n - \"typography-evaluation\"\n - \"ai-agent-guidance\"\npurpose: \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["AGENTS.md", "README.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "AGENTS.md::agents-md-3-authority-and-conflict-resolution", "title": "3. Authority and conflict resolution", "text": "## 3. Authority and conflict resolution\n\nWhen instructions conflict, apply the following order:\n\n1. Repository-local content and explicit repository conventions.\n2. More specific instructions that apply to a narrower task or directory.\n3. User instructions that are compatible with the repository and do not contradict the repository’s stated purpose.\n4. General best practice, when no repository guidance covers the issue.\n\nIf a requirement is missing, unknown, or not supported by evidence, the agent MUST say so explicitly. It MUST NOT invent approvals, enforcement, services, credentials, owners, or review processes that do not exist in the repository.\n\n", "record_type": "agent_guidance_with_file_level_mit", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "AGENTS.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/AGENTS.md", "source_start_line": 50, "source_end_line": 60, "source_document_sha256": "69cd216f67c0ed7060ab381137f9305605b2a8c6fe9b7a89ea6d06770e9989d8", "text_sha256": "499d9d9b46181471c5d4e133aa31ca19bfd4bf454bee15561c27044112e8ccc3", "heading_path": ["AGENTS.md", "3. Authority and conflict resolution"], "metadata_json": "{\"artifact_type\": \"knowledge-base/agent-guidance\", \"author\": {\"name\": \"Double-FW, Gareth Ford Williams\"}, \"date\": \"2026-11-06\", \"language\": \"en\", \"license\": \"MIT\", \"purpose\": \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\", \"repository\": \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\", \"title\": \"Agent Instructions for Accessible Typography and Brand Communication\", \"use_case\": [\"brand-design\", \"communications-design\", \"marketing-design\", \"publishing-design\", \"editorial-design\", \"typography-evaluation\", \"ai-agent-guidance\"], \"version\": \"1.1\"}", "declared_source_license": "MIT", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "{\"name\": \"Double-FW, Gareth Ford Williams\"}", "source_document_intro": "---\ntitle: \"Agent Instructions for Accessible Typography and Brand Communication\"\nversion: \"1.1\"\nauthor:\n name: \"Double-FW, Gareth Ford Williams\"\ndate: \"2026-11-06\"\nlicense: \"MIT\"\nlanguage: \"en\"\nrepository: \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\"\nartifact_type: \"knowledge-base/agent-guidance\"\nuse_case:\n - \"brand-design\"\n - \"communications-design\"\n - \"marketing-design\"\n - \"publishing-design\"\n - \"editorial-design\"\n - \"typography-evaluation\"\n - \"ai-agent-guidance\"\npurpose: \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["AGENTS.md", "README.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "AGENTS.md::agents-md-4-required-operating-behaviour", "title": "4. Required operating behaviour", "text": "## 4. Required operating behaviour\n\nAgents working in this repository MUST:\n\n- write in plain, direct language;\n- distinguish between evidence, assumptions, and conclusions;\n- state the audience, task, language or script, and reading context before making a substantive typography recommendation;\n- separate emotional accessibility, functional accessibility, and technical accessibility;\n- cite the repository’s material and avoid presenting unverified claims as settled fact;\n- identify unresolved risks, unknowns, and missing evidence; and\n- require human review for brand-critical or consequential recommendations when evidence is incomplete or the stakes are high.\n\nAgents MUST NOT:\n\n- claim that a single typeface or style is universally accessible;\n- present serif or sans serif as a universal rule;\n- treat preference as equivalent to accessibility;\n- infer disability or reading condition from a person’s font choice or preference;\n- recommend decorative display type for body text or important instructions;\n- ignore language, script, glyph coverage, fallback behaviour, or shaping requirements;\n- claim validation, approval, or compliance without evidence in the repository or a clearly identified source;\n- invent repository capabilities, infrastructure, security controls, or operational services.\n\n", "record_type": "agent_guidance_with_file_level_mit", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "AGENTS.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/AGENTS.md", "source_start_line": 61, "source_end_line": 83, "source_document_sha256": "69cd216f67c0ed7060ab381137f9305605b2a8c6fe9b7a89ea6d06770e9989d8", "text_sha256": "67626e63b58ec31a6c72f47a5fc6fcf37527141fe7b2b2bab3d5616336eb5706", "heading_path": ["AGENTS.md", "4. Required operating behaviour"], "metadata_json": "{\"artifact_type\": \"knowledge-base/agent-guidance\", \"author\": {\"name\": \"Double-FW, Gareth Ford Williams\"}, \"date\": \"2026-11-06\", \"language\": \"en\", \"license\": \"MIT\", \"purpose\": \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\", \"repository\": \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\", \"title\": \"Agent Instructions for Accessible Typography and Brand Communication\", \"use_case\": [\"brand-design\", \"communications-design\", \"marketing-design\", \"publishing-design\", \"editorial-design\", \"typography-evaluation\", \"ai-agent-guidance\"], \"version\": \"1.1\"}", "declared_source_license": "MIT", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "{\"name\": \"Double-FW, Gareth Ford Williams\"}", "source_document_intro": "---\ntitle: \"Agent Instructions for Accessible Typography and Brand Communication\"\nversion: \"1.1\"\nauthor:\n name: \"Double-FW, Gareth Ford Williams\"\ndate: \"2026-11-06\"\nlicense: \"MIT\"\nlanguage: \"en\"\nrepository: \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\"\nartifact_type: \"knowledge-base/agent-guidance\"\nuse_case:\n - \"brand-design\"\n - \"communications-design\"\n - \"marketing-design\"\n - \"publishing-design\"\n - \"editorial-design\"\n - \"typography-evaluation\"\n - \"ai-agent-guidance\"\npurpose: \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["AGENTS.md", "README.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "AGENTS.md::agents-md-5-evidence-standard", "title": "5. Evidence standard", "text": "## 5. Evidence standard\n\nTypography guidance in this repository should be interpreted as a system-level decision, not as a fixed aesthetic preference.\n\nBefore making or approving a recommendation, agents should establish:\n\n- who the audience is;\n- what task the text supports;\n- which language and script are in scope;\n- where the text will be read and under what conditions;\n- whether the concern is emotional, functional, or technical accessibility; and\n- what evidence supports the recommendation.\n\nIf the evidence is weak, incomplete, or missing, the recommendation must be labelled provisional or incomplete. Do not silently convert uncertainty into certainty.\n\n", "record_type": "agent_guidance_with_file_level_mit", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "AGENTS.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/AGENTS.md", "source_start_line": 84, "source_end_line": 98, "source_document_sha256": "69cd216f67c0ed7060ab381137f9305605b2a8c6fe9b7a89ea6d06770e9989d8", "text_sha256": "f0d08fb6bf97f717b7b15f11af5e9da20472ed32301658337bf7739b633ed98f", "heading_path": ["AGENTS.md", "5. Evidence standard"], "metadata_json": "{\"artifact_type\": \"knowledge-base/agent-guidance\", \"author\": {\"name\": \"Double-FW, Gareth Ford Williams\"}, \"date\": \"2026-11-06\", \"language\": \"en\", \"license\": \"MIT\", \"purpose\": \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\", \"repository\": \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\", \"title\": \"Agent Instructions for Accessible Typography and Brand Communication\", \"use_case\": [\"brand-design\", \"communications-design\", \"marketing-design\", \"publishing-design\", \"editorial-design\", \"typography-evaluation\", \"ai-agent-guidance\"], \"version\": \"1.1\"}", "declared_source_license": "MIT", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "{\"name\": \"Double-FW, Gareth Ford Williams\"}", "source_document_intro": "---\ntitle: \"Agent Instructions for Accessible Typography and Brand Communication\"\nversion: \"1.1\"\nauthor:\n name: \"Double-FW, Gareth Ford Williams\"\ndate: \"2026-11-06\"\nlicense: \"MIT\"\nlanguage: \"en\"\nrepository: \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\"\nartifact_type: \"knowledge-base/agent-guidance\"\nuse_case:\n - \"brand-design\"\n - \"communications-design\"\n - \"marketing-design\"\n - \"publishing-design\"\n - \"editorial-design\"\n - \"typography-evaluation\"\n - \"ai-agent-guidance\"\npurpose: \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["AGENTS.md", "README.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "AGENTS.md::agents-md-6-decision-framework", "title": "6. Decision framework", "text": "## 6. Decision framework\n\nUse this checklist when producing or reviewing guidance:\n\n1. Audience and task\n2. Language and script requirements\n3. Reading context and device conditions\n4. Emotional, functional, and technical considerations\n5. Recommended type treatment or typeface choice\n6. Evidence and testing status\n7. Risks, unresolved questions, and human review needs\n\nFor high-impact or brand-defining typography decisions, the agent should ask for human review when evidence is limited or when the recommendation has a meaningful impact on trust, comprehension, or accessibility.\n\n", "record_type": "agent_guidance_with_file_level_mit", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "AGENTS.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/AGENTS.md", "source_start_line": 99, "source_end_line": 112, "source_document_sha256": "69cd216f67c0ed7060ab381137f9305605b2a8c6fe9b7a89ea6d06770e9989d8", "text_sha256": "28d81a2b5284c8812f15c83fa63a3af30d5b522e08dc67f1252daba4fca84fa0", "heading_path": ["AGENTS.md", "6. Decision framework"], "metadata_json": "{\"artifact_type\": \"knowledge-base/agent-guidance\", \"author\": {\"name\": \"Double-FW, Gareth Ford Williams\"}, \"date\": \"2026-11-06\", \"language\": \"en\", \"license\": \"MIT\", \"purpose\": \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\", \"repository\": \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\", \"title\": \"Agent Instructions for Accessible Typography and Brand Communication\", \"use_case\": [\"brand-design\", \"communications-design\", \"marketing-design\", \"publishing-design\", \"editorial-design\", \"typography-evaluation\", \"ai-agent-guidance\"], \"version\": \"1.1\"}", "declared_source_license": "MIT", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "{\"name\": \"Double-FW, Gareth Ford Williams\"}", "source_document_intro": "---\ntitle: \"Agent Instructions for Accessible Typography and Brand Communication\"\nversion: \"1.1\"\nauthor:\n name: \"Double-FW, Gareth Ford Williams\"\ndate: \"2026-11-06\"\nlicense: \"MIT\"\nlanguage: \"en\"\nrepository: \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\"\nartifact_type: \"knowledge-base/agent-guidance\"\nuse_case:\n - \"brand-design\"\n - \"communications-design\"\n - \"marketing-design\"\n - \"publishing-design\"\n - \"editorial-design\"\n - \"typography-evaluation\"\n - \"ai-agent-guidance\"\npurpose: \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["AGENTS.md", "README.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "AGENTS.md::agents-md-7-human-review-and-escalation", "title": "7. Human review and escalation", "text": "## 7. Human review and escalation\n\nHumans remain the decision owner for consequential or reputational judgments. The agent SHOULD escalate when:\n\n- a recommendation affects brand trust or external communication;\n- the language, script, or audience is under-specified;\n- the content is high-risk, unclear, or safety-relevant;\n- evidence is missing or conflicting; or\n- a claim could be interpreted as a guarantee of accessibility or compliance.\n\nThe agent MUST clearly state what is known, what is uncertain, and what decision remains with a human reviewer.\n\n", "record_type": "agent_guidance_with_file_level_mit", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "AGENTS.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/AGENTS.md", "source_start_line": 113, "source_end_line": 124, "source_document_sha256": "69cd216f67c0ed7060ab381137f9305605b2a8c6fe9b7a89ea6d06770e9989d8", "text_sha256": "7071898826b63344c205a4c57d4bbef755899db6c8be55713b71153d90eec50f", "heading_path": ["AGENTS.md", "7. Human review and escalation"], "metadata_json": "{\"artifact_type\": \"knowledge-base/agent-guidance\", \"author\": {\"name\": \"Double-FW, Gareth Ford Williams\"}, \"date\": \"2026-11-06\", \"language\": \"en\", \"license\": \"MIT\", \"purpose\": \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\", \"repository\": \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\", \"title\": \"Agent Instructions for Accessible Typography and Brand Communication\", \"use_case\": [\"brand-design\", \"communications-design\", \"marketing-design\", \"publishing-design\", \"editorial-design\", \"typography-evaluation\", \"ai-agent-guidance\"], \"version\": \"1.1\"}", "declared_source_license": "MIT", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "{\"name\": \"Double-FW, Gareth Ford Williams\"}", "source_document_intro": "---\ntitle: \"Agent Instructions for Accessible Typography and Brand Communication\"\nversion: \"1.1\"\nauthor:\n name: \"Double-FW, Gareth Ford Williams\"\ndate: \"2026-11-06\"\nlicense: \"MIT\"\nlanguage: \"en\"\nrepository: \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\"\nartifact_type: \"knowledge-base/agent-guidance\"\nuse_case:\n - \"brand-design\"\n - \"communications-design\"\n - \"marketing-design\"\n - \"publishing-design\"\n - \"editorial-design\"\n - \"typography-evaluation\"\n - \"ai-agent-guidance\"\npurpose: \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["AGENTS.md", "README.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "AGENTS.md::agents-md-8-output-expectations", "title": "8. Output expectations", "text": "## 8. Output expectations\n\nWhen responding in this repository, prefer a structure such as:\n\n- Audience and task\n- Language and script requirements\n- Context and constraints\n- Recommendation\n- Evidence status\n- Risks and unresolved questions\n- Human review trigger, if any\n\nResponses should be explicit about uncertainty and should not imply that a recommendation is final when it is only provisional.\n\n", "record_type": "agent_guidance_with_file_level_mit", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "AGENTS.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/AGENTS.md", "source_start_line": 125, "source_end_line": 138, "source_document_sha256": "69cd216f67c0ed7060ab381137f9305605b2a8c6fe9b7a89ea6d06770e9989d8", "text_sha256": "009fc75e691eeded7d946d98dac82850fb01249cdcdf67800e30bd0d56da05ad", "heading_path": ["AGENTS.md", "8. Output expectations"], "metadata_json": "{\"artifact_type\": \"knowledge-base/agent-guidance\", \"author\": {\"name\": \"Double-FW, Gareth Ford Williams\"}, \"date\": \"2026-11-06\", \"language\": \"en\", \"license\": \"MIT\", \"purpose\": \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\", \"repository\": \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\", \"title\": \"Agent Instructions for Accessible Typography and Brand Communication\", \"use_case\": [\"brand-design\", \"communications-design\", \"marketing-design\", \"publishing-design\", \"editorial-design\", \"typography-evaluation\", \"ai-agent-guidance\"], \"version\": \"1.1\"}", "declared_source_license": "MIT", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "{\"name\": \"Double-FW, Gareth Ford Williams\"}", "source_document_intro": "---\ntitle: \"Agent Instructions for Accessible Typography and Brand Communication\"\nversion: \"1.1\"\nauthor:\n name: \"Double-FW, Gareth Ford Williams\"\ndate: \"2026-11-06\"\nlicense: \"MIT\"\nlanguage: \"en\"\nrepository: \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\"\nartifact_type: \"knowledge-base/agent-guidance\"\nuse_case:\n - \"brand-design\"\n - \"communications-design\"\n - \"marketing-design\"\n - \"publishing-design\"\n - \"editorial-design\"\n - \"typography-evaluation\"\n - \"ai-agent-guidance\"\npurpose: \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["AGENTS.md", "README.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "AGENTS.md::agents-md-9-repository-fit-and-maintenance", "title": "9. Repository fit and maintenance", "text": "## 9. Repository fit and maintenance\n\nThis file is intended to be concise, readable, and easy to update. Keep it aligned with actual repository contents and avoid referencing nonexistent systems, tooling, or governance processes.\n\nThe project is a knowledge-base repository, not a production application. This means the guidance is strongest when it is practical, evidence-aware, and explicit about its limits.\n\n", "record_type": "agent_guidance_with_file_level_mit", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "AGENTS.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/AGENTS.md", "source_start_line": 139, "source_end_line": 144, "source_document_sha256": "69cd216f67c0ed7060ab381137f9305605b2a8c6fe9b7a89ea6d06770e9989d8", "text_sha256": "fbb3a3c8a5014638e12543af4845de352d9c1e8b5dd47974cb62e014ea9049ec", "heading_path": ["AGENTS.md", "9. Repository fit and maintenance"], "metadata_json": "{\"artifact_type\": \"knowledge-base/agent-guidance\", \"author\": {\"name\": \"Double-FW, Gareth Ford Williams\"}, \"date\": \"2026-11-06\", \"language\": \"en\", \"license\": \"MIT\", \"purpose\": \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\", \"repository\": \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\", \"title\": \"Agent Instructions for Accessible Typography and Brand Communication\", \"use_case\": [\"brand-design\", \"communications-design\", \"marketing-design\", \"publishing-design\", \"editorial-design\", \"typography-evaluation\", \"ai-agent-guidance\"], \"version\": \"1.1\"}", "declared_source_license": "MIT", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "{\"name\": \"Double-FW, Gareth Ford Williams\"}", "source_document_intro": "---\ntitle: \"Agent Instructions for Accessible Typography and Brand Communication\"\nversion: \"1.1\"\nauthor:\n name: \"Double-FW, Gareth Ford Williams\"\ndate: \"2026-11-06\"\nlicense: \"MIT\"\nlanguage: \"en\"\nrepository: \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\"\nartifact_type: \"knowledge-base/agent-guidance\"\nuse_case:\n - \"brand-design\"\n - \"communications-design\"\n - \"marketing-design\"\n - \"publishing-design\"\n - \"editorial-design\"\n - \"typography-evaluation\"\n - \"ai-agent-guidance\"\npurpose: \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["AGENTS.md", "README.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "AGENTS.md::agents-md-10-short-version", "title": "10. Short version", "text": "## 10. Short version\n\nA well-scoped AI agent in this repository should:\n\n- work inside the repository’s purpose;\n- prefer evidence over style preference;\n- define context before recommending type;\n- separate facts from assumptions;\n- keep uncertainty visible;\n- avoid unsupported guarantees; and\n- route consequential decisions to a human reviewer.\n\nThis is the operational core of the repository guidance.\n", "record_type": "agent_guidance_with_file_level_mit", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "AGENTS.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/AGENTS.md", "source_start_line": 145, "source_end_line": 157, "source_document_sha256": "69cd216f67c0ed7060ab381137f9305605b2a8c6fe9b7a89ea6d06770e9989d8", "text_sha256": "ac79f171d3c68f1638c52868160034f304dafb35c7cc5a9b5070f7b5e002fc56", "heading_path": ["AGENTS.md", "10. Short version"], "metadata_json": "{\"artifact_type\": \"knowledge-base/agent-guidance\", \"author\": {\"name\": \"Double-FW, Gareth Ford Williams\"}, \"date\": \"2026-11-06\", \"language\": \"en\", \"license\": \"MIT\", \"purpose\": \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\", \"repository\": \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\", \"title\": \"Agent Instructions for Accessible Typography and Brand Communication\", \"use_case\": [\"brand-design\", \"communications-design\", \"marketing-design\", \"publishing-design\", \"editorial-design\", \"typography-evaluation\", \"ai-agent-guidance\"], \"version\": \"1.1\"}", "declared_source_license": "MIT", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "{\"name\": \"Double-FW, Gareth Ford Williams\"}", "source_document_intro": "---\ntitle: \"Agent Instructions for Accessible Typography and Brand Communication\"\nversion: \"1.1\"\nauthor:\n name: \"Double-FW, Gareth Ford Williams\"\ndate: \"2026-11-06\"\nlicense: \"MIT\"\nlanguage: \"en\"\nrepository: \"github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems\"\nartifact_type: \"knowledge-base/agent-guidance\"\nuse_case:\n - \"brand-design\"\n - \"communications-design\"\n - \"marketing-design\"\n - \"publishing-design\"\n - \"editorial-design\"\n - \"typography-evaluation\"\n - \"ai-agent-guidance\"\npurpose: \"Repository-local guidance for AI agents and contributors working on accessible typography content in this repository.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["AGENTS.md", "README.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "Accessible_Typography_for_UX_and_Brand_Systems.md::document-preamble", "title": "Document preamble", "text": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "record_type": "practitioner_editorial_typography_synthesis", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "Accessible_Typography_for_UX_and_Brand_Systems.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/Accessible_Typography_for_UX_and_Brand_Systems.md", "source_start_line": 1, "source_end_line": 81, "source_document_sha256": "2a50e1f3f4eafd02687b0e225e9ef2d170a63c82d30ecbe0d2d0d82b9c864664", "text_sha256": "e4008f19395e25ed2b07e502f50c37fb746685e4e64fce9de0563bd8582348d6", "heading_path": [], "metadata_json": "{\"ai_ingestion_guidance\": [\"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\", \"Do not use a typeface category, named font or single design feature as proof of accessibility.\", \"Do not state that serif or sans serif typefaces are universally more accessible.\", \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\", \"Do not infer a disability or reading condition from a person's font or display preferences.\", \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\", \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\", \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\", \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\", \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"], \"audiences\": [\"brand_designers\", \"type_designers\", \"ux_designers\", \"content_designers\", \"design_system_teams\", \"accessibility_professionals\", \"user_researchers\", \"developers\", \"ai_governance_systems\"], \"authors\": [\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"], \"content_status\": \"source_based_synthesis_with_editorial_normalisation\", \"contributing_organisation\": \"The Readability Group\", \"date_processed\": \"2026-09-18\", \"document_type\": [\"practitioner_article\", \"inclusive_typography_guidance\", \"ux_governance_reference\", \"brand_governance_reference\"], \"editorial_treatment\": [\"Combined related writings into a single article with one argument and consistent terminology.\", \"Removed repetition while preserving distinct principles, examples and qualifications.\", \"Separated typeface design, typographic application, technical delivery and brand expression.\", \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\", \"Added governance, testing and AI-use sections derived from the supplied principles.\", \"Preserved links and consolidated attribution in the source list.\"], \"jurisdictional_context\": [\"international\"], \"key_concepts\": [\"emotional_accessibility\", \"functional_accessibility\", \"technical_accessibility\", \"legibility\", \"readability\", \"letterform_ambiguity\", \"visual_crowding\", \"typeface_selection\", \"typographic_context\", \"language_and_script_support\", \"brand_expression\", \"comparative_user_testing\"], \"language\": \"en-GB\", \"primary_domains\": [\"typography\", \"digital_accessibility\", \"inclusive_design\", \"brand_design\", \"user_experience\", \"multilingual_design\"], \"short_title\": \"Accessible Typography\", \"source_basis\": {\"permitted_external_context\": \"Only sources linked from the supplied file were used to clarify authorship and context.\", \"supplied_file\": \"The Readability Group.docx\"}, \"source_characteristics\": {\"combines_multiple_articles\": true, \"contains_brand_commentary\": true, \"contains_neuroscience_explanation\": true, \"contains_practitioner_guidance\": true, \"contains_research_claims\": true, \"independently_peer_reviewed_as_a_collection\": false, \"normative_standard\": false}, \"title\": \"Accessible Typography for UX and Brand Systems\", \"version\": \"1.0-semantic\"}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "source_based_synthesis_with_editorial_normalisation", "applicable_source_license": "MIT", "source_attribution_json": "[\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"]", "source_document_intro": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Accessible_Typography_for_UX_and_Brand_Systems.md", "AGENTS.md", "README.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "Accessible_Typography_for_UX_and_Brand_Systems.md::accessible-typography-for-ux-and-brand-systems", "title": "Accessible Typography for UX and Brand Systems", "text": "# Accessible Typography for UX and Brand Systems\n\n", "record_type": "practitioner_editorial_typography_synthesis", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "Accessible_Typography_for_UX_and_Brand_Systems.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/Accessible_Typography_for_UX_and_Brand_Systems.md", "source_start_line": 82, "source_end_line": 83, "source_document_sha256": "2a50e1f3f4eafd02687b0e225e9ef2d170a63c82d30ecbe0d2d0d82b9c864664", "text_sha256": "887140f6ed39cbb6cbfdc75023b3fb5195de4dc277a876852387c198f510954d", "heading_path": ["Accessible Typography for UX and Brand Systems"], "metadata_json": "{\"ai_ingestion_guidance\": [\"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\", \"Do not use a typeface category, named font or single design feature as proof of accessibility.\", \"Do not state that serif or sans serif typefaces are universally more accessible.\", \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\", \"Do not infer a disability or reading condition from a person's font or display preferences.\", \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\", \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\", \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\", \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\", \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"], \"audiences\": [\"brand_designers\", \"type_designers\", \"ux_designers\", \"content_designers\", \"design_system_teams\", \"accessibility_professionals\", \"user_researchers\", \"developers\", \"ai_governance_systems\"], \"authors\": [\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"], \"content_status\": \"source_based_synthesis_with_editorial_normalisation\", \"contributing_organisation\": \"The Readability Group\", \"date_processed\": \"2026-09-18\", \"document_type\": [\"practitioner_article\", \"inclusive_typography_guidance\", \"ux_governance_reference\", \"brand_governance_reference\"], \"editorial_treatment\": [\"Combined related writings into a single article with one argument and consistent terminology.\", \"Removed repetition while preserving distinct principles, examples and qualifications.\", \"Separated typeface design, typographic application, technical delivery and brand expression.\", \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\", \"Added governance, testing and AI-use sections derived from the supplied principles.\", \"Preserved links and consolidated attribution in the source list.\"], \"jurisdictional_context\": [\"international\"], \"key_concepts\": [\"emotional_accessibility\", \"functional_accessibility\", \"technical_accessibility\", \"legibility\", \"readability\", \"letterform_ambiguity\", \"visual_crowding\", \"typeface_selection\", \"typographic_context\", \"language_and_script_support\", \"brand_expression\", \"comparative_user_testing\"], \"language\": \"en-GB\", \"primary_domains\": [\"typography\", \"digital_accessibility\", \"inclusive_design\", \"brand_design\", \"user_experience\", \"multilingual_design\"], \"short_title\": \"Accessible Typography\", \"source_basis\": {\"permitted_external_context\": \"Only sources linked from the supplied file were used to clarify authorship and context.\", \"supplied_file\": \"The Readability Group.docx\"}, \"source_characteristics\": {\"combines_multiple_articles\": true, \"contains_brand_commentary\": true, \"contains_neuroscience_explanation\": true, \"contains_practitioner_guidance\": true, \"contains_research_claims\": true, \"independently_peer_reviewed_as_a_collection\": false, \"normative_standard\": false}, \"title\": \"Accessible Typography for UX and Brand Systems\", \"version\": \"1.0-semantic\"}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "source_based_synthesis_with_editorial_normalisation", "applicable_source_license": "MIT", "source_attribution_json": "[\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"]", "source_document_intro": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Accessible_Typography_for_UX_and_Brand_Systems.md", "AGENTS.md", "README.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "Accessible_Typography_for_UX_and_Brand_Systems.md::accessible-typography-for-ux-and-brand-systems-article-overview", "title": "Article overview", "text": "## Article overview\n\nTypography carries language, but it also carries identity. People must be able to recognise the characters, follow the text and understand the message. They must also feel that the communication belongs to the organisation, product or service presenting it.\n\nThese requirements are often separated. Accessibility guidance may focus on technical settings such as contrast, resizing and spacing. Brand guidance may focus on personality, distinction and visual tone. Typeface selection may be treated as a matter of taste or reduced to a rule about serif and sans serif forms. None of these approaches is sufficient by itself.\n\nThe Readability Group describes accessible typography through three connected forms of accessibility:\n\n1. **Emotional accessibility** asks whether the typography invites the intended audience to engage and conveys the intended character.\n2. **Functional accessibility** asks whether people can identify, read and understand the text successfully.\n3. **Technical accessibility** asks whether the font and delivery system preserve that experience across languages, devices, settings and assistive technologies.\n\nAn effective type system must address all three. Technical conformance cannot repair an illegible typeface. High legibility cannot compensate for missing glyphs or broken script shaping. A functionally strong typeface can still weaken a brand if it communicates the wrong tone. The purpose of governance is to manage these relationships through evidence rather than assumptions.\n\n", "record_type": "practitioner_editorial_typography_synthesis", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "Accessible_Typography_for_UX_and_Brand_Systems.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/Accessible_Typography_for_UX_and_Brand_Systems.md", "source_start_line": 84, "source_end_line": 97, "source_document_sha256": "2a50e1f3f4eafd02687b0e225e9ef2d170a63c82d30ecbe0d2d0d82b9c864664", "text_sha256": "60fdf643eabfe7d2a6b03d362c4f9900b80fb50f6debdc9b7cd380e250076dbd", "heading_path": ["Accessible Typography for UX and Brand Systems", "Article overview"], "metadata_json": "{\"ai_ingestion_guidance\": [\"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\", \"Do not use a typeface category, named font or single design feature as proof of accessibility.\", \"Do not state that serif or sans serif typefaces are universally more accessible.\", \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\", \"Do not infer a disability or reading condition from a person's font or display preferences.\", \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\", \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\", \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\", \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\", \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"], \"audiences\": [\"brand_designers\", \"type_designers\", \"ux_designers\", \"content_designers\", \"design_system_teams\", \"accessibility_professionals\", \"user_researchers\", \"developers\", \"ai_governance_systems\"], \"authors\": [\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"], \"content_status\": \"source_based_synthesis_with_editorial_normalisation\", \"contributing_organisation\": \"The Readability Group\", \"date_processed\": \"2026-09-18\", \"document_type\": [\"practitioner_article\", \"inclusive_typography_guidance\", \"ux_governance_reference\", \"brand_governance_reference\"], \"editorial_treatment\": [\"Combined related writings into a single article with one argument and consistent terminology.\", \"Removed repetition while preserving distinct principles, examples and qualifications.\", \"Separated typeface design, typographic application, technical delivery and brand expression.\", \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\", \"Added governance, testing and AI-use sections derived from the supplied principles.\", \"Preserved links and consolidated attribution in the source list.\"], \"jurisdictional_context\": [\"international\"], \"key_concepts\": [\"emotional_accessibility\", \"functional_accessibility\", \"technical_accessibility\", \"legibility\", \"readability\", \"letterform_ambiguity\", \"visual_crowding\", \"typeface_selection\", \"typographic_context\", \"language_and_script_support\", \"brand_expression\", \"comparative_user_testing\"], \"language\": \"en-GB\", \"primary_domains\": [\"typography\", \"digital_accessibility\", \"inclusive_design\", \"brand_design\", \"user_experience\", \"multilingual_design\"], \"short_title\": \"Accessible Typography\", \"source_basis\": {\"permitted_external_context\": \"Only sources linked from the supplied file were used to clarify authorship and context.\", \"supplied_file\": \"The Readability Group.docx\"}, \"source_characteristics\": {\"combines_multiple_articles\": true, \"contains_brand_commentary\": true, \"contains_neuroscience_explanation\": true, \"contains_practitioner_guidance\": true, \"contains_research_claims\": true, \"independently_peer_reviewed_as_a_collection\": false, \"normative_standard\": false}, \"title\": \"Accessible Typography for UX and Brand Systems\", \"version\": \"1.0-semantic\"}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "source_based_synthesis_with_editorial_normalisation", "applicable_source_license": "MIT", "source_attribution_json": "[\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"]", "source_document_intro": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Accessible_Typography_for_UX_and_Brand_Systems.md", "AGENTS.md", "README.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "Accessible_Typography_for_UX_and_Brand_Systems.md::accessible-typography-for-ux-and-brand-systems-contents", "title": "Contents", "text": "## Contents\n\n1. The three parts of accessible typography\n2. Legibility and readability\n3. How visual reading informs design\n4. Choosing and evaluating a typeface\n5. Brand expression and emotional accessibility\n6. Language, script and technical delivery\n7. Testing typography in context\n8. Governance for UX, brand and AI systems\n9. Sources and attribution\n\n", "record_type": "practitioner_editorial_typography_synthesis", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "Accessible_Typography_for_UX_and_Brand_Systems.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/Accessible_Typography_for_UX_and_Brand_Systems.md", "source_start_line": 98, "source_end_line": 109, "source_document_sha256": "2a50e1f3f4eafd02687b0e225e9ef2d170a63c82d30ecbe0d2d0d82b9c864664", "text_sha256": "1d8af9bfd54d969f697b3ec8f10a323ba44405275f1d30ee0a77defdf42cc652", "heading_path": ["Accessible Typography for UX and Brand Systems", "Contents"], "metadata_json": "{\"ai_ingestion_guidance\": [\"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\", \"Do not use a typeface category, named font or single design feature as proof of accessibility.\", \"Do not state that serif or sans serif typefaces are universally more accessible.\", \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\", \"Do not infer a disability or reading condition from a person's font or display preferences.\", \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\", \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\", \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\", \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\", \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"], \"audiences\": [\"brand_designers\", \"type_designers\", \"ux_designers\", \"content_designers\", \"design_system_teams\", \"accessibility_professionals\", \"user_researchers\", \"developers\", \"ai_governance_systems\"], \"authors\": [\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"], \"content_status\": \"source_based_synthesis_with_editorial_normalisation\", \"contributing_organisation\": \"The Readability Group\", \"date_processed\": \"2026-09-18\", \"document_type\": [\"practitioner_article\", \"inclusive_typography_guidance\", \"ux_governance_reference\", \"brand_governance_reference\"], \"editorial_treatment\": [\"Combined related writings into a single article with one argument and consistent terminology.\", \"Removed repetition while preserving distinct principles, examples and qualifications.\", \"Separated typeface design, typographic application, technical delivery and brand expression.\", \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\", \"Added governance, testing and AI-use sections derived from the supplied principles.\", \"Preserved links and consolidated attribution in the source list.\"], \"jurisdictional_context\": [\"international\"], \"key_concepts\": [\"emotional_accessibility\", \"functional_accessibility\", \"technical_accessibility\", \"legibility\", \"readability\", \"letterform_ambiguity\", \"visual_crowding\", \"typeface_selection\", \"typographic_context\", \"language_and_script_support\", \"brand_expression\", \"comparative_user_testing\"], \"language\": \"en-GB\", \"primary_domains\": [\"typography\", \"digital_accessibility\", \"inclusive_design\", \"brand_design\", \"user_experience\", \"multilingual_design\"], \"short_title\": \"Accessible Typography\", \"source_basis\": {\"permitted_external_context\": \"Only sources linked from the supplied file were used to clarify authorship and context.\", \"supplied_file\": \"The Readability Group.docx\"}, \"source_characteristics\": {\"combines_multiple_articles\": true, \"contains_brand_commentary\": true, \"contains_neuroscience_explanation\": true, \"contains_practitioner_guidance\": true, \"contains_research_claims\": true, \"independently_peer_reviewed_as_a_collection\": false, \"normative_standard\": false}, \"title\": \"Accessible Typography for UX and Brand Systems\", \"version\": \"1.0-semantic\"}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "source_based_synthesis_with_editorial_normalisation", "applicable_source_license": "MIT", "source_attribution_json": "[\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"]", "source_document_intro": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Accessible_Typography_for_UX_and_Brand_Systems.md", "AGENTS.md", "README.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "Accessible_Typography_for_UX_and_Brand_Systems.md::accessible-typography-for-ux-and-brand-systems-1-the-three-parts-of-accessible-typography", "title": "1. The three parts of accessible typography", "text": "## 1. The three parts of accessible typography\n\n### Emotional accessibility\n\nTypography creates an impression before a person has consciously read the words. A typeface can appear formal, friendly, authoritative, fashionable, academic, neutral or unfamiliar. These associations vary between people, cultures and generations, but they influence whether the communication feels credible and relevant.\n\nThe source writings describe type as a visual tone of voice. This matters in branding because recognition and trust are part of the reading experience. A typeface that is technically strong but emotionally inappropriate may cause rejection or weaken the intended identity. Emotional accessibility is therefore not decoration added after functional decisions. It is a design outcome that must be evaluated with the intended audience.\n\nEmotional response must not be used to excuse a functional barrier. An expressive display face may be suitable for a short heading or logo but unsuitable for instructions, body copy or an error message. Brand systems need rules for where expressive typography may be used and where reading performance has priority.\n\n### Functional accessibility\n\nFunctional accessibility concerns what happens when someone reads. Can they identify the characters quickly and accurately? Can they move through a line and paragraph without unnecessary effort? Can they maintain comprehension? Does the typography continue to work when vision, literacy, language knowledge, attention or reading fluency differs from the assumptions of the design team?\n\nThe answer depends on the combined effect of the typeface and its application. Letterform ambiguity, closed apertures, small counters, tight spacing, weak weight and poor line spacing can each increase effort. The same typeface may perform differently at another size, weight, line length or display resolution.\n\n### Technical accessibility\n\nTechnical accessibility concerns the font file, rendering environment and implementation. A font must contain the characters and marks required by the supported languages. The shaping engine must display joining and contextual forms correctly. Text must resize, reflow and respond to user settings without loss of content or function.\n\nDifferent browsers, operating systems and displays can render the same font differently. Fallback fonts may change character widths, tone and readability. A system that works in a design file may fail when a missing glyph is replaced, an Arabic word is displayed as separate characters or a condensed table style is rendered on a small screen.\n\nTechnical testing is therefore necessary, but it cannot prove that the result is readable or emotionally appropriate. Those outcomes need human evaluation.\n\n", "record_type": "practitioner_editorial_typography_synthesis", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "Accessible_Typography_for_UX_and_Brand_Systems.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/Accessible_Typography_for_UX_and_Brand_Systems.md", "source_start_line": 110, "source_end_line": 133, "source_document_sha256": "2a50e1f3f4eafd02687b0e225e9ef2d170a63c82d30ecbe0d2d0d82b9c864664", "text_sha256": "ba7e22b5227b9509080f653ef7a4f872366b6e7ac9107af3fb174b550331bbe7", "heading_path": ["Accessible Typography for UX and Brand Systems", "1. The three parts of accessible typography"], "metadata_json": "{\"ai_ingestion_guidance\": [\"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\", \"Do not use a typeface category, named font or single design feature as proof of accessibility.\", \"Do not state that serif or sans serif typefaces are universally more accessible.\", \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\", \"Do not infer a disability or reading condition from a person's font or display preferences.\", \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\", \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\", \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\", \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\", \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"], \"audiences\": [\"brand_designers\", \"type_designers\", \"ux_designers\", \"content_designers\", \"design_system_teams\", \"accessibility_professionals\", \"user_researchers\", \"developers\", \"ai_governance_systems\"], \"authors\": [\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"], \"content_status\": \"source_based_synthesis_with_editorial_normalisation\", \"contributing_organisation\": \"The Readability Group\", \"date_processed\": \"2026-09-18\", \"document_type\": [\"practitioner_article\", \"inclusive_typography_guidance\", \"ux_governance_reference\", \"brand_governance_reference\"], \"editorial_treatment\": [\"Combined related writings into a single article with one argument and consistent terminology.\", \"Removed repetition while preserving distinct principles, examples and qualifications.\", \"Separated typeface design, typographic application, technical delivery and brand expression.\", \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\", \"Added governance, testing and AI-use sections derived from the supplied principles.\", \"Preserved links and consolidated attribution in the source list.\"], \"jurisdictional_context\": [\"international\"], \"key_concepts\": [\"emotional_accessibility\", \"functional_accessibility\", \"technical_accessibility\", \"legibility\", \"readability\", \"letterform_ambiguity\", \"visual_crowding\", \"typeface_selection\", \"typographic_context\", \"language_and_script_support\", \"brand_expression\", \"comparative_user_testing\"], \"language\": \"en-GB\", \"primary_domains\": [\"typography\", \"digital_accessibility\", \"inclusive_design\", \"brand_design\", \"user_experience\", \"multilingual_design\"], \"short_title\": \"Accessible Typography\", \"source_basis\": {\"permitted_external_context\": \"Only sources linked from the supplied file were used to clarify authorship and context.\", \"supplied_file\": \"The Readability Group.docx\"}, \"source_characteristics\": {\"combines_multiple_articles\": true, \"contains_brand_commentary\": true, \"contains_neuroscience_explanation\": true, \"contains_practitioner_guidance\": true, \"contains_research_claims\": true, \"independently_peer_reviewed_as_a_collection\": false, \"normative_standard\": false}, \"title\": \"Accessible Typography for UX and Brand Systems\", \"version\": \"1.0-semantic\"}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "source_based_synthesis_with_editorial_normalisation", "applicable_source_license": "MIT", "source_attribution_json": "[\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"]", "source_document_intro": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Accessible_Typography_for_UX_and_Brand_Systems.md", "AGENTS.md", "README.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "Accessible_Typography_for_UX_and_Brand_Systems.md::accessible-typography-for-ux-and-brand-systems-2-legibility-and-readability", "title": "2. Legibility and readability", "text": "## 2. Legibility and readability\n\nThe terms *legibility* and *readability* are often used as if they mean the same thing. The distinction is useful because they identify different sources of difficulty.\n\n### Legibility\n\nLegibility concerns how quickly and accurately a person can recognise a character or glyph. It is affected by the design of the letterform, its size, weight, contrast, surrounding space and the conditions in which it is seen.\n\nLegibility problems often appear when characters are too similar. Common test strings include:\n\n- uppercase `I`, lowercase `l` and the numeral `1`;\n- lowercase `o`, `c`, `e` and `a`;\n- mirrored or rotationally similar forms such as `b`, `d`, `p` and `q`; and\n- combinations such as `r n`, which tight spacing can make resemble `m`.\n\nOpen apertures and sufficiently large counters can help preserve the distinctive structure of characters. Clear differences between ascenders and capital height can provide additional recognition cues. Varied character widths may also help, which is one reason humanist typefaces can perform well at text sizes. These are useful indicators, not universal guarantees.\n\n### Readability\n\nReadability concerns how smoothly and efficiently a person can read connected text. Typeface choice contributes to readability, but spacing, line length, hierarchy and layout may have a greater effect on sustained reading.\n\nReading involves a sequence of fixations and rapid eye movements called saccades. If characters crowd together, lines are difficult to follow or the type creates an uneven visual pattern, the reader may need to refixate or move backwards. This adds effort and can interrupt comprehension.\n\nLegibility and readability can therefore diverge. A typeface may contain individually distinctive characters but become tiring in long paragraphs. Another may create a smooth text colour at normal reading size but lose character detail on a low-resolution screen. Both qualities must be assessed in the context in which the type will be used.\n\n### Comprehension and preference\n\nLegibility, readability, comprehension and preference are related but are not interchangeable measurements. A participant may prefer a familiar or expressive typeface without reading it faster. Another may read a candidate accurately but dislike its tone. A design decision should retain these differences rather than combining them into one accessibility score.\n\n", "record_type": "practitioner_editorial_typography_synthesis", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "Accessible_Typography_for_UX_and_Brand_Systems.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/Accessible_Typography_for_UX_and_Brand_Systems.md", "source_start_line": 134, "source_end_line": 162, "source_document_sha256": "2a50e1f3f4eafd02687b0e225e9ef2d170a63c82d30ecbe0d2d0d82b9c864664", "text_sha256": "efe5afe2e1921836e31bd44fb89a920c2467118fbb5a975242b6cd149e935959", "heading_path": ["Accessible Typography for UX and Brand Systems", "2. Legibility and readability"], "metadata_json": "{\"ai_ingestion_guidance\": [\"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\", \"Do not use a typeface category, named font or single design feature as proof of accessibility.\", \"Do not state that serif or sans serif typefaces are universally more accessible.\", \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\", \"Do not infer a disability or reading condition from a person's font or display preferences.\", \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\", \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\", \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\", \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\", \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"], \"audiences\": [\"brand_designers\", \"type_designers\", \"ux_designers\", \"content_designers\", \"design_system_teams\", \"accessibility_professionals\", \"user_researchers\", \"developers\", \"ai_governance_systems\"], \"authors\": [\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"], \"content_status\": \"source_based_synthesis_with_editorial_normalisation\", \"contributing_organisation\": \"The Readability Group\", \"date_processed\": \"2026-09-18\", \"document_type\": [\"practitioner_article\", \"inclusive_typography_guidance\", \"ux_governance_reference\", \"brand_governance_reference\"], \"editorial_treatment\": [\"Combined related writings into a single article with one argument and consistent terminology.\", \"Removed repetition while preserving distinct principles, examples and qualifications.\", \"Separated typeface design, typographic application, technical delivery and brand expression.\", \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\", \"Added governance, testing and AI-use sections derived from the supplied principles.\", \"Preserved links and consolidated attribution in the source list.\"], \"jurisdictional_context\": [\"international\"], \"key_concepts\": [\"emotional_accessibility\", \"functional_accessibility\", \"technical_accessibility\", \"legibility\", \"readability\", \"letterform_ambiguity\", \"visual_crowding\", \"typeface_selection\", \"typographic_context\", \"language_and_script_support\", \"brand_expression\", \"comparative_user_testing\"], \"language\": \"en-GB\", \"primary_domains\": [\"typography\", \"digital_accessibility\", \"inclusive_design\", \"brand_design\", \"user_experience\", \"multilingual_design\"], \"short_title\": \"Accessible Typography\", \"source_basis\": {\"permitted_external_context\": \"Only sources linked from the supplied file were used to clarify authorship and context.\", \"supplied_file\": \"The Readability Group.docx\"}, \"source_characteristics\": {\"combines_multiple_articles\": true, \"contains_brand_commentary\": true, \"contains_neuroscience_explanation\": true, \"contains_practitioner_guidance\": true, \"contains_research_claims\": true, \"independently_peer_reviewed_as_a_collection\": false, \"normative_standard\": false}, \"title\": \"Accessible Typography for UX and Brand Systems\", \"version\": \"1.0-semantic\"}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "source_based_synthesis_with_editorial_normalisation", "applicable_source_license": "MIT", "source_attribution_json": "[\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"]", "source_document_intro": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Accessible_Typography_for_UX_and_Brand_Systems.md", "AGENTS.md", "README.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "Accessible_Typography_for_UX_and_Brand_Systems.md::accessible-typography-for-ux-and-brand-systems-3-how-visual-reading-informs-design", "title": "3. How visual reading informs design", "text": "## 3. How visual reading informs design\n\nVisual reading begins with light reaching the retina and continues through neurological processes that identify shapes, organise language and attach meaning. Central vision, particularly the foveal region, provides the detailed information needed for reading. Eye movements place successive parts of a line within that detailed field.\n\nThe source material describes a typical fixation in Latin text as covering roughly seven to nine characters under particular reading conditions. This should not be treated as a fixed human limit. Typeface dimensions, size, reading distance, fluency, vision and writing system all affect what can be captured and processed.\n\nThe visual word form area is involved in recognising familiar letter and word patterns. From a design perspective, the important point is practical: the brain must distinguish the visual information before it can interpret the language. Ambiguous letterforms and visual crowding add work before comprehension begins.\n\nContext can also degrade otherwise strong typography. Glare, low resolution, movement, viewing distance, fatigue and display quality may reduce the information available to the reader. Head-mounted displays can add vergence and accommodation conflicts that cause strain for some people. Typography should therefore be tested in the least favourable realistic context, not only on a designer's calibrated monitor.\n\nReading is not exclusively visual. Braille is a writing system read through touch, and digital content may be accessed through speech or other transformations. A visually successful type system must sit within a content and interface system that also supports nonvisual access.\n\n", "record_type": "practitioner_editorial_typography_synthesis", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "Accessible_Typography_for_UX_and_Brand_Systems.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/Accessible_Typography_for_UX_and_Brand_Systems.md", "source_start_line": 163, "source_end_line": 174, "source_document_sha256": "2a50e1f3f4eafd02687b0e225e9ef2d170a63c82d30ecbe0d2d0d82b9c864664", "text_sha256": "9811c8f4ac2ceebca9dd16a3cb13b3e171cda53211a429313266e22dd5508cb0", "heading_path": ["Accessible Typography for UX and Brand Systems", "3. How visual reading informs design"], "metadata_json": "{\"ai_ingestion_guidance\": [\"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\", \"Do not use a typeface category, named font or single design feature as proof of accessibility.\", \"Do not state that serif or sans serif typefaces are universally more accessible.\", \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\", \"Do not infer a disability or reading condition from a person's font or display preferences.\", \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\", \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\", \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\", \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\", \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"], \"audiences\": [\"brand_designers\", \"type_designers\", \"ux_designers\", \"content_designers\", \"design_system_teams\", \"accessibility_professionals\", \"user_researchers\", \"developers\", \"ai_governance_systems\"], \"authors\": [\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"], \"content_status\": \"source_based_synthesis_with_editorial_normalisation\", \"contributing_organisation\": \"The Readability Group\", \"date_processed\": \"2026-09-18\", \"document_type\": [\"practitioner_article\", \"inclusive_typography_guidance\", \"ux_governance_reference\", \"brand_governance_reference\"], \"editorial_treatment\": [\"Combined related writings into a single article with one argument and consistent terminology.\", \"Removed repetition while preserving distinct principles, examples and qualifications.\", \"Separated typeface design, typographic application, technical delivery and brand expression.\", \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\", \"Added governance, testing and AI-use sections derived from the supplied principles.\", \"Preserved links and consolidated attribution in the source list.\"], \"jurisdictional_context\": [\"international\"], \"key_concepts\": [\"emotional_accessibility\", \"functional_accessibility\", \"technical_accessibility\", \"legibility\", \"readability\", \"letterform_ambiguity\", \"visual_crowding\", \"typeface_selection\", \"typographic_context\", \"language_and_script_support\", \"brand_expression\", \"comparative_user_testing\"], \"language\": \"en-GB\", \"primary_domains\": [\"typography\", \"digital_accessibility\", \"inclusive_design\", \"brand_design\", \"user_experience\", \"multilingual_design\"], \"short_title\": \"Accessible Typography\", \"source_basis\": {\"permitted_external_context\": \"Only sources linked from the supplied file were used to clarify authorship and context.\", \"supplied_file\": \"The Readability Group.docx\"}, \"source_characteristics\": {\"combines_multiple_articles\": true, \"contains_brand_commentary\": true, \"contains_neuroscience_explanation\": true, \"contains_practitioner_guidance\": true, \"contains_research_claims\": true, \"independently_peer_reviewed_as_a_collection\": false, \"normative_standard\": false}, \"title\": \"Accessible Typography for UX and Brand Systems\", \"version\": \"1.0-semantic\"}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "source_based_synthesis_with_editorial_normalisation", "applicable_source_license": "MIT", "source_attribution_json": "[\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"]", "source_document_intro": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Accessible_Typography_for_UX_and_Brand_Systems.md", "AGENTS.md", "README.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "Accessible_Typography_for_UX_and_Brand_Systems.md::accessible-typography-for-ux-and-brand-systems-4-choosing-and-evaluating-a-typeface", "title": "4. Choosing and evaluating a typeface", "text": "## 4. Choosing and evaluating a typeface\n\n### Start with the audience and task\n\nTypeface selection should begin with who needs to read, what they need to do and where reading will happen. A short brand mark, a long article, a safety instruction, a financial table and a children's learning product impose different demands.\n\nReading experience also matters. Emerging readers may rely more on recognising individual characters. Experienced readers make greater use of familiar word patterns and can move through text more fluently. A single-storey `a`, for example, may resemble forms first taught to some children, while a double-storey `a` may provide stronger differentiation for an experienced reader. Neither form is universally accessible.\n\n### Do not reduce the decision to serif or sans serif\n\nThe supplied writings suggest that simpler sans serif forms may support character recognition for some emerging readers, while serif forms may provide useful differentiation and flow for some experienced readers. The practical lesson is not that either category wins. Designs within each category vary greatly.\n\nSerifs may distinguish characters in one typeface and add noise in another. A geometric sans serif may contain repeated shapes that increase ambiguity, while a humanist sans serif may offer more variation. Category names should help teams form questions, not make the decision for them.\n\n### Audit character differentiation\n\nReview the complete character set at every intended size and weight. Do not rely on a specimen containing only attractive words. Test letters, numerals, punctuation, diacritics and combinations that expose ambiguity.\n\nThe audit should examine:\n\n- whether `I`, `l` and `1` remain distinct;\n- whether open forms such as `c` and `e` retain their apertures;\n- whether counters remain visible at small sizes and lower resolutions;\n- whether `b`, `d`, `p` and `q` have sufficient distinguishing detail;\n- whether ascenders rise clearly above capital height where the design permits;\n- whether adjacent characters merge or form misleading shapes; and\n- whether bold, italic, condensed and variable-font instances preserve recognition.\n\nMirrored letterforms should be considered carefully, but typography should not be presented as a treatment for dyslexia. Dyslexia is a developmental difference involving language processing, not simply a visual problem. People with dyslexia may also experience visual discomfort or other overlapping needs, but those experiences require separate investigation.\n\n### Evaluate spacing as part of the type system\n\nTight spacing can create visual crowding and merge otherwise legible forms. Adequate letter spacing helps people isolate characters, particularly at small sizes or with reduced vision. More spacing is not always better: excessive spacing can break familiar word patterns and reduce reading flow.\n\nSpacing must respond to size and use. Display typography can usually be set more tightly than body text because the characters are larger. Body text needs spacing that remains stable across browsers, zoom levels and fallback fonts. Designers should test the typeface's default spacing before adding global tracking that may damage carefully designed pairs.\n\n### Judge perceived size, not only the numeric size\n\nTwo typefaces set at the same CSS pixel or typographic point size can appear very different. A fixed minimum size cannot determine accessibility without considering the typeface's proportions, weight, display conditions and available user controls.\n\nSize guidance is still useful, but it should define a testable reading outcome and permit enlargement. A governance system should reject claims that a particular pixel value makes every typeface accessible.\n\n", "record_type": "practitioner_editorial_typography_synthesis", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "Accessible_Typography_for_UX_and_Brand_Systems.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/Accessible_Typography_for_UX_and_Brand_Systems.md", "source_start_line": 175, "source_end_line": 216, "source_document_sha256": "2a50e1f3f4eafd02687b0e225e9ef2d170a63c82d30ecbe0d2d0d82b9c864664", "text_sha256": "bfab8f80e263e2bfdb1dcf4e7e1db15f686e2bbe255f9c65250098b012f81616", "heading_path": ["Accessible Typography for UX and Brand Systems", "4. Choosing and evaluating a typeface"], "metadata_json": "{\"ai_ingestion_guidance\": [\"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\", \"Do not use a typeface category, named font or single design feature as proof of accessibility.\", \"Do not state that serif or sans serif typefaces are universally more accessible.\", \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\", \"Do not infer a disability or reading condition from a person's font or display preferences.\", \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\", \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\", \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\", \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\", \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"], \"audiences\": [\"brand_designers\", \"type_designers\", \"ux_designers\", \"content_designers\", \"design_system_teams\", \"accessibility_professionals\", \"user_researchers\", \"developers\", \"ai_governance_systems\"], \"authors\": [\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"], \"content_status\": \"source_based_synthesis_with_editorial_normalisation\", \"contributing_organisation\": \"The Readability Group\", \"date_processed\": \"2026-09-18\", \"document_type\": [\"practitioner_article\", \"inclusive_typography_guidance\", \"ux_governance_reference\", \"brand_governance_reference\"], \"editorial_treatment\": [\"Combined related writings into a single article with one argument and consistent terminology.\", \"Removed repetition while preserving distinct principles, examples and qualifications.\", \"Separated typeface design, typographic application, technical delivery and brand expression.\", \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\", \"Added governance, testing and AI-use sections derived from the supplied principles.\", \"Preserved links and consolidated attribution in the source list.\"], \"jurisdictional_context\": [\"international\"], \"key_concepts\": [\"emotional_accessibility\", \"functional_accessibility\", \"technical_accessibility\", \"legibility\", \"readability\", \"letterform_ambiguity\", \"visual_crowding\", \"typeface_selection\", \"typographic_context\", \"language_and_script_support\", \"brand_expression\", \"comparative_user_testing\"], \"language\": \"en-GB\", \"primary_domains\": [\"typography\", \"digital_accessibility\", \"inclusive_design\", \"brand_design\", \"user_experience\", \"multilingual_design\"], \"short_title\": \"Accessible Typography\", \"source_basis\": {\"permitted_external_context\": \"Only sources linked from the supplied file were used to clarify authorship and context.\", \"supplied_file\": \"The Readability Group.docx\"}, \"source_characteristics\": {\"combines_multiple_articles\": true, \"contains_brand_commentary\": true, \"contains_neuroscience_explanation\": true, \"contains_practitioner_guidance\": true, \"contains_research_claims\": true, \"independently_peer_reviewed_as_a_collection\": false, \"normative_standard\": false}, \"title\": \"Accessible Typography for UX and Brand Systems\", \"version\": \"1.0-semantic\"}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "source_based_synthesis_with_editorial_normalisation", "applicable_source_license": "MIT", "source_attribution_json": "[\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"]", "source_document_intro": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Accessible_Typography_for_UX_and_Brand_Systems.md", "AGENTS.md", "README.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "Accessible_Typography_for_UX_and_Brand_Systems.md::accessible-typography-for-ux-and-brand-systems-5-brand-expression-and-emotional-accessibility", "title": "5. Brand expression and emotional accessibility", "text": "## 5. Brand expression and emotional accessibility\n\nTypeface choice helps people recognise who is speaking. A brand can lose distinction when typography is selected only for apparent neutrality. It can also become exclusionary when visual personality depends on unfamiliar, decorative or tightly constructed forms that impede reading.\n\nThe source articles use Comic Sans, Burberry's 2018 logo and blackletter to illustrate this tension. Comic Sans can appear approachable or child-centred, but may undermine the intended tone of formal scientific communication. Burberry's simplified wordmark improved direct letter recognition while prompting debate about whether personality had been lost. Blackletter can convey heritage, authority, music culture or streetwear, yet its unfamiliar shapes can be difficult in sustained text.\n\nThese examples do not produce a rule about which style a brand should adopt. They show that emotional and functional effects need different evidence. An expressive style may be appropriate for a logo or campaign heading, paired with a more readable companion for body copy and interaction text.\n\nA brand typography system should therefore define:\n\n- the role of each typeface and style;\n- the minimum contexts in which expressive display type may appear;\n- the body and interface type used for sustained or consequential reading;\n- how hierarchy is preserved when users enlarge or restyle text;\n- approved fallbacks for each language and platform; and\n- when a local script requires a related design rather than a visual imitation of Latin forms.\n\nBrand integrity and accessibility are not opposing goals. Both are weakened when decisions are based on fashion, anecdote or a single technical measure.\n\n", "record_type": "practitioner_editorial_typography_synthesis", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "Accessible_Typography_for_UX_and_Brand_Systems.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/Accessible_Typography_for_UX_and_Brand_Systems.md", "source_start_line": 217, "source_end_line": 235, "source_document_sha256": "2a50e1f3f4eafd02687b0e225e9ef2d170a63c82d30ecbe0d2d0d82b9c864664", "text_sha256": "c4916e3adfe91f224c752e08b4b24f0be0030366c5214ca4850ab79753862355", "heading_path": ["Accessible Typography for UX and Brand Systems", "5. Brand expression and emotional accessibility"], "metadata_json": "{\"ai_ingestion_guidance\": [\"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\", \"Do not use a typeface category, named font or single design feature as proof of accessibility.\", \"Do not state that serif or sans serif typefaces are universally more accessible.\", \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\", \"Do not infer a disability or reading condition from a person's font or display preferences.\", \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\", \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\", \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\", \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\", \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"], \"audiences\": [\"brand_designers\", \"type_designers\", \"ux_designers\", \"content_designers\", \"design_system_teams\", \"accessibility_professionals\", \"user_researchers\", \"developers\", \"ai_governance_systems\"], \"authors\": [\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"], \"content_status\": \"source_based_synthesis_with_editorial_normalisation\", \"contributing_organisation\": \"The Readability Group\", \"date_processed\": \"2026-09-18\", \"document_type\": [\"practitioner_article\", \"inclusive_typography_guidance\", \"ux_governance_reference\", \"brand_governance_reference\"], \"editorial_treatment\": [\"Combined related writings into a single article with one argument and consistent terminology.\", \"Removed repetition while preserving distinct principles, examples and qualifications.\", \"Separated typeface design, typographic application, technical delivery and brand expression.\", \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\", \"Added governance, testing and AI-use sections derived from the supplied principles.\", \"Preserved links and consolidated attribution in the source list.\"], \"jurisdictional_context\": [\"international\"], \"key_concepts\": [\"emotional_accessibility\", \"functional_accessibility\", \"technical_accessibility\", \"legibility\", \"readability\", \"letterform_ambiguity\", \"visual_crowding\", \"typeface_selection\", \"typographic_context\", \"language_and_script_support\", \"brand_expression\", \"comparative_user_testing\"], \"language\": \"en-GB\", \"primary_domains\": [\"typography\", \"digital_accessibility\", \"inclusive_design\", \"brand_design\", \"user_experience\", \"multilingual_design\"], \"short_title\": \"Accessible Typography\", \"source_basis\": {\"permitted_external_context\": \"Only sources linked from the supplied file were used to clarify authorship and context.\", \"supplied_file\": \"The Readability Group.docx\"}, \"source_characteristics\": {\"combines_multiple_articles\": true, \"contains_brand_commentary\": true, \"contains_neuroscience_explanation\": true, \"contains_practitioner_guidance\": true, \"contains_research_claims\": true, \"independently_peer_reviewed_as_a_collection\": false, \"normative_standard\": false}, \"title\": \"Accessible Typography for UX and Brand Systems\", \"version\": \"1.0-semantic\"}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "source_based_synthesis_with_editorial_normalisation", "applicable_source_license": "MIT", "source_attribution_json": "[\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"]", "source_document_intro": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Accessible_Typography_for_UX_and_Brand_Systems.md", "AGENTS.md", "README.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "Accessible_Typography_for_UX_and_Brand_Systems.md::accessible-typography-for-ux-and-brand-systems-6-language-script-and-technical-delivery", "title": "6. Language script and technical delivery", "text": "## 6. Language script and technical delivery\n\nLanguage support must be considered at the beginning of typeface selection. Adding it later can produce missing-character boxes, inconsistent fallback glyphs, broken diacritics and incorrect shaping.\n\nThe font inventory should cover every required language, including names, borrowed words, currencies, mathematical symbols and punctuation. Testing must use meaningful native-language content rather than an alphabet chart alone.\n\nWriting systems organise language differently. Alphabetic, syllabic, abjad and ideographic or logographic systems make different demands on glyph design, shaping, spacing and reading. A system designed around Latin text cannot assume that the same metrics, line breaks or layout rules will work for Arabic, Devanagari, Chinese, Japanese or other scripts.\n\nArabic demonstrates the consequence clearly. It is a joining script whose characters change according to context. A font may contain Arabic glyphs yet remain unusable if the software displays them as isolated forms. Technical coverage without correct shaping is not functional accessibility.\n\nScript is also tied to culture and identity. Substituting a script, forcing transliteration or treating non-Latin writing as a secondary extension can create emotional exclusion even when the message remains technically recoverable. Multilingual brand governance should involve native readers and type specialists rather than asking an AI to simulate cultural authority.\n\n### Digital implementation\n\nImplementation should verify:\n\n- font loading and failure behaviour;\n- fallback order and metric compatibility;\n- glyph and language coverage;\n- contextual shaping and bidirectional text;\n- browser and operating-system rendering;\n- zoom, text resizing and reflow;\n- user spacing and display preferences;\n- weight availability and synthetic bold or italic behaviour;\n- performance on small, low-resolution and older devices; and\n- continuity across web, application, document and print channels.\n\nThe related WCAG criteria in the source collection cover contrast, resizing, images of text, visual presentation, text spacing and reading level. These criteria provide a technical baseline. They do not establish that a typeface is legible, readable or suitable for the brand. Current normative requirements must be retrieved separately when a conformance decision is made.\n\n", "record_type": "practitioner_editorial_typography_synthesis", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "Accessible_Typography_for_UX_and_Brand_Systems.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/Accessible_Typography_for_UX_and_Brand_Systems.md", "source_start_line": 236, "source_end_line": 264, "source_document_sha256": "2a50e1f3f4eafd02687b0e225e9ef2d170a63c82d30ecbe0d2d0d82b9c864664", "text_sha256": "2fc822c7d1742963556132a5a2c7e49e4f9af3f336ffa420a672063eaee7eb05", "heading_path": ["Accessible Typography for UX and Brand Systems", "6. Language script and technical delivery"], "metadata_json": "{\"ai_ingestion_guidance\": [\"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\", \"Do not use a typeface category, named font or single design feature as proof of accessibility.\", \"Do not state that serif or sans serif typefaces are universally more accessible.\", \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\", \"Do not infer a disability or reading condition from a person's font or display preferences.\", \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\", \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\", \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\", \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\", \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"], \"audiences\": [\"brand_designers\", \"type_designers\", \"ux_designers\", \"content_designers\", \"design_system_teams\", \"accessibility_professionals\", \"user_researchers\", \"developers\", \"ai_governance_systems\"], \"authors\": [\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"], \"content_status\": \"source_based_synthesis_with_editorial_normalisation\", \"contributing_organisation\": \"The Readability Group\", \"date_processed\": \"2026-09-18\", \"document_type\": [\"practitioner_article\", \"inclusive_typography_guidance\", \"ux_governance_reference\", \"brand_governance_reference\"], \"editorial_treatment\": [\"Combined related writings into a single article with one argument and consistent terminology.\", \"Removed repetition while preserving distinct principles, examples and qualifications.\", \"Separated typeface design, typographic application, technical delivery and brand expression.\", \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\", \"Added governance, testing and AI-use sections derived from the supplied principles.\", \"Preserved links and consolidated attribution in the source list.\"], \"jurisdictional_context\": [\"international\"], \"key_concepts\": [\"emotional_accessibility\", \"functional_accessibility\", \"technical_accessibility\", \"legibility\", \"readability\", \"letterform_ambiguity\", \"visual_crowding\", \"typeface_selection\", \"typographic_context\", \"language_and_script_support\", \"brand_expression\", \"comparative_user_testing\"], \"language\": \"en-GB\", \"primary_domains\": [\"typography\", \"digital_accessibility\", \"inclusive_design\", \"brand_design\", \"user_experience\", \"multilingual_design\"], \"short_title\": \"Accessible Typography\", \"source_basis\": {\"permitted_external_context\": \"Only sources linked from the supplied file were used to clarify authorship and context.\", \"supplied_file\": \"The Readability Group.docx\"}, \"source_characteristics\": {\"combines_multiple_articles\": true, \"contains_brand_commentary\": true, \"contains_neuroscience_explanation\": true, \"contains_practitioner_guidance\": true, \"contains_research_claims\": true, \"independently_peer_reviewed_as_a_collection\": false, \"normative_standard\": false}, \"title\": \"Accessible Typography for UX and Brand Systems\", \"version\": \"1.0-semantic\"}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "source_based_synthesis_with_editorial_normalisation", "applicable_source_license": "MIT", "source_attribution_json": "[\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"]", "source_document_intro": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Accessible_Typography_for_UX_and_Brand_Systems.md", "AGENTS.md", "README.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "Accessible_Typography_for_UX_and_Brand_Systems.md::accessible-typography-for-ux-and-brand-systems-7-testing-typography-in-context", "title": "7. Testing typography in context", "text": "## 7. Testing typography in context\n\nNo typeface should be labelled as accessible solely through expert inspection. Inspection identifies risks and suitable candidates; testing shows how people perform with them. Expert review can inform ways of optimising a font's design, user testing with a statistically significant group, in a way that does not prime or bias a design is the only way of evidencing accessibility objectively.\n\n### Test the typeface and the typography separately\n\nAn isolated test can compare character recognition between typefaces without layout becoming the main variable. An in-context test can then evaluate how the selected typeface works within headings, paragraphs, controls, tables, errors and responsive layouts.\n\nTesting only in isolation may select a typeface that performs poorly in the product. Testing only in a complete interface may make it difficult to identify whether the problem comes from the letterforms, spacing, content or interaction design.\n\n### Recruit for relevant reading experiences\n\nThe BBC Reith and Qalam work described in the source included people with moderate to severe vision impairment, people with dyslexia and people who did not identify with a related condition. The compiled account states that BBC Reith outperformed Helvetica, Arial, Gill Sans and Tiresias in the benchmark testing. The source does not provide the complete protocol or results needed to generalise that outcome to every context.\n\nResearch for another product should include people relevant to its audience and risks. Depending on scope, this may include people with low vision, dyslexia, aphasia, learning disabilities, lower literacy, age-related changes in vision, and native readers of every supported script. These categories should guide recruitment, not be used by the design team to diagnose participants.\n\n### Measure performance and experience\n\nUseful measures include:\n\n- character and word recognition accuracy;\n- reading speed under controlled conditions;\n- refixations or regressions where eye tracking is appropriate;\n- comprehension and task completion;\n- reported effort, fatigue and visual discomfort;\n- confidence and error recovery;\n- preference and perceived brand fit; and\n- performance across size, device, contrast theme and environmental context.\n\nPreference and performance should be reported separately. An organisation may decide that one candidate offers the best overall balance, but it should preserve the evidence behind that trade-off.\n\n### Compare candidates rather than testing one in isolation\n\nThe decision should compare plausible candidates using the same content, task and conditions. A test of one typeface can reveal a problem but cannot establish that it is the best available choice. Comparative testing also reduces the risk of confirming a decision already made for brand or procurement reasons.\n\n", "record_type": "proposed_testing_guidance_not_observed_results", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "Accessible_Typography_for_UX_and_Brand_Systems.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/Accessible_Typography_for_UX_and_Brand_Systems.md", "source_start_line": 265, "source_end_line": 299, "source_document_sha256": "2a50e1f3f4eafd02687b0e225e9ef2d170a63c82d30ecbe0d2d0d82b9c864664", "text_sha256": "0e0d1c0931cdee41a2c84a2e57a4143576b59387300c5344b6e6feb992149d7d", "heading_path": ["Accessible Typography for UX and Brand Systems", "7. Testing typography in context"], "metadata_json": "{\"ai_ingestion_guidance\": [\"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\", \"Do not use a typeface category, named font or single design feature as proof of accessibility.\", \"Do not state that serif or sans serif typefaces are universally more accessible.\", \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\", \"Do not infer a disability or reading condition from a person's font or display preferences.\", \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\", \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\", \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\", \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\", \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"], \"audiences\": [\"brand_designers\", \"type_designers\", \"ux_designers\", \"content_designers\", \"design_system_teams\", \"accessibility_professionals\", \"user_researchers\", \"developers\", \"ai_governance_systems\"], \"authors\": [\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"], \"content_status\": \"source_based_synthesis_with_editorial_normalisation\", \"contributing_organisation\": \"The Readability Group\", \"date_processed\": \"2026-09-18\", \"document_type\": [\"practitioner_article\", \"inclusive_typography_guidance\", \"ux_governance_reference\", \"brand_governance_reference\"], \"editorial_treatment\": [\"Combined related writings into a single article with one argument and consistent terminology.\", \"Removed repetition while preserving distinct principles, examples and qualifications.\", \"Separated typeface design, typographic application, technical delivery and brand expression.\", \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\", \"Added governance, testing and AI-use sections derived from the supplied principles.\", \"Preserved links and consolidated attribution in the source list.\"], \"jurisdictional_context\": [\"international\"], \"key_concepts\": [\"emotional_accessibility\", \"functional_accessibility\", \"technical_accessibility\", \"legibility\", \"readability\", \"letterform_ambiguity\", \"visual_crowding\", \"typeface_selection\", \"typographic_context\", \"language_and_script_support\", \"brand_expression\", \"comparative_user_testing\"], \"language\": \"en-GB\", \"primary_domains\": [\"typography\", \"digital_accessibility\", \"inclusive_design\", \"brand_design\", \"user_experience\", \"multilingual_design\"], \"short_title\": \"Accessible Typography\", \"source_basis\": {\"permitted_external_context\": \"Only sources linked from the supplied file were used to clarify authorship and context.\", \"supplied_file\": \"The Readability Group.docx\"}, \"source_characteristics\": {\"combines_multiple_articles\": true, \"contains_brand_commentary\": true, \"contains_neuroscience_explanation\": true, \"contains_practitioner_guidance\": true, \"contains_research_claims\": true, \"independently_peer_reviewed_as_a_collection\": false, \"normative_standard\": false}, \"title\": \"Accessible Typography for UX and Brand Systems\", \"version\": \"1.0-semantic\"}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "source_based_synthesis_with_editorial_normalisation", "applicable_source_license": "MIT", "source_attribution_json": "[\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"]", "source_document_intro": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Accessible_Typography_for_UX_and_Brand_Systems.md", "AGENTS.md", "README.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "Accessible_Typography_for_UX_and_Brand_Systems.md::accessible-typography-for-ux-and-brand-systems-8-governance-for-ux-brand-and-ai-systems", "title": "8. Governance for UX brand and AI systems", "text": "## 8. Governance for UX brand and AI systems\n\n### Governance principles\n\n1. **Define the intended reading conditions.** Record audiences, tasks, languages, scripts, devices, sizes and environmental constraints.\n2. **Separate the three accessibility outcomes.** Evaluate emotional response, reading function and technical delivery rather than collapsing them into one score.\n3. **Treat design features as hypotheses.** Open apertures, humanist construction, wider spacing or a particular `a` form may justify testing but cannot prove accessibility.\n4. **Use current standards for technical requirements.** WCAG and organisational policy define minimum obligations. User evidence determines whether the implementation works in practice.\n5. **Retain user control.** Typography must tolerate zoom, text resizing, spacing overrides, contrast preferences and alternative presentation without loss of content or function.\n6. **Test multilingual claims with native readers.** Glyph coverage and automated rendering checks cannot establish linguistic or cultural suitability.\n7. **Record trade-offs.** If brand expression and reading performance point towards different choices, document the evidence, intended contexts and approved limits.\n\n### Rules for AI-assisted design\n\nAn AI may use this document to shortlist risks, generate specimen strings, propose test conditions, check a font inventory or review a design-system specification. It must not certify a typeface as accessible from its name, category or marketing description.\n\nWhen generating a recommendation, the AI should state:\n\n- the audience and reading task it assumes;\n- the language, script, device and size in scope;\n- the observed typeface or typography feature;\n- whether the issue concerns emotional, functional or technical accessibility;\n- the evidence available and what remains untested;\n- the comparison or user test required; and\n- the human owner who must approve the decision.\n\nThe AI should block or flag:\n\n- a claim that one font is accessible to everyone;\n- serif or sans serif presented as a universal rule;\n- a dyslexia-related claim without relevant evidence;\n- fixed-size guidance presented without reference to the typeface or user resizing;\n- use of a typeface that lacks required characters or script shaping;\n- body or interface text that depends on a decorative display face;\n- fallback typography that changes meaning, hierarchy or brand attribution;\n- a palette that reduces visual discomfort by falling below required contrast; and\n- testing that records preference but not reading performance, or performance but not participant experience.\n\n### Decision record for machine-managed systems\n\nThe following fields allow a governance system to preserve the basis of a typographic decision:\n\n```yaml\ntypography_decision:\n component: \"body_text\"\n candidate_typeface: \"example_name\"\n audiences: []\n languages_and_scripts: []\n reading_tasks: []\n contexts_and_devices: []\n emotional_accessibility_evidence: []\n functional_accessibility_evidence: []\n technical_accessibility_evidence: []\n standards_and_policy_requirements: []\n unresolved_risks: []\n user_testing_status: \"not_started\"\n decision_status: \"requires_human_review\"\n approving_roles: []\n review_date: null\n```\n\nThis record is evidence, not a scorecard. Empty fields must remain visible so an AI cannot convert missing evidence into an assumption of success.\n\n", "record_type": "governance_and_blank_record_not_approved_decision", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "Accessible_Typography_for_UX_and_Brand_Systems.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/Accessible_Typography_for_UX_and_Brand_Systems.md", "source_start_line": 300, "source_end_line": 362, "source_document_sha256": "2a50e1f3f4eafd02687b0e225e9ef2d170a63c82d30ecbe0d2d0d82b9c864664", "text_sha256": "8cd0238d6cced58c76f3b99ea364e234fff9f8dbf3de560502c6c5f2471ce485", "heading_path": ["Accessible Typography for UX and Brand Systems", "8. Governance for UX brand and AI systems"], "metadata_json": "{\"ai_ingestion_guidance\": [\"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\", \"Do not use a typeface category, named font or single design feature as proof of accessibility.\", \"Do not state that serif or sans serif typefaces are universally more accessible.\", \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\", \"Do not infer a disability or reading condition from a person's font or display preferences.\", \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\", \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\", \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\", \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\", \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"], \"audiences\": [\"brand_designers\", \"type_designers\", \"ux_designers\", \"content_designers\", \"design_system_teams\", \"accessibility_professionals\", \"user_researchers\", \"developers\", \"ai_governance_systems\"], \"authors\": [\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"], \"content_status\": \"source_based_synthesis_with_editorial_normalisation\", \"contributing_organisation\": \"The Readability Group\", \"date_processed\": \"2026-09-18\", \"document_type\": [\"practitioner_article\", \"inclusive_typography_guidance\", \"ux_governance_reference\", \"brand_governance_reference\"], \"editorial_treatment\": [\"Combined related writings into a single article with one argument and consistent terminology.\", \"Removed repetition while preserving distinct principles, examples and qualifications.\", \"Separated typeface design, typographic application, technical delivery and brand expression.\", \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\", \"Added governance, testing and AI-use sections derived from the supplied principles.\", \"Preserved links and consolidated attribution in the source list.\"], \"jurisdictional_context\": [\"international\"], \"key_concepts\": [\"emotional_accessibility\", \"functional_accessibility\", \"technical_accessibility\", \"legibility\", \"readability\", \"letterform_ambiguity\", \"visual_crowding\", \"typeface_selection\", \"typographic_context\", \"language_and_script_support\", \"brand_expression\", \"comparative_user_testing\"], \"language\": \"en-GB\", \"primary_domains\": [\"typography\", \"digital_accessibility\", \"inclusive_design\", \"brand_design\", \"user_experience\", \"multilingual_design\"], \"short_title\": \"Accessible Typography\", \"source_basis\": {\"permitted_external_context\": \"Only sources linked from the supplied file were used to clarify authorship and context.\", \"supplied_file\": \"The Readability Group.docx\"}, \"source_characteristics\": {\"combines_multiple_articles\": true, \"contains_brand_commentary\": true, \"contains_neuroscience_explanation\": true, \"contains_practitioner_guidance\": true, \"contains_research_claims\": true, \"independently_peer_reviewed_as_a_collection\": false, \"normative_standard\": false}, \"title\": \"Accessible Typography for UX and Brand Systems\", \"version\": \"1.0-semantic\"}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "source_based_synthesis_with_editorial_normalisation", "applicable_source_license": "MIT", "source_attribution_json": "[\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"]", "source_document_intro": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Accessible_Typography_for_UX_and_Brand_Systems.md", "AGENTS.md", "README.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "Accessible_Typography_for_UX_and_Brand_Systems.md::accessible-typography-for-ux-and-brand-systems-conclusion", "title": "Conclusion", "text": "## Conclusion\n\nAccessible typography is a property of a complete reading experience. It emerges from the typeface, the way it is set, the content, the reader, the language, the display and the surrounding environment.\n\nThe strongest governance question is not, “Is this an accessible font?” It is, “For whom, for which task, in which language and context, and according to what evidence does this typography work?”\n\nThat question protects both accessibility and brand quality. It replaces myths and fixed recipes with informed selection, comparative testing and accountable decisions.\n\n---\n\n", "record_type": "practitioner_editorial_typography_synthesis", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "Accessible_Typography_for_UX_and_Brand_Systems.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/Accessible_Typography_for_UX_and_Brand_Systems.md", "source_start_line": 363, "source_end_line": 372, "source_document_sha256": "2a50e1f3f4eafd02687b0e225e9ef2d170a63c82d30ecbe0d2d0d82b9c864664", "text_sha256": "e66434563644e7a1d73466a4d1271fbfb017d3d8986fb846e96ec06ecdb2a9ad", "heading_path": ["Accessible Typography for UX and Brand Systems", "Conclusion"], "metadata_json": "{\"ai_ingestion_guidance\": [\"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\", \"Do not use a typeface category, named font or single design feature as proof of accessibility.\", \"Do not state that serif or sans serif typefaces are universally more accessible.\", \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\", \"Do not infer a disability or reading condition from a person's font or display preferences.\", \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\", \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\", \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\", \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\", \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"], \"audiences\": [\"brand_designers\", \"type_designers\", \"ux_designers\", \"content_designers\", \"design_system_teams\", \"accessibility_professionals\", \"user_researchers\", \"developers\", \"ai_governance_systems\"], \"authors\": [\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"], \"content_status\": \"source_based_synthesis_with_editorial_normalisation\", \"contributing_organisation\": \"The Readability Group\", \"date_processed\": \"2026-09-18\", \"document_type\": [\"practitioner_article\", \"inclusive_typography_guidance\", \"ux_governance_reference\", \"brand_governance_reference\"], \"editorial_treatment\": [\"Combined related writings into a single article with one argument and consistent terminology.\", \"Removed repetition while preserving distinct principles, examples and qualifications.\", \"Separated typeface design, typographic application, technical delivery and brand expression.\", \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\", \"Added governance, testing and AI-use sections derived from the supplied principles.\", \"Preserved links and consolidated attribution in the source list.\"], \"jurisdictional_context\": [\"international\"], \"key_concepts\": [\"emotional_accessibility\", \"functional_accessibility\", \"technical_accessibility\", \"legibility\", \"readability\", \"letterform_ambiguity\", \"visual_crowding\", \"typeface_selection\", \"typographic_context\", \"language_and_script_support\", \"brand_expression\", \"comparative_user_testing\"], \"language\": \"en-GB\", \"primary_domains\": [\"typography\", \"digital_accessibility\", \"inclusive_design\", \"brand_design\", \"user_experience\", \"multilingual_design\"], \"short_title\": \"Accessible Typography\", \"source_basis\": {\"permitted_external_context\": \"Only sources linked from the supplied file were used to clarify authorship and context.\", \"supplied_file\": \"The Readability Group.docx\"}, \"source_characteristics\": {\"combines_multiple_articles\": true, \"contains_brand_commentary\": true, \"contains_neuroscience_explanation\": true, \"contains_practitioner_guidance\": true, \"contains_research_claims\": true, \"independently_peer_reviewed_as_a_collection\": false, \"normative_standard\": false}, \"title\": \"Accessible Typography for UX and Brand Systems\", \"version\": \"1.0-semantic\"}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "source_based_synthesis_with_editorial_normalisation", "applicable_source_license": "MIT", "source_attribution_json": "[\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"]", "source_document_intro": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Accessible_Typography_for_UX_and_Brand_Systems.md", "AGENTS.md", "README.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "Accessible_Typography_for_UX_and_Brand_Systems.md::accessible-typography-for-ux-and-brand-systems-sources-and-attribution", "title": "Sources and attribution", "text": "## Sources and attribution\n\nThis article combines material supplied in *The Readability Group - Various Writings*. The combined work is attributed to **Gareth Ford Williams, Bruno Maag, David Bailey and Michael Mathews**. The source file does not assign every passage to an individual author; the list below records individual attribution where the linked publication identifies it.\n\n### Foundational Readability Group articles\n\n- Gareth Ford Williams, [A Guide to Understanding What Makes a Typeface Accessible](https://levelup.gitconnected.com/a-guide-to-understanding-what-makes-a-typeface-accessible-and-how-to-make-informed-decisions-9e5c0b9040a0), 14 August 2020.\n- Bruno Maag, [The Three Pillars of Accessibility](https://medium.com/the-readability-group/the-three-components-of-accessibility-86075e14f46f), 8 February 2021.\n- Bruno Maag, [About Legibility and Readability](https://medium.com/the-readability-group/about-legibility-and-readability-596fcd432a06), 15 March 2021.\n- David Bailey, [The Emotional Accessibility of Reading](https://medium.com/the-readability-group/the-emotional-accessibility-of-reading-a450286906ad), 26 March 2021.\n- Bruno Maag, [Typographic Accessibility in More Detail](https://medium.com/the-readability-group/typographic-accessibility-in-more-detail-4a11a0ef1cc2), 1 April 2021.\n- Bruno Maag, [The Visual System](https://medium.com/the-readability-group/the-visual-system-a-brief-guide-to-anatomy-and-physiology-in-the-context-of-typography-b29718389f16), 4 May 2021.\n- Bruno Maag, [It's All Squiggles to Me](https://medium.com/the-readability-group/its-all-squiggles-to-me-541b326a94a8), 8 June 2021.\n- [The Readability Group](http://thereadability.group/), collective research initiative.\n\n### BBC Reith and type design\n\n- David Bailey, [Introducing Reith - the New Face of the BBC](https://www.bbc.co.uk/gel/articles/introducing-bbc-reith).\n- Dalton Maag, [BBC Reith](https://www.daltonmaag.com/work/bbc-reith).\n- Lucy Bourton, [BBC's New Typeface BBC Reith Is Designed to Improve Legibility on Screen](https://www.itsnicethat.com/news/bbc-reith-typeface-graphic-design-110817).\n- Phil Garnham, [Get to Grips with Accessible Web Typography](https://www.creativebloq.com/features/master-accessible-web-typography).\n\n### Legibility readability and reading research\n\n- Association of Registered Graphic Designers, Canada, [A Practical Handbook on Accessible Graphic Design](https://www.rgd.ca/resources/accessibility/access).\n- Lior Reich, Marcin Szwed, Laurent Cohen and Amir Amedi, [A Ventral Visual Stream Reading Center Independent of Visual Experience](https://www.sciencedirect.com/science/article/pii/S0960982211000637), 2011.\n- Allan Haley, [It's About Legibility](https://www.fonts.com/content/learning/fontology/level-4/fine-typography/legibility).\n- Ilene Strizver, [Legibility and Readability What's the Difference](https://creativepro.com/legibility-and-readability-whats-the-difference/).\n- Stanislas Dehaene, [Reading in the Brain](https://readinginthebrain.pagesperso-orange.fr/intro.htm), ISBN 9780143118053.\n- Julian G. Elliott and Elena L. Grigorenko, *The Dyslexia Debate*, ISBN 9780521135870.\n- Sophie Beier, [Typeface Legibility for Visually Impaired Readers](https://sofiebeier.dk/).\n- Kevin Larson, [The Science of Word Recognition](https://docs.microsoft.com/en-us/typography/develop/word-recognition).\n- Eleni Beveratou, [The Effect of Type Design and Typesetting on Visually Impaired Readers](https://www.researchgate.net/publication/309749121_The_effect_of_type_design_and_typesetting_on_visually_impaired_readers).\n- Jennifer Buckingham and Anne Castles, [Why Do Some Children Learn to Read Without Explicit Teaching](https://www.nomanis.com.au/post/why-do-some-children-learn-to-read-without-explicit-teaching).\n- [Word Superiority Effect](https://en.wikipedia.org/wiki/Word_superiority_effect), background reference linked from the source material.\n\n### Visual system references\n\n- Mayfield Clinic, [Anatomy of the Brain](https://mayfieldclinic.com/pe-anatbrain.htm).\n- [Visual System](https://en.wikipedia.org/wiki/Visual_system), background reference linked from the source material.\n- [Optic Nerve](https://en.wikipedia.org/wiki/Optic_nerve), background reference linked from the source material.\n- [Magnocellular Cell](https://en.wikipedia.org/wiki/Magnocellular_cell), background reference linked from the source material.\n- [Parvocellular Cell](https://en.wikipedia.org/wiki/Parvocellular_cell), background reference linked from the source material.\n- Neuroscientifically Challenged, [Know Your Brain Corpus Callosum](https://www.neuroscientificallychallenged.com/blog/know-your-brain-corpus-callosum).\n\n### Content literacy and standards\n\n- Sarah Richards, [Specifying a Reading Age for Web Content](https://contentdesign.london/reading/specifying-a-reading-age-for-web-content/).\n- UK Department for Education, [Adult Education Survey 2016](https://www.gov.uk/government/publications/adult-education-survey-2016).\n- John Sabatini, [Understanding the Basic Reading Skills of US Adults](https://lincs.ed.gov/professional-development/resource-collections/profile-896).\n- W3C, [Web Content Accessibility Guidelines 2.1](https://www.w3.org/TR/WCAG21/), including criteria linked in the source for captions, contrast, text resizing, images of text, visual presentation, text spacing and reading level.\n\n### Cultural and illustrative examples\n\n- Huffington Post, [Higgs Boson Discovery Announcement Made in Comic Sans](https://www.huffingtonpost.co.uk/2012/07/04/higgs-boson-discovery-comic-sans_n_1648494.html).\n- Business Insider, [The Alien Writing System in Arrival](https://www.businessinsider.com/alien-language-in-arrival-linguist-2016-11?r=US&IR=T).\n\n", "record_type": "source_attribution_and_interpretation_limits", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "Accessible_Typography_for_UX_and_Brand_Systems.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/Accessible_Typography_for_UX_and_Brand_Systems.md", "source_start_line": 373, "source_end_line": 429, "source_document_sha256": "2a50e1f3f4eafd02687b0e225e9ef2d170a63c82d30ecbe0d2d0d82b9c864664", "text_sha256": "e54dcf0b8f4ae40a1d75ea98dc63cc0db42e2a070194edd7c0160c427ca3d484", "heading_path": ["Accessible Typography for UX and Brand Systems", "Sources and attribution"], "metadata_json": "{\"ai_ingestion_guidance\": [\"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\", \"Do not use a typeface category, named font or single design feature as proof of accessibility.\", \"Do not state that serif or sans serif typefaces are universally more accessible.\", \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\", \"Do not infer a disability or reading condition from a person's font or display preferences.\", \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\", \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\", \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\", \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\", \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"], \"audiences\": [\"brand_designers\", \"type_designers\", \"ux_designers\", \"content_designers\", \"design_system_teams\", \"accessibility_professionals\", \"user_researchers\", \"developers\", \"ai_governance_systems\"], \"authors\": [\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"], \"content_status\": \"source_based_synthesis_with_editorial_normalisation\", \"contributing_organisation\": \"The Readability Group\", \"date_processed\": \"2026-09-18\", \"document_type\": [\"practitioner_article\", \"inclusive_typography_guidance\", \"ux_governance_reference\", \"brand_governance_reference\"], \"editorial_treatment\": [\"Combined related writings into a single article with one argument and consistent terminology.\", \"Removed repetition while preserving distinct principles, examples and qualifications.\", \"Separated typeface design, typographic application, technical delivery and brand expression.\", \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\", \"Added governance, testing and AI-use sections derived from the supplied principles.\", \"Preserved links and consolidated attribution in the source list.\"], \"jurisdictional_context\": [\"international\"], \"key_concepts\": [\"emotional_accessibility\", \"functional_accessibility\", \"technical_accessibility\", \"legibility\", \"readability\", \"letterform_ambiguity\", \"visual_crowding\", \"typeface_selection\", \"typographic_context\", \"language_and_script_support\", \"brand_expression\", \"comparative_user_testing\"], \"language\": \"en-GB\", \"primary_domains\": [\"typography\", \"digital_accessibility\", \"inclusive_design\", \"brand_design\", \"user_experience\", \"multilingual_design\"], \"short_title\": \"Accessible Typography\", \"source_basis\": {\"permitted_external_context\": \"Only sources linked from the supplied file were used to clarify authorship and context.\", \"supplied_file\": \"The Readability Group.docx\"}, \"source_characteristics\": {\"combines_multiple_articles\": true, \"contains_brand_commentary\": true, \"contains_neuroscience_explanation\": true, \"contains_practitioner_guidance\": true, \"contains_research_claims\": true, \"independently_peer_reviewed_as_a_collection\": false, \"normative_standard\": false}, \"title\": \"Accessible Typography for UX and Brand Systems\", \"version\": \"1.0-semantic\"}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "source_based_synthesis_with_editorial_normalisation", "applicable_source_license": "MIT", "source_attribution_json": "[\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"]", "source_document_intro": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Accessible_Typography_for_UX_and_Brand_Systems.md", "AGENTS.md", "README.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "Accessible_Typography_for_UX_and_Brand_Systems.md::accessible-typography-for-ux-and-brand-systems-source-and-interpretation-notes", "title": "Source and interpretation notes", "text": "## Source and interpretation notes\n\nThe linked articles mix practitioner experience, research interpretation and illustrative commentary. They should not be treated as one peer-reviewed study or as a replacement for current standards. Claims about a particular typeface, reading group or neurological mechanism require the original study method and evidence before they are generalised.\n\nThe supplied compilation identifies Michael Mathews as a creator of the combined work but does not attach his name to a specific linked article. This edition therefore credits him as a co-author of the source collection without inventing an individual article attribution.\n\nWhen an LLM retrieves this article for a design decision, it should also retrieve the current organisational brand system, supported-language inventory, applicable accessibility requirements, implementation constraints and evidence from comparative testing with intended readers.\n\n", "record_type": "source_attribution_and_interpretation_limits", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "Accessible_Typography_for_UX_and_Brand_Systems.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/Accessible_Typography_for_UX_and_Brand_Systems.md", "source_start_line": 430, "source_end_line": 437, "source_document_sha256": "2a50e1f3f4eafd02687b0e225e9ef2d170a63c82d30ecbe0d2d0d82b9c864664", "text_sha256": "27d1cf9d751c398b256085803db5f57033414642363e8d06e7236dfeef434e26", "heading_path": ["Accessible Typography for UX and Brand Systems", "Source and interpretation notes"], "metadata_json": "{\"ai_ingestion_guidance\": [\"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\", \"Do not use a typeface category, named font or single design feature as proof of accessibility.\", \"Do not state that serif or sans serif typefaces are universally more accessible.\", \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\", \"Do not infer a disability or reading condition from a person's font or display preferences.\", \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\", \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\", \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\", \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\", \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"], \"audiences\": [\"brand_designers\", \"type_designers\", \"ux_designers\", \"content_designers\", \"design_system_teams\", \"accessibility_professionals\", \"user_researchers\", \"developers\", \"ai_governance_systems\"], \"authors\": [\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"], \"content_status\": \"source_based_synthesis_with_editorial_normalisation\", \"contributing_organisation\": \"The Readability Group\", \"date_processed\": \"2026-09-18\", \"document_type\": [\"practitioner_article\", \"inclusive_typography_guidance\", \"ux_governance_reference\", \"brand_governance_reference\"], \"editorial_treatment\": [\"Combined related writings into a single article with one argument and consistent terminology.\", \"Removed repetition while preserving distinct principles, examples and qualifications.\", \"Separated typeface design, typographic application, technical delivery and brand expression.\", \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\", \"Added governance, testing and AI-use sections derived from the supplied principles.\", \"Preserved links and consolidated attribution in the source list.\"], \"jurisdictional_context\": [\"international\"], \"key_concepts\": [\"emotional_accessibility\", \"functional_accessibility\", \"technical_accessibility\", \"legibility\", \"readability\", \"letterform_ambiguity\", \"visual_crowding\", \"typeface_selection\", \"typographic_context\", \"language_and_script_support\", \"brand_expression\", \"comparative_user_testing\"], \"language\": \"en-GB\", \"primary_domains\": [\"typography\", \"digital_accessibility\", \"inclusive_design\", \"brand_design\", \"user_experience\", \"multilingual_design\"], \"short_title\": \"Accessible Typography\", \"source_basis\": {\"permitted_external_context\": \"Only sources linked from the supplied file were used to clarify authorship and context.\", \"supplied_file\": \"The Readability Group.docx\"}, \"source_characteristics\": {\"combines_multiple_articles\": true, \"contains_brand_commentary\": true, \"contains_neuroscience_explanation\": true, \"contains_practitioner_guidance\": true, \"contains_research_claims\": true, \"independently_peer_reviewed_as_a_collection\": false, \"normative_standard\": false}, \"title\": \"Accessible Typography for UX and Brand Systems\", \"version\": \"1.0-semantic\"}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "source_based_synthesis_with_editorial_normalisation", "applicable_source_license": "MIT", "source_attribution_json": "[\"Gareth Ford Williams\", \"Bruno Maag\", \"David Bailey\", \"Michael Mathews\"]", "source_document_intro": "---\ntitle: \"Accessible Typography for UX and Brand Systems\"\nshort_title: \"Accessible Typography\"\nauthors:\n - \"Gareth Ford Williams\"\n - \"Bruno Maag\"\n - \"David Bailey\"\n - \"Michael Mathews\"\ncontributing_organisation: \"The Readability Group\"\nlanguage: \"en-GB\"\ndocument_type:\n - \"practitioner_article\"\n - \"inclusive_typography_guidance\"\n - \"ux_governance_reference\"\n - \"brand_governance_reference\"\ncontent_status: \"source_based_synthesis_with_editorial_normalisation\"\ndate_processed: \"2026-09-18\"\nversion: \"1.0-semantic\"\njurisdictional_context:\n - \"international\"\nprimary_domains:\n - \"typography\"\n - \"digital_accessibility\"\n - \"inclusive_design\"\n - \"brand_design\"\n - \"user_experience\"\n - \"multilingual_design\"\naudiences:\n - \"brand_designers\"\n - \"type_designers\"\n - \"ux_designers\"\n - \"content_designers\"\n - \"design_system_teams\"\n - \"accessibility_professionals\"\n - \"user_researchers\"\n - \"developers\"\n - \"ai_governance_systems\"\nkey_concepts:\n - \"emotional_accessibility\"\n - \"functional_accessibility\"\n - \"technical_accessibility\"\n - \"legibility\"\n - \"readability\"\n - \"letterform_ambiguity\"\n - \"visual_crowding\"\n - \"typeface_selection\"\n - \"typographic_context\"\n - \"language_and_script_support\"\n - \"brand_expression\"\n - \"comparative_user_testing\"\nsource_basis:\n supplied_file: \"The Readability Group.docx\"\n permitted_external_context: \"Only sources linked from the supplied file were used to clarify authorship and context.\"\nsource_characteristics:\n combines_multiple_articles: true\n contains_practitioner_guidance: true\n contains_research_claims: true\n contains_neuroscience_explanation: true\n contains_brand_commentary: true\n normative_standard: false\n independently_peer_reviewed_as_a_collection: false\neditorial_treatment:\n - \"Combined related writings into a single article with one argument and consistent terminology.\"\n - \"Removed repetition while preserving distinct principles, examples and qualifications.\"\n - \"Separated typeface design, typographic application, technical delivery and brand expression.\"\n - \"Changed categorical claims into testable design considerations where the source did not establish a universal rule.\"\n - \"Added governance, testing and AI-use sections derived from the supplied principles.\"\n - \"Preserved links and consolidated attribution in the source list.\"\nai_ingestion_guidance:\n - \"Use this document to generate requirements, questions, evaluation criteria and test plans for typography in UX and brand systems.\"\n - \"Do not use a typeface category, named font or single design feature as proof of accessibility.\"\n - \"Do not state that serif or sans serif typefaces are universally more accessible.\"\n - \"Do not recommend a specialist dyslexia font solely because it is marketed as accessible.\"\n - \"Do not infer a disability or reading condition from a person's font or display preferences.\"\n - \"Distinguish legibility, readability, comprehension, preference and emotional response when interpreting evidence.\"\n - \"Treat emotional, functional and technical accessibility as related but separately testable qualities.\"\n - \"Retrieve current WCAG requirements and organisational policy before making a conformance decision.\"\n - \"Escalate brand trade-offs, unsupported scientific claims and conflicting user evidence for human review.\"\n - \"Require comparative testing in the intended language, script, device, size and usage context before approving a typeface as a system default.\"\n---\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["Accessible_Typography_for_UX_and_Brand_Systems.md", "AGENTS.md", "README.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "README.md::accessible-typography-for-ux-and-brand-systems", "title": "Accessible Typography for UX and Brand Systems", "text": "# Accessible Typography for UX and Brand Systems\n\nA curated repository containing the combined writings of The Readability Group in a single, structured source document on accessible typography for UX, brand, and design-system work.\n\nThis project is intended to support:\n\n- research and reference on typography accessibility\n- inclusive design and UX governance\n- brand-system decision-making\n- AI/LLM training and retrieval grounded in a clear editorial synthesis\n- LLM-based guidance for brand, communications, marketing, and publishing design\n\n", "record_type": "orientation", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "README.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/README.md", "source_start_line": 1, "source_end_line": 12, "source_document_sha256": "f404e743fa6eaf9f48227c12427cac0db80d89428007a5cba27407342aca2a90", "text_sha256": "f80537a349310e947cfbb4d8e7e6f9ad05383bc02f70bd34ed3581de48db2cd1", "heading_path": ["Accessible Typography for UX and Brand Systems"], "metadata_json": "{}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "[]", "source_document_intro": "# Accessible Typography for UX and Brand Systems\n\nA curated repository containing the combined writings of The Readability Group in a single, structured source document on accessible typography for UX, brand, and design-system work.\n\nThis project is intended to support:\n\n- research and reference on typography accessibility\n- inclusive design and UX governance\n- brand-system decision-making\n- AI/LLM training and retrieval grounded in a clear editorial synthesis\n- LLM-based guidance for brand, communications, marketing, and publishing design\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["README.md", "AGENTS.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "README.md::accessible-typography-for-ux-and-brand-systems-repository-contents", "title": "Repository contents", "text": "## Repository contents\n\n- `Accessible_Typography_for_UX_and_Brand_Systems.md` — the main document, combining the source writings into a single structured article.\n- `AGENTS.md` — a purpose-built instruction file for any LLM involved in brand, communications, marketing, or publishing design, grounded in the repository's accessible typography guidance.\n- `LICENSE` — MIT license for the repository.\n- `README.md` — project overview and usage guidance.\n\n", "record_type": "orientation", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "README.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/README.md", "source_start_line": 13, "source_end_line": 19, "source_document_sha256": "f404e743fa6eaf9f48227c12427cac0db80d89428007a5cba27407342aca2a90", "text_sha256": "9d2aa42cd6b419495f88aff9fede4089c8d062ad0abd6f710317a64d3717bdc0", "heading_path": ["Accessible Typography for UX and Brand Systems", "Repository contents"], "metadata_json": "{}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "[]", "source_document_intro": "# Accessible Typography for UX and Brand Systems\n\nA curated repository containing the combined writings of The Readability Group in a single, structured source document on accessible typography for UX, brand, and design-system work.\n\nThis project is intended to support:\n\n- research and reference on typography accessibility\n- inclusive design and UX governance\n- brand-system decision-making\n- AI/LLM training and retrieval grounded in a clear editorial synthesis\n- LLM-based guidance for brand, communications, marketing, and publishing design\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["README.md", "AGENTS.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "README.md::accessible-typography-for-ux-and-brand-systems-about-the-document", "title": "About the document", "text": "## About the document\n\nThe main article explores how typography affects:\n\n- legibility and readability\n- emotional accessibility\n- functional accessibility\n- technical accessibility\n- multilingual and script support\n- brand expression and identity\n- governance and testing in digital products\n\nIt frames accessibility not as a single font choice or one-size-fits-all rule, but as a broader outcome of typeface design, application, language support, context, and user testing.\n\n", "record_type": "orientation", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "README.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/README.md", "source_start_line": 20, "source_end_line": 33, "source_document_sha256": "f404e743fa6eaf9f48227c12427cac0db80d89428007a5cba27407342aca2a90", "text_sha256": "286bafe7102f0f9209a2fd10fbfb64006367f30d38230997163ea00684174bb2", "heading_path": ["Accessible Typography for UX and Brand Systems", "About the document"], "metadata_json": "{}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "[]", "source_document_intro": "# Accessible Typography for UX and Brand Systems\n\nA curated repository containing the combined writings of The Readability Group in a single, structured source document on accessible typography for UX, brand, and design-system work.\n\nThis project is intended to support:\n\n- research and reference on typography accessibility\n- inclusive design and UX governance\n- brand-system decision-making\n- AI/LLM training and retrieval grounded in a clear editorial synthesis\n- LLM-based guidance for brand, communications, marketing, and publishing design\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["README.md", "AGENTS.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "README.md::accessible-typography-for-ux-and-brand-systems-agent-guidance", "title": "Agent guidance", "text": "## Agent guidance\n\nThe repository also includes `AGENTS.md`, which provides operational instructions for AI systems working in brand, communications, marketing, and publishing design. Its purpose is to help an LLM:\n\n- separate emotional, functional, and technical accessibility in typography decisions;\n- evaluate type choices in context rather than as isolated style preferences;\n- account for audience, task, language, script, and device conditions before recommending type;\n- avoid unsupported claims that a single font or a font category is universally accessible;\n- integrate accessibility, brand integrity, and editorial clarity into one decision framework.\n\nThis file is intended as a practical design and governance aid for AI-assisted brand and communications work grounded in the repository's source material.\n\n", "record_type": "orientation", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "README.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/README.md", "source_start_line": 34, "source_end_line": 45, "source_document_sha256": "f404e743fa6eaf9f48227c12427cac0db80d89428007a5cba27407342aca2a90", "text_sha256": "8e85047a2230a82f831ff526f65c262eca63b2b2af0b41941f78cb3c46ec55c3", "heading_path": ["Accessible Typography for UX and Brand Systems", "Agent guidance"], "metadata_json": "{}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "[]", "source_document_intro": "# Accessible Typography for UX and Brand Systems\n\nA curated repository containing the combined writings of The Readability Group in a single, structured source document on accessible typography for UX, brand, and design-system work.\n\nThis project is intended to support:\n\n- research and reference on typography accessibility\n- inclusive design and UX governance\n- brand-system decision-making\n- AI/LLM training and retrieval grounded in a clear editorial synthesis\n- LLM-based guidance for brand, communications, marketing, and publishing design\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["README.md", "AGENTS.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "README.md::accessible-typography-for-ux-and-brand-systems-intended-use", "title": "Intended use", "text": "## Intended use\n\nThis repository is suitable for:\n\n- design and content teams defining typographic standards\n- accessibility reviews and UX audits\n- brand and design-system governance\n- AI systems that need source material on accessible typography\n- LLMs assisting with writing, editorial, brand, communications, marketing, and publishing design\n- researchers and practitioners studying inclusive typographic practice\n\n", "record_type": "orientation", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "README.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/README.md", "source_start_line": 46, "source_end_line": 56, "source_document_sha256": "f404e743fa6eaf9f48227c12427cac0db80d89428007a5cba27407342aca2a90", "text_sha256": "f3907eaa1d40ae28f822d4cacdc8a4ba93d2f92e11fbe32e8709a7952ee10533", "heading_path": ["Accessible Typography for UX and Brand Systems", "Intended use"], "metadata_json": "{}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "[]", "source_document_intro": "# Accessible Typography for UX and Brand Systems\n\nA curated repository containing the combined writings of The Readability Group in a single, structured source document on accessible typography for UX, brand, and design-system work.\n\nThis project is intended to support:\n\n- research and reference on typography accessibility\n- inclusive design and UX governance\n- brand-system decision-making\n- AI/LLM training and retrieval grounded in a clear editorial synthesis\n- LLM-based guidance for brand, communications, marketing, and publishing design\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["README.md", "AGENTS.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "README.md::accessible-typography-for-ux-and-brand-systems-key-themes", "title": "Key themes", "text": "## Key themes\n\nThe document covers themes such as:\n\n- the difference between legibility and readability\n- how visual reading works in practice\n- why typeface choice must be evaluated in context\n- how serif and sans serif styles are not universally superior\n- the importance of script, language, and glyph coverage\n- how testing should compare candidates under realistic conditions\n- how AI-assisted design tools should avoid overclaiming accessibility\n\n", "record_type": "orientation", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "README.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/README.md", "source_start_line": 57, "source_end_line": 68, "source_document_sha256": "f404e743fa6eaf9f48227c12427cac0db80d89428007a5cba27407342aca2a90", "text_sha256": "6d4d0207c7950fa6ce70889dd124ae8ef04c483280f4e5554044e5902f533747", "heading_path": ["Accessible Typography for UX and Brand Systems", "Key themes"], "metadata_json": "{}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "[]", "source_document_intro": "# Accessible Typography for UX and Brand Systems\n\nA curated repository containing the combined writings of The Readability Group in a single, structured source document on accessible typography for UX, brand, and design-system work.\n\nThis project is intended to support:\n\n- research and reference on typography accessibility\n- inclusive design and UX governance\n- brand-system decision-making\n- AI/LLM training and retrieval grounded in a clear editorial synthesis\n- LLM-based guidance for brand, communications, marketing, and publishing design\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["README.md", "AGENTS.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "README.md::accessible-typography-for-ux-and-brand-systems-attribution", "title": "Attribution", "text": "## Attribution\n\nThe source material combines writings associated with:\n\n- Gareth Ford Williams\n- Bruno Maag\n- David Bailey\n- Michael Mathews\n- The Readability Group\n\nThe repository preserves the source-based editorial synthesis and integrates relevant guidance into a single, coherent document.\n\n", "record_type": "orientation", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "README.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/README.md", "source_start_line": 69, "source_end_line": 80, "source_document_sha256": "f404e743fa6eaf9f48227c12427cac0db80d89428007a5cba27407342aca2a90", "text_sha256": "ae0ec7acfb3e8af1629554c83707de815027b4ececcdbb6927e4334d5e0ee2f3", "heading_path": ["Accessible Typography for UX and Brand Systems", "Attribution"], "metadata_json": "{}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "[]", "source_document_intro": "# Accessible Typography for UX and Brand Systems\n\nA curated repository containing the combined writings of The Readability Group in a single, structured source document on accessible typography for UX, brand, and design-system work.\n\nThis project is intended to support:\n\n- research and reference on typography accessibility\n- inclusive design and UX governance\n- brand-system decision-making\n- AI/LLM training and retrieval grounded in a clear editorial synthesis\n- LLM-based guidance for brand, communications, marketing, and publishing design\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["README.md", "AGENTS.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "README.md::accessible-typography-for-ux-and-brand-systems-license", "title": "License", "text": "## License\n\nThis project is licensed under the MIT License. See the `LICENSE` file for full details.\n\n", "record_type": "orientation", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "README.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/README.md", "source_start_line": 81, "source_end_line": 84, "source_document_sha256": "f404e743fa6eaf9f48227c12427cac0db80d89428007a5cba27407342aca2a90", "text_sha256": "8bb01ee73606850bae654ab502cece00738b119b00880705582ed3735c434408", "heading_path": ["Accessible Typography for UX and Brand Systems", "License"], "metadata_json": "{}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "[]", "source_document_intro": "# Accessible Typography for UX and Brand Systems\n\nA curated repository containing the combined writings of The Readability Group in a single, structured source document on accessible typography for UX, brand, and design-system work.\n\nThis project is intended to support:\n\n- research and reference on typography accessibility\n- inclusive design and UX governance\n- brand-system decision-making\n- AI/LLM training and retrieval grounded in a clear editorial synthesis\n- LLM-based guidance for brand, communications, marketing, and publishing design\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["README.md", "AGENTS.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"} {"id": "README.md::accessible-typography-for-ux-and-brand-systems-notes", "title": "Notes", "text": "## Notes\n\nThis repository is a research and reference dataset, not a formal WCAG certification or a single authoritative standard. It should be used alongside current standards, organizational policy, and context-specific evaluation. The included `AGENTS.md` is a practical interpretive layer for AI-assisted design work, not a substitute for live user research, governance review, or legal/compliance advice.\n", "record_type": "orientation", "source_repository": "Double-FW/Accessible-Typography-for-UX-and-Brand-Systems", "source_path": "README.md", "source_commit": "b6f5dacf838a195552c7a39b3afcd3821a4f8759", "source_url": "https://github.com/Double-FW/Accessible-Typography-for-UX-and-Brand-Systems/blob/b6f5dacf838a195552c7a39b3afcd3821a4f8759/README.md", "source_start_line": 85, "source_end_line": 87, "source_document_sha256": "f404e743fa6eaf9f48227c12427cac0db80d89428007a5cba27407342aca2a90", "text_sha256": "08a53d9ef4bbe392ff6f9a8e9d12af619f78e0dea521f145b8ae652801a05ec4", "heading_path": ["Accessible Typography for UX and Brand Systems", "Notes"], "metadata_json": "{}", "declared_source_license": "not_declared_in_document_front_matter", "repository_license": "MIT", "source_status": "see_source", "applicable_source_license": "MIT", "source_attribution_json": "[]", "source_document_intro": "# Accessible Typography for UX and Brand Systems\n\nA curated repository containing the combined writings of The Readability Group in a single, structured source document on accessible typography for UX, brand, and design-system work.\n\nThis project is intended to support:\n\n- research and reference on typography accessibility\n- inclusive design and UX governance\n- brand-system decision-making\n- AI/LLM training and retrieval grounded in a clear editorial synthesis\n- LLM-based guidance for brand, communications, marketing, and publishing design\n\n", "required_context_sections": ["Accessible_Typography_for_UX_and_Brand_Systems.md#7-testing-typography-in-context", "Accessible_Typography_for_UX_and_Brand_Systems.md#8-governance-for-ux-brand-and-ai-systems", "Accessible_Typography_for_UX_and_Brand_Systems.md#source-and-interpretation-notes"], "dataset_version": "1.0.1", "source_commit_date": "2026-11-10", "language": "en-GB", "required_context_paths": ["README.md", "AGENTS.md", "Accessible_Typography_for_UX_and_Brand_Systems.md"], "review_status": "faithful_extraction_checked_not_font_testing_scientific_or_content_approval"}