new post

Gemfile.lock

@@ -1,8 +1,9 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (7.2.1)
+    activesupport (7.2.2)
       base64
+      benchmark (>= 0.3)
       bigdecimal
       concurrent-ruby (~> 1.0, >= 1.3.1)
       connection_pool (>= 2.2.5)
@@ -21,6 +22,7 @@ GEM
       httpclient (~> 2.8, >= 2.8.3)
       json (>= 1.5.1)
     base64 (0.2.0)
+    benchmark (0.3.0)
     bigdecimal (3.1.8)
     coffee-script (2.4.1)
       coffee-script-source
@@ -40,14 +42,14 @@ GEM
     ethon (0.16.0)
       ffi (>= 1.15.0)
     eventmachine (1.2.7)
-    execjs (2.9.1)
-    faraday (2.10.1)
-      faraday-net_http (>= 2.0, < 3.2)
+    execjs (2.10.0)
+    faraday (2.12.0)
+      faraday-net_http (>= 2.0, < 3.4)
+      json
       logger
-    faraday-net_http (3.1.1)
+    faraday-net_http (3.3.0)
       net-http
     ffi (1.17.0-arm64-darwin)
-    ffi (1.17.0-x86_64-linux-gnu)
     filesize (0.2.0)
     forwardable-extended (2.6.0)
     gemoji (4.1.0)
@@ -108,7 +110,7 @@ GEM
       nokogiri (>= 1.4)
     http_parser.rb (0.8.0)
     httpclient (2.8.3)
-    i18n (1.14.5)
+    i18n (1.14.6)
       concurrent-ruby (~> 1.0)
     jekyll (3.10.0)
       addressable (~> 2.4)
@@ -230,7 +232,7 @@ GEM
       gemoji (>= 3, < 5)
       html-pipeline (~> 2.2)
       jekyll (>= 3.0, < 5.0)
-    json (2.7.2)
+    json (2.7.5)
     kramdown (2.4.0)
       rexml
     kramdown-parser-gfm (1.1.0)
@@ -239,7 +241,7 @@ GEM
     listen (3.9.0)
       rb-fsevent (~> 0.10, >= 0.10.3)
       rb-inotify (~> 0.9, >= 0.9.10)
-    logger (1.6.0)
+    logger (1.6.1)
     mercenary (0.3.6)
     minima (2.5.1)
       jekyll (>= 3.5, < 5.0)
@@ -250,8 +252,6 @@ GEM
       uri
     nokogiri (1.16.7-arm64-darwin)
       racc (~> 1.4)
-    nokogiri (1.16.7-x86_64-linux)
-      racc (~> 1.4)
     octokit (4.25.1)
       faraday (>= 1, < 3)
       sawyer (~> 0.9)
@@ -263,8 +263,7 @@ GEM
     rb-fsevent (0.11.2)
     rb-inotify (0.11.1)
       ffi (~> 1.0)
-    rexml (3.3.6)
-      strscan
+    rexml (3.3.9)
     rouge (3.30.0)
     rubyzip (2.3.2)
     safe_yaml (1.0.5)
@@ -278,22 +277,19 @@ GEM
       faraday (>= 0.17.3, < 3)
     securerandom (0.3.1)
     simpleidn (0.2.3)
-    strscan (3.1.0)
     terminal-table (1.8.0)
       unicode-display_width (~> 1.1, >= 1.1.1)
     typhoeus (1.4.1)
       ethon (>= 0.9.0)
     tzinfo (2.0.6)
       concurrent-ruby (~> 1.0)
     unicode-display_width (1.8.0)
-    uri (0.13.0)
+    uri (0.13.1)
     verbal_expressions (0.1.5)
-    webrick (1.8.1)
+    webrick (1.9.0)
 
 PLATFORMS
-  arm64-darwin-21
   arm64-darwin-23
-  x86_64-linux
 
 DEPENDENCIES
   github-pages
@@ -305,4 +301,4 @@ DEPENDENCIES
   webrick
 
 BUNDLED WITH
-   2.4.13
+   2.4.22

_posts/2024/11/2024-11-03-strasberg-symposium-usability-and-design.md

@@ -0,0 +1,24 @@
+---
+title: "Symposium on Usability and Design in France in April 2025"
+permalink: /blog/strasberg-symposium-usability-and-design
+date: 2024-11-03
+categories:
+- academics-and-practitioners
+- technical-writing
+keywords: 
+rebrandly: https://idbwrtng.com/strasberg-symposium-usability-and-design
+description: "The University of Strasbourg, in collaboration with Louisiana Tech University, is holding a <a href='https://usability-conference.unistra.fr'>Symposium on Usability and Design</a> in France April 24-25, 2025. The focus is on 'Addressing Access and Accessibility Through Usability and Design: Ideas and Approaches for Web Communication, Technical Communication and Localization.'"
+---
+
+Here's a more detailed description of the symposium's focus:
+
+> ​As technologies and cultures change, the contexts in which individuals access and use information continually shift in new and often unexpected ways. Accordingly, what constitutes both usable designs and usability is also in a matter of access and accessibility. Such factors also shape usability practices in the interconnected files of technical communication and localization. We therefore need to continually review, reflect on, and – if needed – revise our approaches to understanding usability, technical communication, and localization to effectively address access and accessibility. Such processes should include regular examinations of how each field influences and is influenced by the others in relation to addressing access and accessibility in local, regional, and global contexts.
+
+You can [submit a proposal to present here](https://usability-conference.unistra.fr/call-for-proposals/). 
+
+Although AI isn't mentioned, in discussions about the future of technical communication I have with colleagues and other professionals, the consensus is that we're at at a crossroads in tech comm, in which we'll primarily be writing with machine consumption in mind and focused on the AI chat experience users have. In fact, one colleague argued that informational formats are evolving from websites to chat interfaces as the main way we get information. I have no idea if AI factors into this symposium, but it could. Topics about usability, accessibility, and design seem relevant to this trend.
+
+You can learn more about the symposium here: [https://usability-conference.unistra.fr/](https://usability-conference.unistra.fr/).
+
+{% include ads.html %}
+