DAF Town Hall Feb 2026 (#464)

Author: michael-n-cooper

astro/src/content/daf/town-hall.mdx

@@ -22,13 +22,11 @@ Please complete our [sign-up](https://forms.gle/gnPZYH8gKDui58jv9) form to recei
 <Section>
 ## Upcoming Town Hall
 
-The next Town Hall is scheduled for _11 December 2025_. Agenda:
+The next Town Hall is scheduled for _12 February 2026_. Agenda:
 
-1. Recap of previous town hall (5 min)
-2. Background on support needed (10 min)
-3. Examine the types of support needed (30 min)
-4. General discussion (10 min)
-5. Next town hall on 11 December (5 min)
+1. Recap of previous town hall
+1. [Individual abilities restructuring](https://accessiblecommunity-my.sharepoint.com/:w:/g/personal/rbmontgomery_accessiblecommunity_onmicrosoft_com/IQDshxCmGytOQrEiR5Iu68LjAU2B_UMasSPYXR76Iyl8mK0?e=K6fk3D) exploration
+1. Next town hall on 12 March
 
 </Section>
 <Section>
@@ -53,6 +51,35 @@ If you are interested in participating in or using this work in any way, please
 <Section>
 ## Previous Town Halls
 
+<details>
+<summary>8 January 2026</summary>
+
+Continuing discussion of [Support needed](https://github.com/michael-n-cooper/daf-data/wiki/Support) categories, the group decided the "Assistive Technology" should be renamed to "Adapt". Because "Avoid" is also an adaptation, it could merge with this. "Adjust" is also adaptation that would merge with this. From this discussion, the support needed categories might become:
+
+* Alternative
+* Adapt
+* Default
+
+Exploring some of the [background thinking](https://aihal-accessibility.com/articles/design-approaches-from-normal-curve), it was observed that the term "normal" is overloaded and that "statistical distribution" would be preferred. Also the statistical distribution is not the most precise model of reality, and it is important to find a good balance of precision and usefulness. It will be important for the framework to be clear about the validity of models it develops and uses. 
+
+Conversation moved on to ways to expand our reach across user groups. Accessibility itself includes consider adaptations of the individual such as physical therapy, wheelchairs, training, etc. This means there is a blurry line, both practically and ethically, between providing accessibility by changing the person vs by changing the content.
+
+A proposed basic problem description that the DAF seeks to address: "make it so any person can use any built object". This goal needs to be clear in communication about the framework. Ultimately, we want the framework to help us see beyond our local knowledge, to gain an overview of the broader problem and solution space we seek to address.
+
+</details>
+
+<details>
+<summary>11 December 2025</summary>
+
+Completing the walkthrough of the framework concepts, this town hall focused on the [support needed](https://github.com/michael-n-cooper/daf-data/wiki/Support) categories:
+
+* [Default](https://github.com/michael-n-cooper/daf-data/wiki/Default) - discussed implications of the term "default" and the nature of its position in accessibility space;
+* [Avoid](https://github.com/michael-n-cooper/daf-data/wiki/Avoid) - questioned whether it means avoiding or suppressing content, and whether that is just an adjustment.
+* [Assistive Technology](https://github.com/michael-n-cooper/daf-data/wiki/AssistiveTechnology) - explored the line between AT and inbuilt support features. A concern was raised that, unless AT is universally available, a model that allows AT as a solution will be biased against people without access to it. Gregg referenced an [alternate approach](https://drive.google.com/drive/u/1/folders/1M4aKIRkhi_WDUcL6meTkParVFeZuoD6d) to AT.
+
+[11 December recording and transcript](https://us06web.zoom.us/rec/share/VavyU616QNuZChh8H2lf5bs--6vB80zbxXXYEjmoFT_u45XybiZNU5Ed41uEhHom.14hNPfxcQ8dcNi70)
+</details>
+
 <details>
 <summary>13 November 2025</summary>