This is a valid RSS feed.
This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.
<rdf:RDF
line 628, column 4: (47 occurrences) [help]
</description>
^
line 827, column 0: (2 occurrences) [help]
line 837, column 0: (17 occurrences) [help]
line 864, column 0: (7 occurrences) [help]
<?xml version="1.0" encoding="utf-8"?>
<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dcq="http://purl.org/dc/terms/"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:admin="http://webns.net/mvcb/"
xmlns:cc="http://creativecommons.org/ns#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns="http://purl.org/rss/1.0/">
<channel rdf:about="https://jedi.org/blog/">
<title>Jedi's BLOG</title>
<link>https://jedi.org/blog/</link>
<description>Context makes sense</description>
<dc:language>zh-tw</dc:language>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2024-02-07T18:51:03+08:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=2.661" />
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<items>
<rdf:Seq> <rdf:li rdf:resource="https://jedi.org/blog/archives/006419.html" />
<rdf:li rdf:resource="https://jedi.org/blog/archives/006418.html" />
<rdf:li rdf:resource="https://jedi.org/blog/archives/006417.html" />
<rdf:li rdf:resource="https://jedi.org/blog/archives/006416.html" />
<rdf:li rdf:resource="https://jedi.org/blog/archives/006415.html" />
<rdf:li rdf:resource="https://jedi.org/blog/archives/006414.html" />
<rdf:li rdf:resource="https://jedi.org/blog/archives/006413.html" />
<rdf:li rdf:resource="https://jedi.org/blog/archives/006412.html" />
<rdf:li rdf:resource="https://jedi.org/blog/archives/006411.html" />
<rdf:li rdf:resource="https://jedi.org/blog/archives/006410.html" />
<rdf:li rdf:resource="https://jedi.org/blog/archives/006409.html" />
<rdf:li rdf:resource="https://jedi.org/blog/archives/006408.html" />
<rdf:li rdf:resource="https://jedi.org/blog/archives/006407.html" />
<rdf:li rdf:resource="https://jedi.org/blog/archives/006406.html" />
<rdf:li rdf:resource="https://jedi.org/blog/archives/006405.html" />
</rdf:Seq>
</items>
</channel>
<item rdf:about="https://jedi.org/blog/archives/006419.html">
<title>ISO 9999:2022 的聽覺輔具及相關輔具變動</title>
<link>https://jedi.org/blog/archives/006419.html</link>
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<description>
<![CDATA[<p>大約六年前我曾經詳列 <a href="https://jedi.org/blog/archives/006209.html" title="CNS 15390 與 ISO 9999(系列之二)| Jedi's BLOG">ISO 9999:2016 的聽覺輔具及相關輔具變動</a>,以及 <a href="https://jedi.org/blog/archives/006214.html" title="CNS 15390 與 ISO 9999(系列總結)| Jedi's BLOG">CNS 15390 的種種嚴重錯誤</a>,實際執行 CNS 15390 翻譯工作的<a href="https://newrepat.sfaa.gov.tw/repat-catrap" rel="nofollow" title="首頁|多功能輔具資源整合推廣中心-衛生福利部社會及家庭署">多功能輔具中心</a>當時還跟我說正在著手更新,結果這些年過去,CNS 15390 依然不變,ISO 9999 倒是已經推進到 2022 年的第七版。</p>
<p>ISO 9999:2022 跟 ISO 9999:2016 之間的變化幅度相當大,我在本文針對聽覺輔具及相關輔具的部份,也就是 ISO 9999:2016 的 <code>04 27 15</code>、<code>05 03 03</code>、<code>05 06</code>、<code>06 30 24</code>、<code>09 06 09</code>、<code>22 06</code>、<code>22 18</code>、<code>22 24</code>、<code>22 27</code>、<code>22 33</code>、<code>27 03 09</code>、<code>27 06 27</code>、<code>28 24 03</code>、<code>28 24 15</code> 等分類代碼,比較這兩個版本間的異同。</p>]]>
<![CDATA[<hr>
<dl>
<dt id="042715">分類代碼 04 27 15</dt>
<dd>ISO 9999:2022 改編至分類代碼 <code>04 28 06</code></dd>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>(<code>04 27 15</code>) Sound stimulators<ul>
<li>Devices to mask the auditory perception of noise produced from within the ear or from external sources</li>
<li>Included are, e.g. tinnitus masks.</li>
<li>Assistive products for hearing, see 22 06</li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd>(<code>04 28 06</code>) Assistive products for stimulating senses with sound<ul>
<li>Assistive products for sound therapy and stimulation of senses with sound waves</li>
<li>Included are, e.g. tinnitus masks.</li>
<li>Assistive products for hearing, see 22 06</li></ul></dd>
</dl></dd>
</dl>
<p>近十年來的耳鳴處遇策略早已不是「遮蔽」,而是搭配聲音治療 (sound therapy) 的技術。原本 <code>04 27</code> 在 ISO 9999:2016 是刺激器 (stimulators),到了 ISO 9999:2022 調整為目的很特定的「治療細胞或組織層級的刺激器」(stimulators for treatment on cellular and tissue level),因此刪除 <code>04 27 15</code>,改編列到這一版新增的 <code>04 28</code>「刺激感官的輔具產品」(assistive products for stimulating senses) 底下,並且大幅調整描述,首次寫出「聲音治療」的輔具用途。</p>
<hr>
<dl>
<dt id="050303">分類代碼 05 03 03</dt>
<dd>ISO 9999:2022 改編至分類代碼 <code>22 09 12</code></dd>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>(<code>05 03 03</code>) Assistive products for voice training and speech training<ul>
<li>Products for training and developing the use of voice and speech, particularly in relation to the production and awareness of sounds</li>
<li>Included are, e.g. assistive products for training spoken language, S-, F- and Sch-indicators, acoustic spectral analysers.</li>
<li>Assistive products for mother tongue training, see 05 18 03</li>
<li>Assistive products for foreign language training, see 05 18 06</li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd>(<code>22 09 12</code>) Assistive products for voice training and speech training<ul>
<li>Products for training and developing the use of voice and speech, particularly in relation to the production and awareness of sounds</li>
<li>Included are, e.g. assistive products for training spoken language, S-, F- and Sch-indicators, acoustic spectral analysers.</li></ul></dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 刪除整個 <code>05</code>「教育及技能訓練輔具產品」(assistive products for education and for training in skills) 類別,底下各細類進行重編、整併、刪除,其中 <code>05 03 03</code> 重編到 <code>22 09</code>「音聲及言語功能輔具產品」(assistive products for voice and speech functions) 底下,且不再區分母語訓練、外語訓練等主要使用目的。</p>
<hr>
<dl>
<dt id="050603">分類代碼 05 06 03</dt>
<dd>ISO 9999:2022 改編至分類代碼 <code>22 21 18</code></dd>
<dd lang="en">Assistive products for training in finger spelling<ul>
<li>Products for training in, and learning, finger spelling, i.e. tactile communication for deaf blind persons</li></ul></dd>
<dt id="050606">分類代碼 05 06 06</dt>
<dd>ISO 9999:2022 改編至分類代碼 <code>22 21 21</code></dd>
<dd lang="en">Assistive products for training in sign language<ul>
<li>Products for training in, and learning, sign languages, i.e. visual languages for deaf persons</li></ul></dd>
<dt id="050609">分類代碼 05 06 09</dt>
<dd>ISO 9999:2022 改編至分類代碼 <code>22 21 24</code></dd>
<dd lang="en">Assistive products for training in lip-reading<ul>
<li>Products for training in, and learning, lip-reading</li>
<li>Included are, e.g. assistive products for training deaf and hard of hearing persons to understand what other persons say by watching the movement of their lips.</li></ul></dd>
<dt id="050612">分類代碼 05 06 12</dt>
<dd>ISO 9999:2022 改編至分類代碼 <code>22 21 27</code></dd>
<Dd lang="en">Assistive products for training in cued speech<ul>
<li>Products for training and learning vocal language supplemented by signing</li></ul></dd>
</dl>
<p>ISO 9999:2022 刪除整個 <code>05</code>「教育及技能訓練輔具產品」(assistive products for education and for training in skills) 類別,底下各細類進行重編、整併、刪除,其中 <code>05 06 03</code>~<code>05 06 12</code> 重編到 <code>22 21</code>「面對面溝通輔具產品」(assistive products for face-to-face communication) 底下,內容則未修改。</p>
<hr>
<dl>
<dt id="2206">分類代碼 22 06</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Assistive products for hearing<ul>
<li>Devices for concentrating, amplifying and modulating sound for a person with hearing problems</li>
<li>Included are, e.g. hearing aids with built-in tinnitus masking, induction coil devices.</li>
<li>Sound stimulators, see 04 27 15</li>
<li>Induction loop devices, see 22 18 30</li></li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd>Assistive products for hearing<ul>
<li>Devices for concentrating, amplifying, modulating and transmitting sound for a person with hearing problems</li>
<li>Included are, e.g. hearing aids with built-in tinnitus masking.</li>
<li>Assistive products for stimulating senses with sound, see 04 28 06</li></ul></dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 在聽覺輔具產品的定義多加上「傳輸聲音」(transmitting sound) 這一項,因而不再排除感應線圈裝置 (induction loop devices) 產品;早先在 ISO 9999:2016 的分類方式讓人混淆,把一整套感應線圈系統拆成發射訊號的線圈部分 (induction loop devices) 及接收訊號的線圈部分 (induction coil devices) 分成兩類,現在以 ISO 9999:2022 的分類方式就能歸類在一起了。除此之外,這裡也可以看到 <a href="#042715">04 27 15</a> 重新分類到 <code>04 28 06</code>。</p>
<hr>
<dl>
<dt id="220606">分類代碼 22 06 06</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Body-worn hearing aids<ul>
<li>Devices worn attached to the person's clothes or hanging around her/his neck for amplifying sound</li></li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd>Hearing amplifiers<ul>
<li>Devices placed on or nearby the person’s body for amplifying surrounding sound or for increasing the volume of one or more persons’ voices</li>
<li>Included are, e.g. communication amplifiers.</li></ul></dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 在這個分類做出相當激烈的改變:不再把體配型助聽器視為「助聽器」,而是把這類輔具跟各種體配型態的輔聽器統稱為「擴聽器」,配戴方式也以更寬鬆的方式來描述,不再明示衣服或頸部,改為放在身體上或身體附近都算符合。</p>
<hr>
<dl>
<dt id="220625">分類代碼 22 06 25</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd lang="zh-Hant-TW">(無此分類)</dd>
<dt>ISO 9999:2022</dt>
<dd>Sound transmission systems for hearing aids<ul>
<li>Devices for transmitting sound between source and hearing aid</li>
<li>Included are induction loop systems, induction loop amplifiers, radio frequency (FM) transmission systems, infrared (IR) systems and streaming systems</li></ul></dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 新增這個分類,把所有<a href="https://jedi.org/blog/archives/006260.html" title="各廠牌助聽器無線配件功能比較 | Jedi's BLOG">搭配助聽器使用的聲音傳輸配件</a>及系統通通涵括在內,包括線圈系統、調頻輔具、紅外線系統、串流系統等等,用於雙對側傳聲型助聽器的<a href="https://jedi.org/blog/archives/006418.html" title="雙對側傳聲型助聽器無線收音麥克風設備產品 | Jedi's BLOG">無線收音麥克風設備</a>也符合此分類的定義。請注意這類輔具的要件是主要功能為搭配助聽器使用。</p>
<hr>
<dl>
<dt id="220627">分類代碼 22 06 27</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Accessories for assistive products for hearing<ul>
<li>Included are, e.g. audio connections, spectacle adaptations, remote controls for hearing aids, software, batteries, rechargeable batteries, battery chargers.</li></li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd>Accessories for assistive products for hearing<ul>
<li>Included are, e.g. audio connections, spectacle adaptations, remote controls for hearing aids, software, special purpose batteries, rechargeable batteries, battery chargers.</li></ul></dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 在這個分類的變動是把「電池」修改成「用於特殊目的的電池」(special purpose batteries),因此排除常規使用的電池。舉例來說,有些人工電子耳語言處理器在搭配調頻輔具使用的情況,需要更換使用大電流規格的專用電池,這種專用電池即屬於本類,但平常使用的電池則不是。</p>
<hr>
<dl>
<dt id="2218">分類代碼 22 18</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Assistive products that record, play and display audio and visual information<ul>
<li>Devices that record or deliver information in audio or visual formats and products that combine any of those functions</li>
<li>Included are, e.g. audio and video equipment, televisions, sound transmission systems, products that process audio or visual information to enhance its quality and usefulness, such as filtering noises or converting analog to digital information.</li>
<li>Headphones, see 22 18 38</li>
<li>Visual computer displays and accessories, see 22 39 04</li></li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd>Assistive products that record, play and display audio and visual information<ul>
<li>Devices that record or deliver information in audio or visual formats and products that combine any of those functions</li>
<li>Included are, e.g. audio and video equipment, televisions, sound transmission systems, products that process audio or visual information to enhance its quality and usefulness, such as filtering noises or converting analogue to digital information.</li>
<li>Visual displays, see 22 39 04</li></ul></dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 在這類的修改屬於編輯性修訂,例如把 <samp>analog</samp> 改為 <samp>analogue</samp>,以及把已經併入子類別的耳機 (headphones) 略去(之前在 ISO 9999:2007 編在 <code>22 06</code> 底下,但從 ISO 9999:2016 起已經編入 <code>22 18</code>,只不過 ISO 9999:2016 漏掉沒處理完整),沒有實際的變化。</p>
<hr>
<dl>
<dt id="221803">分類代碼 22 18 03</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Sound recording and playing devices<ul>
<li>Devices for recording and playback of sounds</li>
<li>Included are, e.g. reel-to-reel and all types of tape recorders, index tone generators, demagnetizers, digital audio playback and recording devices such as minidiscs, CD players and DAISY players.</li></li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd>Sound recording and playing devices<ul>
<li>Devices for recording and playback of sound, e.g. dictaphones and music players</li>
<li>DAISY players and e-book readers, see 22 13 21</li></ul></dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 調整了這個分類的說明及範例,比較大的變化是把 DAISY 播放器及其他(有聲)電子書閱讀器分出去另外成為 <code>22 13 21</code>。</p>
<hr>
<dl>
<dt id="221806">分類代碼 22 18 06</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Video recording and playing devices<ul>
<li>Devices for saving and playing visual images and motion pictures on tape or other electronic media</li>
<li>Included are, e.g. cameras, video players, digital video recorders and players.</li></li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd>Video recording and playing devices<ul>
<li>Devices for saving and playing visual images and motion pictures on tape or other electronic media</li>
<li>Included are, e.g. cameras and projectors.</li></ul></dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 調整了此分類的範例,明確納入「投影機」(projectors) 產品。</p>
<hr>
<dl>
<dt id="221809">分類代碼 22 18 09</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Radio receivers<ul>
<li>Included are, e.g. radio sets.</li></li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd>Radio receivers<ul>
<li>Included are, e.g. radio receivers with audio display.</li></ul></dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 調整了此分類的範例,這個範例有點微妙,「audio display」指的應該是把聲音內容以視覺化方式呈現出來的顯示效果,大概是要表達即使這類收音機附有視覺化效果顯示螢幕,但是主要功能還是在於接收射頻訊號的輔具,而不是「把聲音轉換成視覺刺激」的輔具。</p>
<hr>
<dl>
<dt id="221818">分類代碼 22 18 18</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Closed-circuit television systems<ul>
<li>Closed systems for transmitting images with a camera to a recorder or direct displaying in a remote location</li>
<li>Image-enlarging video systems, see 22 03 18</li>
<li>Monitoring and positioning systems, see 22 27 24</li></li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd>Closed-circuit television systems<ul>
<li>Closed systems for transmitting images with a camera to a recorder or direct displaying in a remote location</li>
<li>Image-enlarging system, see 22 03 18</li>
<li>Localization and tracking systems, see 22 29 12</li></ul></dd>
</dl></dd>
</dl>
<p>這個分類本身沒有變化,改變的是 ISO 9999:2022 把 <code>22 27 24</code> 改編到 <code>22 29 12</code> 並調整名稱及內容。</p>
<hr>
<dl>
<dt id="221824">分類代碼 22 18 24</dt>
<dd>ISO 9999:2022 部分併入至分類代碼 <a href="#220625">22 06 25</a></dd>
<dt id="221827">分類代碼 22 18 27</dt>
<dd>ISO 9999:2022 部分併入至分類代碼 <a href="#220625">22 06 25</a></dd>
<dt id="221830">分類代碼 22 18 30</dt>
<dd>ISO 9999:2022 部分併入至分類代碼 <a href="#220625">22 06 25</a></dd>
</dl>
<p>ISO 9999:2016 中的這三個分類 (Radio frequency transmission systems, Infrared (IR) systems for audio information, Induction loop devices),如果用於搭配助聽器,就併入 ISO 9999:2022 的 <a href="#220625">22 06 25</a>,否則就刪除,亦即不再將其他用途的設備視為輔具。</p>
<hr>
<dl>
<dt id="221838">分類代碼 22 18 38</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Headphones<ul>
<li>Included are, e.g. devices that increase the volume of TVs, radios, stereos or are used together with communication amplifiers.</li>
<li>Assistive products that record, play and display audio and visual information, see 22 18</li></li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd>Headphones, earphones and headsets<ul>
<li>Head-worn loudspeakers placed nearby or inside the ear</li>
<li>Included are, e.g. devices that increase the volume of TVs, radios, stereos or are used together with communication amplifiers.</li></ul></dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 把這個分類擴充到包含入耳式耳機、耳麥組等類型的產品,給出一個較明確的定義,並且酌做編輯修訂:耳機在 ISO 9999:2007 編在 <code>22 06 24</code>,從 ISO 9999:2016 已經改編到 <code>22 18</code> 底下,相關的編輯沒處理完整,所以 ISO 9999:2022 加以修訂。</p>
<hr>
<dl>
<dt id="2224">分類代碼 22 24</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Assistive products for telephoning and telematic messaging</dd>
<dt>ISO 9999:2022</dt>
<dd>Assistive products for distant communication<ul>
<li>Assistive products for telecommunication and electronic network communication</li>
<li>Included are products primarily used for distance communication, but with options for face-to-face communication.</li>
<li>Assistive products for face-to-face communication, see 22 21</li></ul></dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 不再使用「電話使用」(telephoning)、「遠距通信傳訊」(telematic messaging) 這種說法,改用更符合時代演變的廣義統稱為「遠距溝通」(distant communication) 來描述,定義包括主要用途為遠距溝通的電訊 (telecommunication) 及電子網路通訊 (electronic network communication) 產品,無論是否兼具面對面溝通的輔助功能,皆屬於這個分類。</p>
<hr>
<dl>
<dt id="222403">分類代碼 22 24 03</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Standard network telephones<ul>
<li>Included are, e.g. stationary telephones with or without portable receivers, loudspeakers, visual telephones, videophones, telex and telefax machines, telephones with built-in warning signals, internet telephones, tactile telephones.</li>
<li>Assistive products for hearing, see 22 06</li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd lang="zh-Hant-TW">(部分打散重編至 <a href="#222404">22 24 04</a>、<a href="#222405">22 24 05</a>、<a href="#222407">22 24 07</a>,部分刪除)</dd>
</dl></dd>
<dt id="222404">分類代碼 22 24 04</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd lang="zh-Hant-TW">(無此分類)</dd>
<dt>ISO 9999:2022</dt>
<dd>Multifunctional communication systems<ul>
<li>Devices that combine speech, text, images and video communication</li>
<li>Included are, e.g. smartphones, telephone conference system, videophones.</li>
<li>Assistive products for hearing, see 22 06</li></ul></dd>
</dl></dd>
<dt id="222405">分類代碼 22 24 05</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd lang="zh-Hant-TW">(無此分類)</dd>
<dt>ISO 9999:2022</dt>
<dd>Telex and telefax machines</dd>
</dl></dd>
<dt id="222406">分類代碼 22 24 06</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Telephones for mobile networks<ul>
<li>Included are, e.g. car telephones, portable short-range telephones, hands-free models, camera-equipped models.</li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd lang="zh-Hant-TW">(部分打散重編至 <a href="#222404">22 24 04</a>、<a href="#222405">22 24 05</a>、<a href="#222407">22 24 07</a>,部分刪除)</dd>
</dl></dd>
<dt id="222407">分類代碼 22 24 07</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd lang="zh-Hant-TW">(無此分類)</dd>
<dt>ISO 9999:2022</dt>
<dd>Devices mainly for speech communication<ul>
<li>Included are, e.g. stationary telephones with or without portable receivers, mobile phones, internet telephones, tactile telephones, hand-free models.</li></ul></dd>
</dl></dd>
<dt id="222409">分類代碼 22 24 09</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Devices and software for real-time text communication<ul>
<li>Included are, e.g. mobile text telephones, devices and software for real-time text conversion, telephones with Braille input/output.</li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd lang="zh-Hant-TW">(部分打散重編至 <a href="#222404">22 24 04</a>、<a href="#222405">22 24 05</a>、<a href="#222407">22 24 07</a>,部分刪除)</dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 不再以標準網絡 (standard network) 或行動網絡 (mobile networks) 來區分電話,而是以「主要用途」來區分:</p>
<ul>
<li>具備多種(語音、文字、圖像、視訊)溝通模式的一律編到 <code>22 24 04</code>,包括智慧型手機 (smartphones)、電話會議系統 (telephone conference system)、視訊電話 (videophones) 等。</li>
<li>以口語交談溝通為主要用途的則編到 <code>22 24 07</code>,包括功能型手機 (mobile phones)、網際網路電話 (internet telephones)、觸覺電話 (tactile telephones) 等。</li>
<li>電傳打字機 (telex) 及傳真機 (telefax) 共同編到 <code>22 24 05</code>,這一類的共通點是溝通雙方都不使用口語交談。</li>
</ul>
<p class="pre">請注意:在 ISO 9999:2022 當中,「智慧型手機」同時存在於 <code>22 24 04</code> 及 <code>22 33 06</code> 兩個分類,但是附錄索引中僅指向 <code>22 24 04</code>,也許到了下一個版本會針對這個情況再做調整。</p>
<hr>
<dl>
<dt id="222415">分類代碼 22 24 15</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Telephone answering machines</dd>
<dt>ISO 9999:2022</dt>
<dd lang="zh-Hant-TW">(刪除)</dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 不再把電話答錄機視為輔具產品。</p>
<hr>
<dl>
<dt id="222421">分類代碼 22 24 21</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Accessories for telephoning<ul>
<li>Included are, e.g. connection units and signal transformers of an incoming message, keyboards for mobile phones, number presentation assistive products, dialling, engaged and ring tone indicators, dialling assistive products, receiver holders, receiver amplifiers.</li>
<li>Assistive products for hearing, see 22 06</li>
<li>Assistive products to assist or replace arm function, hand function, finger function or combination of these functions, see 24 18</li>
<li>Assistive products for fixation, see 24 27</li></li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd>Accessories for assistive products for distant communication<ul>
<li>Included are, e.g. connecting units and signal transformers of an incoming message, keyboards for mobile phones, number presentation assistive products, receiver holders, receiver amplifiers.</li>
<li>Assistive products for hearing, see 22 06</li>
<li>Assistive products to assist or replace arm function, hand function, finger function or combination of these functions, see 24 18</li>
<li>Assistive products for fixation, see 24 27</li></ul></dd>
</dl></dd>
</dl>
<p>除了名稱依照 <a href="#2224">22 24</a> 一起調整,ISO 9999:2022 在這個分類中刪減幾個例項:撥號、接聽、鈴響指示器 (dialling, engaged and ring tone indicators) 及撥號輔具 (dialling assistive products),暗示著這幾項現在比較適合歸到 <code>22 06</code>、<code>24 18</code>、<code>24 27</code> 等分類。</p>
<hr>
<dl>
<dt id="222424">分類代碼 22 24 24</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Telecommunication and telematics software<ul>
<li>Software for verbal and visual communication between computers via the computer network</li>
<li>Included are, e.g. Internet Protocol (IP), Voice over Internet Protocol (VoIP) telephony (IP) software, teleconference software, internet-based video communication systems, apps to facilitate use of smartphones and tablets.</li>
<li>Face-to-face communication software, see 22 21 12</li></li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd>Software for distant communication<ul>
<li>Software for textual, verbal and visual communication between computers via the computer network</li>
<li>Included are, e.g. teleconference software, internet-based video communication systems, e-mail-software and instant messaging apps to facilitate use of smartphones and tablets.</li>
<li>Face-to-face communication software, see 22 21 12</li></ul></dd>
</dl></dd>
</dl>
<p>除了名稱依照 <a href="#2224">22 24</a> 一起調整,ISO 9999:2022 在這個分類擴充加入文字 (textual) 溝通的用途範圍,並且調整例項:網際網路協定 (Internet Protocol) 是個通訊協定而非輔具故刪除,網際網路電話 (VoIP) 應該編到 <a href="#222407">22 24 07</a> 故在此刪除,然後新增加電子郵件軟體 (e-mail-software) 及即時傳訊應用程式 (instant messaging apps),即透過電腦網路而在電腦之間進行文字溝通的輔具。</p>
<hr>
<dl>
<dt id="222427">分類代碼 22 24 27</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Intercoms<ul>
<li>Stand-alone electronic communication systems intended to facilitate a limited or private dialogue between two or more persons in different locations</li>
<li>Assistive products for alarming, indicating, reminding and signalling, see 22 27</li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd lang="zh-Hant-TW">(合併至 <a href="#222433">22 24 33</a>)</dd>
</dl></dd>
<dt id="222430">分類代碼 22 24 30</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Entry phones<ul>
<li>Included are, e.g. door entry systems with integrated door openers, entry phone amplifiers.</li>
<li>Assistive products for alarming, indicating, reminding and signalling, see 22 27</li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd lang="zh-Hant-TW">(合併至 <a href="#222433">22 24 33</a>)</dd>
</dl></dd>
<dt id="222433">分類代碼 22 24 33</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd lang="zh-Hant-TW">(無此分類)</dd>
<dt>ISO 9999:2022</dt>
<dd>Intercoms and entry phones<ul>
<li>Stand-alone electronic communication systems intended to facilitate a limited or private dialogue between two or more persons in different locations</li>
<li>Included are, e.g. door entry systems with integrated door openers, entry phone amplifiers.</li>
<li>Assistive products for signalling, alarming, monitoring, and identifying, see 22 29</li>
<li>Closed-circuit television systems, see 22 18 18</li></ul></dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 將原本的 <code>22 24 27</code> 及 <code>22 24 30</code> 合併成 <code>22 24 33</code>,除此之外沒有明顯的更動。另外可以注意到這裡也反映出 <code>22 27</code> 已經重編到 <code>22 29</code>,以及多列舉一個應區別分開的閉路電視系統 (closed-circuit television system)。</p>
<hr>
<dl>
<dt id="2227">分類代碼 22 27</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Assistive products for alarming, indicating, reminding and signalling</dd>
<dt>ISO 9999:2022</dt>
<dd lang="zh-Hant-TW">(拆分成 <a href="#2228">22 28</a> 及 <a href="#2229">22 29</a>)</dd>
</dl></dd>
<dt id="2228">分類代碼 22 28</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd lang="zh-Hant-TW">(無此分類)</dd>
<dt>ISO 9999:2022</dt>
<dd>Assistive products for managing time, memory, and planning<ul>
<li>Assistive products for indication and understanding of time, for planning, for supporting memory, attention and for structuring e.g. activities</li></ul></dd>
</dl></dd>
<dt id="2229">分類代碼 22 29</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd lang="zh-Hant-TW">(無此分類)</dd>
<dt>ISO 9999:2022</dt>
<dd>Assistive products for signalling, alarming and localization<ul>
<li>Assistive products for signalling, alarming, warning, localizing and tracking a person</li>
<li>Included are products for marking.</li></ul></dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 將原本的 <code>22 27</code> 拆成 <code>22 28</code> 及 <code>22 29</code>,其中跟聽覺功能障礙者生活較相關的大概是在 <code>22 29</code> 分類之中。</p>
<hr>
<dl>
<dt id="222704">分類代碼 22 27 04</dt>
<dd>ISO 9999:2022 改編至分類代碼 <code>22 29 03</code></dd>
<dd lang="en">Signalling devices<ul>
<li>Devices that transform a signal, e.g. from telephone, doorbell, babycall, to a visual, an acoustic or a mechanical output.</li></ul></dd>
</dl>
<p>本分類僅因應 ISO 9999:2022 將 <code>22 27</code> 拆成 <code>22 28</code> 及 <code>22 29</code> 而調整分類代碼,內容未變動。</p>
<hr>
<dl>
<dt id="22 27 21">分類代碼 22 27 21</dt>
<dd>ISO 9999:2022 改編至分類代碼 <code>22 29 09</code></dd>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>(<code>22 27 21</code>) Environmental emergency alarm systems<ul>
<li>Included are, e.g. fire alarms, smoke-detectors.</li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd>(<code>22 29 09</code>) Environmental emergency alarm systems<ul>
<li>Included are, e.g. fire alarms, smoke detectors, alarm systems with internal transmitter.</li></ul></dd>
</dl></dd>
</dl>
<p>本分類因應 ISO 9999:2022 將 <code>22 27</code> 拆成 <code>22 28</code> 及 <code>22 29</code> 而調整分類代碼,例項說明補增「具備內部發射器」(with internal transmitter) 文字,意思是指這個分類的輔具項目並不依賴其他設備或產品的警示信號。</p>
<hr>
<dl>
<dt id="223315">分類代碼 22 33 15</dt>
<dd><dl lang="en">
<dt>ISO 9999:2016</dt>
<dd>Browser software<ul>
<li>Included are, e.g. software for SMS, WAP and e-mail.</li>
<li>Face-to-face communication software, see 22 21 12</li>
<li>Office software and industrial software, see 28 21 12</li></li></ul></dd>
<dt>ISO 9999:2022</dt>
<dd>Browser software<ul>
<li>Included are, e.g. software for SMS, WAP and e-mail.</li>
<li>Office software and industrial software, see 28 21 12</li></ul></dd>
</dl></dd>
</dl>
<p>ISO 9999:2022 刪除這個分類中可能需要區別面對面溝通軟體的情況,除此之外沒有變更。</p>
<p class="pre">請注意:在 ISO 9999:2022 當中,「電子郵件軟體」同時存在於 <code>22 24 24</code> 及 <code>22 33 15</code> 兩個分類,也許到了下一個版本會針對這個情況再做調整。</p>
<hr>
<p>以下這些分類在 ISO 9999:2022 均未改變或調整,維持與 ISO 9999:2016 相同:</p>
<dl lang="en">
<dt id="063024">06 30 24</dt>
<dd>Aural prostheses</dd>
<dt id="090609">09 06 09</dt>
<dd>Assistive products for ear protection or hearing protection<ul>
<li>Assistive products for reducing noise, see 27 03 09</li></ul></dd>
<dt id="220603">22 06 03</dt>
<dd>Ear-trumpets<ul>
<li>Devices for concentrating and channelling sounds into the ear</li></ul></dd>
<dt id="220609">22 06 09</dt>
<dd>Spectacle hearing aids<ul>
<li>Frames of eyeglasses with built-in electronic devices to amplify sound</li></ul></dd>
<dt id="220612">22 06 12</dt>
<dd>In-the-ear hearing aids<ul>
<li>Devices worn within the ear to amplify sound</li>
<li>Included are, e.g. in-the-canal hearing aids.</li></ul></dd>
<dt id="220615">22 06 15</dt>
<dd>Behind-the-ear hearing aids<ul>
<li>Devices worn behind the ear to amplify sound</li>
<li>Included are, e.g. headband hearing aids.</li></ul></dd>
<dt id="220618">22 06 18</dt>
<dd>Tactile hearing aids<ul>
<li>Devices for receiving, amplifying and transforming sounds into tactile signals</li></ul></dd>
<dt id="220621">22 06 21</dt>
<dd>Hearing aids used in connection with implants<ul>
<li>Devices for assisting hearing by stimulating the receivers implanted, e.g. in the inner ear</li></ul></dd>
<dt id="221812">22 18 12</dt>
<dd>Two-way radios<ul>
<li>Devices for receiving and transmitting mainly one to one remote radio communication</li>
<li>Included are, e.g. Citizens Band (CB), Family Radio Services (FRS), General Mobile Radio Service (GMRS), marine radios.</li></ul></dd>
<dt id="221815">22 18 15</dt>
<dd>Televisions<ul>
<li>Included are, e.g. digital and high definition televisions.</li></ul></dd>
<dt id="221821">22 18 21</dt>
<dd>Decoders for video text and text television<ul>
<li>Devices for translating videotext into artificial speech and decoding spoken output to provide video captions</li>
<li>Excluded are speech recognition systems.</li></ul></dd>
<dt id="221833">22 18 33</dt>
<dd>Microphones<ul>
<li>Included are, e.g. headset microphones.</li></ul></dd>
<dt id="221836">22 18 36</dt>
<dd>Loudspeakers</dd>
<dt id="221839">22 18 39</dt>
<dd>Accessories for audio, video and visual systems</dd>
<dt id="222412">22 24 12</dt>
<dd>Telephone booths</dd>
<dt id="222418">22 24 18</dt>
<dd>Telephone switchboards<ul>
<li>Panels and boards of switches for controlling the operation of a telephone system</li></ul></dd>
<dt id="2233">22 33</dt>
<dd>Computers and terminals<ul>
<li>Office software and industrial software, see 28 21 12</li></ul></dd>
<dt id="223303">22 33 03</dt>
<dd>Desktop (non-portable) computers</dd>
<dt id="223306">22 33 06</dt>
<dd>Portable computers and personal digital assistants (PDA)<ul>
<li>Computers that can be powered with batteries and thus can be used anywhere</li>
<li>Included are, e.g. computers in combination with mobile phones such as smartphones.</li></ul></dd>
<dt id="223312">22 33 12</dt>
<dd>Operating software<ul>
<li>Office software and industrial software, see 28 21 12</li></ul></dd>
<dt id="270309">27 03 09</dt>
<dd>Assistive products for reducing noise<ul>
<li>Devices or materials that reduce or absorb noise</li>
<li>Included are, e.g. sound-absorbing materials.</li>
<li>Assistive products for noise reduction in workplaces, see 28 24 15</li></ul></dd>
<dt id="270627">27 06 27</dt>
<dd>Assistive products and tools for measuring sound levels<ul>
<li>Devices for measuring and indicating sound levels</li></ul></dd>
<dt id="282403">28 24 03</dt>
<dd>Personal protective equipment for workplaces<ul>
<li>Devices designed to be worn or held by an individual for protection against health and safety hazards</li>
<li>Included are, e.g. products for head protection, eye protection, hearing protection, hand protection, foot protection, airway protection and whole-body protection, safety boots, protective work clothing, work belts.</li>
<li>Foot orthoses, see 06 12 03</li>
<li>Clothes and shoes, see 09 03</li>
<li>Body-worn assistive products for body protection, see 09 06</li>
<li>Products for skin protection and skin cleaning, see 09 21</li></ul></dd>
<dt id="282415">28 24 15</dt>
<dd>Assistive products for noise reduction in workplaces<ul>
<li>Devices or materials that reduce or absorb noise at workplaces</li>
<li>Included are, e.g. sound-absorbing materials.</li>
<li>Assistive products for reducing noise, see 27 03 09</li></ul></dd>
</dl>]]>
</description>
<dc:subject>occupation</dc:subject>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2024-02-07T18:51:03+08:00</dc:date>
</item>
<item rdf:about="https://jedi.org/blog/archives/006418.html">
<title>雙對側傳聲型助聽器無線收音麥克風設備產品</title>
<link>https://jedi.org/blog/archives/006418.html</link>
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<description>
<![CDATA[<p><a href="https://jedi.org/blog/archives/006381.html" title="身心障礙者輔具費用補助辦法、輔具費用補助基準表修正 | Jedi's BLOG">現行</a>〈身心障礙者輔具費用補助基準表〉有一項叫「助聽器—雙對側傳聲型」的輔具(項次 85),也就是完整的 <a href="https://jedi.org/blog/archives/006314.html#bicros" title="BiCROS(雙對側傳聲助聽器)| 單側/非對稱聽損者聽覺輔具選項 | Jedi's BLOG">BiCROS</a> 系統,由兩個設備元件組合而成:一個進階型助聽器、一個無線收音麥克風設備。</p>
<p>什麼樣的產品才能符合「無線收音麥克風設備」呢?〈身心障礙者輔具費用補助基準表〉對於各種輔具產品的分類判定,有兩個重要的原則,是許多輔具廠商(有意或無意)忽略的;這兩個原則分別是:</p>
<dl>
<dt>依產品功能規格</dt>
<dd>輔具產品的分類,依照其「可以用來做什麼」來判別,而不是依照其「被用來做什麼」來判別。只要產品本身具備相對應的功能規格,無論實際適配階段是否運用到那些功能,都不影響輔具分類。</dd>
<dt>依主要使用目的</dt>
<dd>輔具產品的分類,要依照其主要目的來判定。舉例來說,iPhone 具備「把鏡頭拍攝到的東西放大後顯示於螢幕上」的功能,但這不是 iPhone 產品的主要使用目的,所以不能說 iPhone 是「攜帶式擴視機」。</dd>
<dd>因為這項原則,所有的產品最多只能歸到一個輔具類別,不可能某項產品同時是這一類輔具又是另一類輔具。</dd>
</dl>
<p>依照上述原則,「使用兩只助聽器搭配無線傳輸功能」的跨傳聆聽系統,並不符合「雙對側傳聲型助聽器」輔具產品,因為那是「兩只助聽器」而不是「一只助聽器及一只無線收音麥克風設備」。目前台灣市面上銷售的聽覺輔具產品中,我整理出 16 個廠牌共 71 個「無線收音麥克風設備」產品型號,可用來與相同廠牌的進階型助聽器組合成雙對側傳聲型助聽器系統。以下列出這些廠牌及產品型號,供同業參考。</p>]]>
<![CDATA[<p>目前已銷售「助聽器—雙對側傳聲型」產品的廠牌包括:</p>
<ul>
<li>Audibel</li>
<li>Audio Service</li>
<li>Beltone</li>
<li>Bernafon</li>
<li>Coselgi</li>
<li>MicroTech</li>
<li>NuEar</li>
<li>Oticon</li>
<li>Philips</li>
<li>Phonak</li>
<li>ReSound</li>
<li>Rexton</li>
<li>Signia</li>
<li>Sonic</li>
<li>Starkey</li>
<li>Widex</li>
</ul>
<p>上述廠牌用於雙對側傳聲型助聽器系統的「無線收音麥克風設備」產品型號包括:</p>
<ul>
<li>Audibel A4 iQ CROS</li>
<li>Audibel Via Edge AI/Via AI/Via RIC R CROS</li>
<li>Audibel Via Edge AI/Via AI/Via RIC 312 CROS</li>
<li>Audibel Via Edge AI/Via AI/Via BTE 13 CROS</li>
<li>Audibel Arc AI RIC R CROS</li>
<li>Audibel Arc AI RIC 312 CROS</li>
<li>Audibel Arc AI BTE 13 CROS</li>
<li>Audio Service CROS RIC G5</li>
<li>Audio Service CROS RIC LI-ION G5</li>
<li>Audio Service CROS QUIX G5</li>
<li>Audio Service CROS RIC G6</li>
<li>Audio Service CROS RIC Li-Ion G6</li>
<li>Audio Service CROS quiX G6</li>
<li>Audio Service CROS R Li 7</li>
<li>Audio Service CROS R S 7</li>
<li>Audio Service CROS SR Li 7</li>
<li>Audio Service CROS R Li 8</li>
<li>Audio Service CROS IF CIC Li 8</li>
<li>Beltone Serene CROS Transmitter</li>
<li>Bernafon CROS MNR T R</li>
<li>Coselgi CROS</li>
<li>MicroTech Summit iQ CROS System</li>
<li>MicroTech Esentia Edge AI/Esentia AI/Esentia RIC R CROS</li>
<li>MicroTech Esentia Edge AI/Esentia AI/Esentia RIC 312 CROS</li>
<li>MicroTech Esentia Edge AI/Esentia AI/Esentia BTE 13 CROS</li>
<li>MicroTech Envy AI RIC R CROS</li>
<li>MicroTech Envy AI RIC 312 CROS</li>
<li>MicroTech Envy AI BTE 13 CROS</li>
<li>NuEar NOW iQ CROS</li>
<li>NuEar Circa Edge AI/Circa AI/Circa RIC R CROS</li>
<li>NuEar Circa Edge AI/Circa AI/Circa RIC 312 CROS</li>
<li>NuEar Circa Edge AI/Circa AI/Circa BTE 13 CROS</li>
<li>NuEar Savant AI RIC R CROS</li>
<li>NuEar Savant AI RIC 312 CROS</li>
<li>NuEar Savant AI BTE 13 CROS</li>
<li>Oticon CROS PX miniRITE R</li>
<li>Oticon CROS miniRITE T</li>
<li>Philips HearLink CROS MNR T R</li>
<li>Phonak CROS</li>
<li>Phonak CROS B-13</li>
<li>Phonak CROS B-312</li>
<li>Phonak CROS B-R</li>
<li>Phonak CROS B Custom</li>
<li>Phonak CROS P-R</li>
<li>Phonak CROS P-13</li>
<li>ReSound Nexia CROS Transmitter</li>
<li>Rexton CROS inoX 8C</li>
<li>Rexton CROS Li RIC 8C</li>
<li>Rexton CROS RIC 8C</li>
<li>Signia CROS Pure</li>
<li>Signia CROS Pure 312 Nx</li>
<li>Signia CROS Pure Charge&Go Nx</li>
<li>Signia CROS Silk Nx</li>
<li>Signia CROS Pure 312 X</li>
<li>Signia CROS Pure Charge&Go X</li>
<li>Signia CROS Silk X</li>
<li>Signia CROS Pure 312 AX</li>
<li>Signia CROS Pure C&G AX</li>
<li>Signia CROS Styletto AX</li>
<li>Signia CROS Pure C&G IX</li>
<li>Signia CROS Silk C&G IX</li>
<li>Sonic CROS MNR T R</li>
<li>Starkey Muse iQ Power Plus BTE 13 CROS</li>
<li>Starkey Livio Edge AI/Livio AI/Livio RIC R CROS</li>
<li>Starkey Livio Edge AI/Livio AI/Livio RIC 312 CROS</li>
<li>Starkey Livio Edge AI/Livio AI/Livio BTE 13 CROS</li>
<li>Starkey Evolv AI RIC R CROS</li>
<li>Starkey Evolv AI RIC 312 CROS</li>
<li>Starkey Evolv AI BTE 13 CROS</li>
<li>Widex CROS-FA BTE</li>
<li>Widex CROS-FS BTE</li>
</ul>
<p>註:大家可以注意到這些產品的型號中都含有「CROS」,實務上大概可以放心這樣判斷:任何一組雙對側傳聲型助聽器的產品型號中,必定含有名稱包括 CROS 的設備元件。</p>]]>
</description>
<dc:subject>occupation</dc:subject>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2024-02-04T11:01:11+08:00</dc:date>
</item>
<item rdf:about="https://jedi.org/blog/archives/006417.html">
<title>Aurvana Ace 2</title>
<link>https://jedi.org/blog/archives/006417.html</link>
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<description>
<![CDATA[<p>本日入手 <a href="https://us.creative.com/p/headphones-headsets/creative-aurvana-ace-2" title="Creative Aurvana Ace 2 True Wireless In-ears with Bluetooth® LE Audio, aptX™ Lossless, and xMEMS Driver - Creative Labs (United States)">Creative Aurvana Ace 2</a> 耳機,市面上第一款採用 <a href="https://xmems.com/" title="xMEMS | The First Solid-State True MEMS Speaker">xMEMS</a> 微機電單體技術的耳機產品,頻率反應範圍是驚人的 5 Hz~40,000 Hz,採用 <a href="https://www.bluetooth.com/blog/new-core-specification-v5-3-feature-enhancements/" title="New Core Specification v5.3 Feature Enhancements | Bluetooth® Technology Website">Bluetooth 5.3</a>,支援 LC3 (<a href="https://www.bluetooth.com/learn-about-bluetooth/feature-enhancements/le-audio/" title="LE Audio | Bluetooth® Technology Website">LE Audio</a>), aptX Lossless, <a href="https://www.aptx.com/aptx-adaptive" title="Qualcomm® aptX™ Adaptive | Bluetooth Audio Codec Technology">aptX Adaptive</a> 等音訊編碼。</p>
<p><img alt="Creative Aurvana Ace 2 外盒特寫" src="https://jedi.org/blog/archives/creative.aurvana.ace.2-01.png" width="450" height="450" border="0"><br>
<img alt="Aurvana Ace 2 半透明充電艙特寫" src="https://jedi.org/blog/archives/creative.aurvana.ace.2-02.png" width="600" height="450" border="0"></p>]]>
<![CDATA[<p>Creative Aurvana Ace 2 並非單純只使用 xMEMS 單體,因為 xMEMS 的特性較適合表現高頻聲音,所以 Aurvana Ace 2 也搭配 10 ㎜ 動圈 (dynamic driver) 來涵蓋全音域。網路上可以找到有些人已經實測過這組耳機的頻率反應,例如 <a href="https://www.audiosciencereview.com/forum/index.php?threads/creative-aurvana-ace-2-review.50590/#post-1831925" title="Measurement by VSG | Creative Aurvana Ace 2 Review | Audio Science Review (ASR) Forum">VSG 的量測報告</a>或者 <a href="https://www.soundguys.com/creative-aurvana-ace-2-review-108668/" title="Creative Aurvana Ace 2 review - SoundGuys">SoundGuys 的評測報告</a>,結果完全對得起它標榜的規格,搭配 <a href="https://autoeq.app/" title="AutoEq">AutoEq</a> 所需調整的<a href="https://www.audiosciencereview.com/forum/index.php?threads/creative-aurvana-ace-2-review.50590/#post-1831976" title="Just two EQ filters required | Creative Aurvana Ace 2 Review | Audio Science Review (ASR) Forum">幅度</a>也很小,可見其先天體質優秀。以它的零售價格 (US$ 149.99) 來說,我覺得是非常值得入手的無線入耳式耳機產品。</p>
<p><img alt="Aurvana Ace 2 充電艙打開,露出兩只耳機的特寫" src="https://jedi.org/blog/archives/creative.aurvana.ace.2-03.png" width="800" height="450" border="0"><br>
<img alt="Aurvana Ace 2 耳機特寫" src="https://jedi.org/blog/archives/creative.aurvana.ace.2-04.png" width="800" height="450" border="0"></p>
<p>註:xMEMS 單體的另一項特色是相位失真低,這對於音質也很重要。另外,Creative Aurvana Ace 2 裡面使用的 xMEMS 單體其實是台積電代工製造的(想不到吧~)。</p>]]>
</description>
<dc:subject>desire</dc:subject>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2024-01-26T19:32:31+08:00</dc:date>
</item>
<item rdf:about="https://jedi.org/blog/archives/006416.html">
<title>Sony PlayStation Access Controller</title>
<link>https://jedi.org/blog/archives/006416.html</link>
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<description>
<![CDATA[<p><img alt="Sony PlayStation Access Controller 包裝外盒正面特寫" src="https://jedi.org/blog/archives/sony_access_controller_box-01.png" width="800" height="450" border="0"><br>
繼 <a href="https://jedi.org/blog/archives/006261.html" title="Microsoft Xbox Adaptive Controller(及配件)開箱記錄 | Jedi's BLOG">Xbox 適應性控制器</a>及 <a href="https://jedi.org/blog/archives/006277.html" title="HORI Flex Controller 彈性控制器 | Jedi's BLOG">Switch 彈性控制器</a>之後,我今天順利入手 <a href="https://www.playstation.com/zh-hant-tw/accessories/access-controller/" title="Access™ 控制器 | | PS5 的可自訂自適應控制器套件 | PlayStation (台灣)">PS5 主機專用 Access 控制器</a>(型號:<code>CFI-ZAC1</code>),也就是先前介紹過的<a href="https://jedi.org/blog/archives/006393.html" title="Sony 的適應性控制器專案 (Project Leonardo) | Jedi's BLOG">李奧納多專案</a>的正式成果產品。</p>
<p>有別於 Xbox 適應性控制器及 Switch 彈性控制器都沒有在台灣銷售,PS5 主機專用 Access 控制器是<strong>正式在<u class="pn">台灣</u>銷售的公司貨</strong>,該有的原廠周邊一年免費保固以及中文使用說明文件一應俱全,有興趣的讀者可以直接參考 Sony 官方部落格(中文)文章介紹:</p>
<ul>
<li><a href="https://blog.zh-hant.playstation.com/2023/12/05/20231205-accesscontroller/" title="Access 控制器入門指南 – PlayStation.Blog 繁體中文">Access 控制器入門指南</a></li>
<li><a href="https://blog.zh-hant.playstation.com/2023/10/16/20221016-accesscontroller/" title="深入瞭解 Access 控制器的開發過程,並搶先一睹其無障礙的包裝設計 – PlayStation.Blog 繁體中文">Access 控制器的開發過程及無障礙包裝設計</a></li>
</ul>]]>
<![CDATA[<p>既然 Sony 自己已經有很詳細的介紹,我若再寫些重複的內容就沒意思了,所以這次大概不會像先前那樣詳細寫開箱心得跟特寫,畢竟官方的照片更多更漂亮。另一個問題是我其實根本沒有 PS5 遊戲主機,還不知道這種情況下能夠怎麼發揮 Access 控制器;最近工作相當忙碌,大概最快要等到明年初才能設法抽空來研究,屆時若有心得再來分享。</p>
<p><img alt="包裝盒底面的照片顯示內容物的特寫,以及連往線上說明的 QR Code 二維條碼" src="https://jedi.org/blog/archives/sony_access_controller_box-02.png" width="800" height="450" border="0"><img alt="包裝盒側面標示 1 年免費保固、型號為 CFI-ZAC1,以及內容物:Access 控制器、USB 連接線、19 個按鈕帽、3 個操作桿帽、23 個按鈕帽圖標、說明書" src="https://jedi.org/blog/archives/sony_access_controller_box-03.png" width="350" height="400" border="0"><img alt="包裝盒側面標示對應機器為 PS5" src="https://jedi.org/blog/archives/sony_access_controller_box-04.png" width="350" height="400" border="0"></p>
<p>對了,Sony 的部落格提到有個可以搭配的 <a href="https://www.logitechg.com/en-us/products/gamepads/adaptive-gaming-kit-for-access-controller.943-001253.html" title="Adaptive Gaming Kit for Access™ Controller | Logitech G">Access 控制器專用的 Logitech G Adaptive Gaming Kit</a>,預計售價 79.99 美元,這組套件跟我先前入手的<a href="https://jedi.org/blog/archives/006262.html" title="Logitech Switch | Jedi's BLOG">羅技適應性遊戲套件</a>(售價 99.99 美元)價差 20 美元,除了內附的貼紙不同(PS5 跟 Xbox),東西<strong>規格都是一樣的</strong>,只是數量比較少:</p>
<dl>
<dt>小型按鈕</dt>
<dd>3 個 → 2 個</dd>
<dt>大型按鈕</dt>
<dd>3 個 → 2 個</dd>
<dt>壓力感應板機</dt>
<dd>2 個,沒少</dd>
<dt>輕觸開關</dt>
<dd>4 個 → 2 個</dd>
<dt>固定板</dt>
<dd>2 個 → 1 個,少了多折式的那個</dd>
<dt>按鈕貼紙</dt>
<dd>Xbox 式樣 → PS5 式樣</dd>
</dl>
<p>不確定羅技這一組「Access 控制器專用適應性遊戲套件」會不會跟著正式在<u class="pn">台灣</u>上市銷售,如果會的話,買來接 Xbox 適應性控制器、Switch 彈性控制器,甚至用來接<a href="https://jedi.org/blog/archives/006388.html" title="微軟適應性集線器及適應性按鈕功能介紹 | Jedi's BLOG">微軟適應性集線器</a>或 <a href="https://jedi.org/blog/archives/006282.html" title="AbleNet Blue2 特殊開關 | Jedi's BLOG">Blue2</a> 之類的特殊開關都很划算。</p>]]>
</description>
<dc:subject>desire</dc:subject>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2023-12-07T16:46:35+08:00</dc:date>
</item>
<item rdf:about="https://jedi.org/blog/archives/006415.html">
<title>運用行為模型及動機諮商工具以促進親和力</title>
<link>https://jedi.org/blog/archives/006415.html</link>
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<description>
<![CDATA[<p>稍早我跟隨設計制度總顧問<a href="https://muan.co/" title="Mu-An Chiou">邱慕安</a>的腳步,在<a href="https://international.gov-design.com/24hours/" title="International Design in Government: 24-hour Remote Conference 2023">國際政府設計 24 小時遠端研討會</a>上,分享 <a href="https://pdis.nat.gov.tw/" title="行政院公共數位創新空間">PDIS</a> 這一年來的經驗。</p>
<p>儘管我測試、演練了好幾輪,到我要開始的那一刻,瀏覽器硬生生地跳出異常、無法存取我的攝影鏡頭,最後我只能以投影片畫面搭配純語音的形式完成分享(我還忘記關閉鏡頭設備,整個分享期間都顯示著設備異常畫面,真是太糗了),處理瀏覽器期間也幸虧有慕安協助撐場,各位觀看重播時就會看到我有多糗,請多包容。</p>
<p>我分享的主題是「運用行為模型及動機諮商工具以促進親和力 <span lang="en">(Applying behavioral model and motivation toolkit to improve accessibility)</span>」,有興趣的朋友可以<a href="https://jedi.org/blog/archives/ABMAMTTIA.pptx" download="Applying behavioral model and motivation toolkit to improve accessibility.pptx" title="Applying behavioral model and motivation toolkit to improve accessibility.pptx, 137 KB">下載 PPTX 格式的簡報投影片</a>,我以 CC0 公眾授權方式,將這份簡報投影片貢獻至公眾領域。</p>
<p class="pre">這份投影片經過親和力檢查,所有的圖片或圖案均加上替代文字,確認過每一頁內的文件報讀順序正確合理,且所有文字內容與背景色彩均達到充分對比(部分文字以加框線的方式來提昇對比)。萬一使用上仍然遭遇障礙,敬請讓我知道。</p>
<p>投影片內容以及我的分享內容都是英文,這篇部落格則提供華語翻譯,讓更多人知道我分享了什麼。</p>]]>
<![CDATA[<p class="pre" lang="en"><img alt="Title slide: Applying behavioral model and motivation toolkit to improve accessibility" src="https://jedi.org/blog/archives/ABMAMTTIA-01.png" width="800" height="450" border="0"><br>
Hello everyone, I'm Mu-An's colleague, Jedi Lin, the Head of Accessibility Design in Public Digital Innovation Space. I'll share my experience about applying the behavioral model and motivation toolkit to improve accessibility in government agencies.</p>
<p>大家好,我是<u class="pn">慕安</u>的同事<u class="pn">林克寰</u>,在行政院公共數位創新空間 <span lang="en">(Public Digital Innovation Space, PDIS)</span> 擔任無障礙設計總顧問。我將分享如何運用行為模型及動機諮商工具,對政府機關促進親和力。</p>
<p class="pre" lang="en"><img alt="Slide: A bit of me" src="https://jedi.org/blog/archives/ABMAMTTIA-02.png" width="800" height="450" border="0" loading="lazy"><br>
I am a web accessibility consultant and audiologist for more than twenty years. My prior work experience is directly involved in Taiwan's social welfare, special education, and job accommodation for people with disabilities, from the practice level as a care-giver, to the policy level as a committee member and policy draft editor.</p>
<p>我從事網頁親和力顧問及聽力師工作超過二十年,直接參與過台灣身心障礙者的社會福利、特殊教育、職務再設計等領域,我擔任過第一線的服務提供者,直接在實務層級參與,也擔任過委員會成員及政策草案編輯,在政策層級參與。</p>
<p class="pre" lang="en"><img alt="Slide: Goal" src="https://jedi.org/blog/archives/ABMAMTTIA-03.png" width="800" height="450" border="0" loading="lazy"><br>
In PDIS, one of our goal is to change how government agencies behave so they can grow and sustain accessibility. We want accessibility to be the corner stone of our policies and culture.</p>
<p>我們在 PDIS 的目標包括要改變政府機關的行事方式,讓政府機關能夠生育滋養親和力。我們想要讓親和力成為我們的政策及文化基石。</p>
<p class="pre" lang="en"><img alt="Slide: Challenges" src="https://jedi.org/blog/archives/ABMAMTTIA-04.png" width="800" height="450" border="0" loading="lazy"><br>
We face many challenges. Government agencies don't always do what they claim. They may claim they value the participation of people with disabilities, yet practice segregation. For example, some agencies provide accessible service with very limited functionality compared to inaccessible ones. People with disabilities are forced to process transactions at the counter, in person, accompanied by someone without disabilities. These agencies see this as their success because they can "protect and serve" people with disabilities better. That's really bad. Some government agencies don't know what they are doing. When asking them what their website is built for, they literally reply they don't know, maybe their commander ordered one, or just because "everybody has one, we should too." They know nothing about who will use their services or how. We also see lots of conflicts inside these agencies. Every department has different preferences and priorities, and thinks the responsibility belongs to another department. Everyone in the agencies thinks they are doing their job well by the book and by the order. Anything beyond that is beyond them.</p>
<p>我們面臨到許多挑戰。政府機關不總是言行一致,例如政府機關可能宣稱注重身心障礙者參與,實際上卻實施隔離手段,像是有些政府機關提供的無障礙服務只包含非常有限的功能,更多功能只提供成有障礙的服務,導致身心障礙者往往被迫要在非身心障礙者陪伴下,親自臨櫃辦理事務。這些機關把這個情況視為成功而沾沾自喜,因為他們覺得如此可以提供身心障礙者更好的「保護及服務」。這真的很糟。</p>
<p>有些政府機關不知道自己在做什麼,當問到網站的設置目的,他們真的回答說不知道,或者說是長官指示要架設,或者「因為別人有,我們也要有」。這些政府機關對於哪些人會來使用他們的服務、怎麼使用皆一無所知。</p>
<p>我們也觀察到政府機關內經常有著眾多衝突矛盾。每個部門都有不同的偏好及優先考量,總是認為相關責任應該歸屬到其他部門;機關內的每個公務員都覺得自己依照行政規章及長官指示認真執行公務,除此之外都不是他們的權責範圍。</p>
<p class="pre" lang="en"><img alt="Slide: Idea" src="https://jedi.org/blog/archives/ABMAMTTIA-05.png" width="800" height="450" border="0" loading="lazy"><br>
What do I think? I can see these government agencies are organic. Just like humans. Humans don't always do what we claim. Humans don't always know what we are doing. We want a healthy life yet stay up late, or drink and eat too much, or never exercise. From my experience in healthcare practice, we have the knowledge and toolkits to facilitate people making positive behavior changes. I know how to help people treat their hearing loss with hearing aids, for instance. How can we apply these knowledge and toolkits to help government agencies treat their accessibility barrier?</p>
<p>我如何看待這一切呢?從我的眼光中,這些政府機關其實都是某種有機體,就跟人類一樣。人類不總是言行一致、不總是知道自己在做什麼,我們想要健康的生活,偏偏又經常熬夜、暴飲暴食、毫不運動。在我從事健康照護的工作經驗中,我們已經具備足夠的知識及工具,能夠協助大家做出正向行為改變,例如我很清楚知道怎麼幫助大家用助聽器來治療聽力損失。我們要怎麼運用這些知識及工具,幫助政府機關治療這些親和力阻礙?</p>
<p class="pre" lang="en"><img alt="Slide: COM-B model" src="https://jedi.org/blog/archives/ABMAMTTIA-06.png" width="800" height="450" border="0" loading="lazy"><br>
Let me introduce the COM-B model. The COM-B model is a behavioral model widely adopted in many areas, such as to form an exercise habit, to quit smoking, et cetera. This model illustrates that it takes Capability, Opportunity, and Motivation to perform a certain Behavior or behavior change. Please notice that Capability and Opportunity can improve Motivation too. For any government agency, Capability includes its funding, human resource, knowledge, and skills. Opportunity might be people's demand, study or news report event, higher policy issued or changed, even upcoming election. We can work on Capability and Opportunity, but in the end, it's Motivation that matters. After all, if the agency doesn't want to be helped, nothing we work on Capability and Opportunity works.</p>
<p>請讓我介紹 <dfn><span lang="en">COM-B</span> 行為模型</dfn>,這個模型被廣泛用於多個領域,例如用以養成運動習慣、戒菸等等。這個模型表示出任何人都需要有<mark>能力</mark> <span lang="en">(Capability)</span>、<mark>機會</mark> <span lang="en">(Opportunity)</span>、<mark>動機</mark> <span lang="en">(Motivation)</span> 才能進行特定的<mark>行為</mark> <span lang="en">(Behavior)</span> 或做出行為改變。請注意能力及機會也能促進動機。</p>
<p>對於任何政府機關,所謂的<dfn id="capability">能力</dfn>包括經費預算、人力資源、知識、技能等,而<dfn id="opportunity">機會</dfn>可能是民眾提出訴求、研究報告或新聞報導、高層政策實施或變動、即將發生的選舉等。我們可以設法增加能力及機會,但最終還是要看<em>動機</em>。畢竟,如果政府機關不希望獲得幫助,我們在能力及機會方面努力再多也沒用。</p>
<p class="pre" lang="en"><img alt="Slide: Person-Centered Care (PCC)" src="https://jedi.org/blog/archives/ABMAMTTIA-07.png" width="800" height="450" border="0" loading="lazy"><br>
The same problem exists in human too. In healthcare area, studies showed the most effective and reliable method is PCC, Person-Centered Care. In PCC practice, patients actively participate in their treatment in close cooperation with their health professionals. The PCC practice has four principles: The treatment is based on the unique person's needs. The treatment focuses on the abilities of the person and encourage activity. The treatment is coherent. Health professionals approach patients with dignity, compassion, and respect. Now, let's think of organic government agency as a person. We'd like to have the agency actively participate in its improvement plan in close cooperation with us. The plan shall be based on the unique agency's needs. The plan shall focus on the current Capability of the agency and encourage activity for known Opportunity. The plan shall mean something to the agency, echo its value, and contribute to its mission. We shall approach the agency with dignity, compassion, and respect. We have to learn its history, culture, politiics, and work with that. We don't plot the plan but facilitate the agency to make its own.</p>
<p>在人類身上也有同樣的困難。健康照護領域的研究指出,最有效且可靠的方式是實施<dfn>以人為本的照護服務 <span lang="en">(Person-Centered Care, PCC)</span></dfn>。在 PCC 的照護模式中,患者與健康照護專家緊密合作,積極參與自己的治療處遇計畫。PCC 照護模式有四項原則:</p>
<ul>
<li>應基於獨特個人的需求進行治療處遇</li>
<li>治療處遇應著重於個人的能力,並鼓勵活動</li>
<li>治療處遇應連貫一致</li>
<li>健康照護專家應以尊嚴、同情、尊重的態度對待患者</li>
</ul>
<p>現在讓我們把政府機關當成一個人。我們希望政府機關能跟我們緊密合作,積極參與自己的改善方案,這個改善方案應該基於獨特機關的需求來規畫實施,著重於機關現有的<a href="#capability">能力</a>,鼓勵對已知<a href="#opportunity">機會</a>進行活動;這個改善方案應對機關具有實質意義,能夠呼應機關的價值,促進機關達成使命。我們應該以尊嚴、同情、尊重的態度來對待政府機關,這表示我們需要學習各機關的歷史脈絡、文化、政治關係等,納入相關考量。我們不是要替政府機關規畫改善方案,而是要協助政府機關訂定自己的改善方案。</p>
<p class="pre" lang="en"><img alt="Slide: PCC techniques: the motivation toolkit" src="https://jedi.org/blog/archives/ABMAMTTIA-08.png" width="800" height="450" border="0" loading="lazy"><br>
As to Motivation, there is an available motivation toolkit in Person-Centered Care. The toolkit contains the Circle, the Line, and the Box. Let's see how to use them.</p>
<p>至於<em>動機</em>的部份,在 PCC 照護模式中有套動機諮商工具組可以運用,這套工具組包含:<a href="#circle">圓圈</a>、<a href="#line">線條</a>、<a href="#box">方格</a>。讓我們來看看這套工具組要怎麼派上用場。</p>
<p class="pre" lang="en"><img alt="Slide: The Circle" src="https://jedi.org/blog/archives/ABMAMTTIA-09.png" width="800" height="450" border="0" loading="lazy"><br>
The Circle illustrates the different phases of behavior change. The first phase is Contemplation, followed by Preparation, Action, Maintenance, and Relapse. Each phase leads to the next, forming a circle, with Maintenance phase may leading to Permanent Change if lucky. Before Contemplation, there is phase zero, Pre-contemplation. When we visit a certain government agency, we check which phase it is currently at. Then we can know how to provide help. Pre-contemplation, Contemplation, and Preparation phase belong to the Attitude Process. These three phases focus on attitude change. It's about IF and WHY; there is no need to rush action. Action, Maintenance, and Relapse phase belong to the Behavioral Process. These three phases focus on behavior change. It's about HOW and WHAT, about action and actual doing. Now, how do we know which phase a certain agency is at?</p>
<p><dfn id="circle">圓圈</dfn>是一個描繪行為改變階段的參考框架。從<a href="#contemplation">意圖期</a>開始,接下來是<a href="#preparation">準備期</a>、<a href="#action">行動期</a>、<a href="#maintenance">維持期</a>、<a href="#relapse">故態復萌</a>,每個階段推進至下一個階段,形成一個圓圈。如果幸運的話,<a href="#maintenance">維持期</a>也可能推進到<em>持久改變 (Permanent Change)</em> 階段。另外,在<a href="#contemplation">意圖期</a>前面還有個第零階段:<a href="#precontemplation">意圖前期</a>。</p>
<p>當我們與某個政府機關相遇的時候,我們會判斷這個機關目前處於改變的哪個階段,然後就能知道要如何提供協助。</p>
<p><a href="#precontemplation">意圖前期</a>、<a href="#contemplation">意圖期</a>、<a href="#preparation">準備期</a>屬於行為改變的<dfn>態度歷程 <span lang="en">(Attitude Process)</span></dfn>,這三個階段專注於態度的改變,著重於<em>是否要改變</em>以及<em>為什麼要改變</em>,沒有必要在這些階段催促著一定要做什麼行為不可。</p>
<p><a href="#action">行動期</a>、<a href="#maintenance">維持期</a>、<a href="#relapse">故態復萌</a>屬於行為改變的<dfn>行為歷程 <span lang="en">(Behavioral Process)</span></dfn>,這三個階段專注於行為的改變,著重於<em>如何改變</em>以及<em>改變什麼</em>,也就是行動跟作為的部份。</p>
<p>那麼,究竟我們要如何得知政府機關處於行為改變的哪個階段?</p>
<p class="pre" lang="en"><img alt="Slide: [Phase 0] Pre-contemplation" src="https://jedi.org/blog/archives/ABMAMTTIA-10.png" width="800" height="450" border="0" loading="lazy"><br>
If the agency says, "we don't have a problem," then we know there is a huge problem. This is phase zero, Pre-contemplation, where the agency doesn't have the idea at all. In this phase, we review the feedback from actual users with them, and explore the barriers of current services. Sometimes the barriers are so profound that no one can report the existence of the barriers. We show them how people use the web or services, let them be aware there are different users, have different abilities, challenges, and needs. We provide education and awareness in this phase. If the agency is aware their systems or services don't cover all the users, they move into the next phase.</p>
<p>如果政府機關宣稱「我們沒有問題」,那我們就知道問題嚴重了。這就是第零階段:<dfn>意圖前期 <span lang="en">(Pre-contemplation)</span></dfn> 的表現,處於這個階段的政府機關缺乏最基本的意圖。對於這個階段,我們會跟政府機關一起回顧系統實際使用者的真實回饋,探索現有服務所存在的各種障礙;有時候這些障礙之巨大,導致根本沒有人能夠回報障礙的存在。</p>
<p>我們會向政府機關展示大家如何使用網頁或政府服務,讓政府機關感知到有各式各樣不同的使用者,其能力、挑戰、需求各有不同。我們在這個階段提供教育及覺識,如果政府機關開始覺得自己的系統或服務尚無法涵蓋所有使用者,就能進入下一個階段。</p>
<p class="pre" lang="en"><img alt="Slide: [Phase 1] Contemplation" src="https://jedi.org/blog/archives/ABMAMTTIA-11.png" width="800" height="450" border="0" loading="lazy"><br>
Phase one, Contemplation, is when the agency says, "our service might need to be accessible." The agency in this phase is usually a bit confused. They have ambivalence on whether pursuing accessibility. We listen to them, provide information to explore, clearify, support, and enhance their experience. Then we use the next motivation tool, the Line, to explore their ambivalence and motivation.</p>
<p>處於第一階段,即<dfn id="contemplation">意圖期 <span lang="en">(Contemplation)</span></dfn>的政府機關,會表達「我們的服務可能需要親和易用。」處於這個階段的政府機關通常有點困惑,對於是否要追尋親和力感到躊躇猶豫。我們會聆聽這些機關的聲音,提供相關的資訊,協助機關深入探索、澄清、支持、增強他們的相關經驗,然後我們會利用<a href="#line">線條</a>工具,探索機關的內在矛盾及動機。</p>
<p class="pre" lang="en"><img alt="Slide: The Line" src="https://jedi.org/blog/archives/ABMAMTTIA-12.png" width="800" height="450" border="0" loading="lazy"><br>
The Line is actually a visual scale, scored from zero to ten, means not at all to very much. We ask two questions: How important is it for you to improve accessibility right now? and How much do you believe in your ability to be inclusive? We ask about the score and then why. We may continue to discuss the score with more information to come to a mutually satisfactory conclusion. If the first score is low, we explore the reason, including what other conditions may change the score. If the first score is high but the second score is low, we can provide information on how to improve their ability. If both scores are high, they usually move into the next phase.</p>
<p><dfn id="line">線條</dfn>工具其實就是個視覺量尺,從 0 分到 10 分,分別代表從「完全沒有」到「非常多」。我們會問兩個問題:</p>
<ol>
<li>貴機關覺得現在改善親和力有多重要?</li>
<li>貴機關對於自己包容友善的能力,有多少信心?</li>
</ol>
<p>我們詢問過機關自己給的分數後,接著追問為什麼是那個分數。我們可能提出更多資訊,接續討論這兩個問題的分數,直到我們跟機關雙方都對分數達成共識。如果第一題的分數很低,我們將探索低分的原因有哪些,包括是否有其他條件或因素可能在現在或將來會造成分數改變;如果第一題的分數很高,但第二題的分數很低,我們可以提供有哪些增強機關能力的資訊。如果兩題的分數都很高,通常機關就能進入下一個階段。</p>
<p class="pre" lang="en"><img alt="Slide: [Phase 2] Preparation" src="https://jedi.org/blog/archives/ABMAMTTIA-13.png" width="800" height="450" border="0" loading="lazy"><br>
When the agency determines their service needs to be accessible, they are in phase two, Preparation. In this phase, we can offer advice on possible strategies, guidelines, options, and steps. Usually, they will have many questions, for them, it's an exciting new journey ahead. Some agencies may continue to express ambivalence in this phase. This time, we can use the next motivation tool, the Box, to help them.</p>
<p>當政府機關確信其提供的服務應親和易用,就表示機關已經處於第二階段:<dfn>準備期 <span lang="en">(Preparation)</span></dfn>。在這個階段中,我們提供可能的策略、指引、選項、步驟等建議。通常處於這個階段的政府機關會拋出許多問題,對這些機關而言,即將展開興奮的嶄新旅程。有些機關在這個階段可能又冒出一些內在矛盾而顯得猶豫,這次我們要用<a href="#box">方格</a>動機諮商工具來協助機關。</p>
<p class="pre" lang="en"><img alt="Slide: The Box" src="https://jedi.org/blog/archives/ABMAMTTIA-14.png" width="800" height="450" border="0" loading="lazy"><br>
The Box contains four quadrants, with one question in each. Usually we focus on the first two questions, the latter two if there is time available. Through these questions, we help them explore the advantages and disadvantages of doing nothing at all, and taking action. We write these answers down, with their own words, usually by online collaboration tools such as Google Docs, then discuss and explore with them. Once they put their mind to taking action, they move into the next phase.</p>
<p><dfn id="box">方格</dfn>包含四個象限,每個象限裡有一條題目,通常我們先聚焦在前兩條題目,如果時間允許再進行後兩條。我們利用這些題目,協助政府機關探索「什麼都不做」的優點跟缺點,以及「做出改變」的優點跟缺點。我們會依照政府機關自己的話語把這幾條題目的回答寫下來,通常是利用 Google 文件等線上共筆工具讓彼此一起參與,然後再一起討論跟探索這些回答。一旦政府機關下定決心要做出改變,就能進入下一個階段。</p>
<p class="pre" lang="en"><img alt="Slide: [Phase 3] Action" src="https://jedi.org/blog/archives/ABMAMTTIA-15.png" width="800" height="450" border="0" loading="lazy"><br>
From phase three, Action, the Behavioral Process starts. We shall take their views and needs, develop a joint strategy with them to drive this accessibility journey. The important part of this phase is to encourage them by highlighting their benefits of improved accessibility. With positive reinforcement, they can grow accessibility and move into the next phase.</p>
<p>從第三個階段,即<dfn id="action">行動期 <span lang="en">(Action)</span></dfn>起,進入行為改變的行為歷程。我們應該考量政府機關的觀點及需求,一起合作發展出聯合策略,驅動這趟親和力旅程。這個階段的重點是要盡量彰顯親和力已經改善的部份確實帶來哪些效益,由此鼓勵政府機關;利用這種正向增強,政府機關就能孕育親和力茁壯,進入下一個階段。</p>
<p class="pre" lang="en"><img alt="Slide: [Phase 4] Maintenance" src="https://jedi.org/blog/archives/ABMAMTTIA-16.png" width="800" height="450" border="0" loading="lazy"><br>
In phase four, Maintenance, the agency acts as accessibility is a priority, and keeps doing so. We may ask how they are managing accessibility, share knowledge and information, answer their questions, provide furthur support. If they are ambivalent, then use the Box to explore their situation. Keep supporting them with positive reinforcement; they may achieve permanent change.</p>
<p>當政府機關處於第四個階段,即<dfn id="maintenance">維持期 <span lang="en">(Maintenance)</span></dfn>,可以看到其實際作為把親和力視為要件,並持續如此。我們可以詢問機關如何掌握親和力作為,彼此分享知識及資訊,回答機關進一步的提問、提供更深入的支持。萬一政府機關在這個階段流露出內在矛盾,還是可以回頭使用<a href="#box">方格</a>工具協助機關探索狀況如何。持續以正向增強提供支持,機關就有機會達到持久改變。</p>
<p class="pre" lang="en"><img alt="Slide: [Phase 5] Relapse" src="https://jedi.org/blog/archives/ABMAMTTIA-17.png" width="800" height="450" border="0" loading="lazy"><br>
Some agencies, however, after a period of Maintenance, feel "it's done already." In this Relapse phase, they stop taking action, and their motivation declines. Don't panic; let's listen to them and explore their positive experience with accessibility, remind them of all those good we have made and still can make. We shall use the Line and the Box again if they continue to express ambivalence. With our continued support, they can move into the Contemplation phase and start all over again.</p>
<p>然而,有些政府機關在一段<a href="#maintenance">維持期</a>之後,開始覺得「都做完了」,而開始<dfn>故態復萌 <span lang="en">(Relapse)</span></dfn>,停下親和力相關作為,動機逐漸衰退。遇到這樣的機關也別慌,我們需要傾聽機關訴說的經驗,從中探索親和力的正向體驗,提醒機關我們已經達成哪些效益,而且這些效益還能持續開創。如果機關仍然浮現更多內在矛盾,我們可以再回頭拿出<a href="#line">線條</a>及<a href="#box">方塊</a>工具,不要放棄,持續支持,機關可能再次進入<a href="#contemplation">意圖期</a>而重新踏上行為改變。</p>
<p class="pre" lang="en"><img alt="Slide: Where are we" src="https://jedi.org/blog/archives/ABMAMTTIA-18.png" width="800" height="450" border="0" loading="lazy"><br>
In this year, most government agencies we reviewed are at phase zero to two, all in the Attitude Process. It takes time for agencies to shape their idea and attitude. PDIS is not the magic wand. I can not wave my hand to make accessibility happen as in the Star Wars movies. PDIS is here, to empower Taiwan's government agencies, enrich our culture, and help Taiwan become more inclusive and accessible. May the Force be with us all.</p>
<p>我們在今年協助過的政府機關中,絕大多數都處於第零階段到第二階段,全部處於行為改變的態度歷程。政府機關需要相當的時間才能塑造出相關的認知及態度。PDIS 並不是什麼魔法杖,我也沒辦法像電影中的絕地武士那樣揮個手就讓親和力普及。PDIS 在此的意義與目的,是要賦權台灣的政府機關,豐富台灣的公部門文化,協助台灣更加包容友善。願原力與你我同在。</p>
<p class="pre">註:我在上述這段分享中,提到這些模型、工具、技巧借鏡健康照護領域,有興趣的夥伴不妨移駕我之前的另一篇文章《<a href="https://jedi.org/blog/archives/006383.html" title="在輔具中心提供以人為本的聽覺輔具服務
| Jedi's BLOG">在輔具中心提供以人為本的聽覺輔具服務</a>》,我寫了更多細節及技巧可供參考。</p>]]>
</description>
<dc:subject>typing</dc:subject>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2023-11-29T14:16:52+08:00</dc:date>
</item>
<item rdf:about="https://jedi.org/blog/archives/006414.html">
<title>就醫無礙標竿競賽</title>
<link>https://jedi.org/blog/archives/006414.html</link>
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<description>
<![CDATA[<p>衛福部公告<a href="https://www.mohw.gov.tw/cp-18-76765-1.html" title="公告 112 年就醫無礙標竿競賽 | 衛生福利部">就醫無礙標竿競賽</a>,參賽組別獎金最高 30 萬元新台幣,報名至 2023 年 12 月 29 日為止。</p>
<p>不過只有醫院及中、西、牙醫診所可以參加,聽力所跟其他治療所不行。</p>]]>
</description>
<dc:subject>twitter</dc:subject>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2023-11-28T16:38:20+08:00</dc:date>
</item>
<item rdf:about="https://jedi.org/blog/archives/006413.html">
<title>漁村符號輸入表格修改版</title>
<link>https://jedi.org/blog/archives/006413.html</link>
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<description>
<![CDATA[<p>漁村符號輸入法 (EHQ-Symbols Input Method) 是 <a href="https://zonble.net/" title="zonble - Da bin ich noch.">zonble</a>(楊維中)當年在工兵營營部的作品(這段故事寫在他的《防區狀況三生效-驗證精實案》<a href="https://zonble.github.io/zk3/16/#_12" title="16 消逝 | 防區狀況三生效-驗證精實案 2022 修訂版">第 16 章</a>),用來輸入<a href="http://eshensh.net/ez/csw/index.html" title="「中國海字集」修復版 | 輕鬆輸入法之家">中國海字集</a>的各種符號。隨著時代與科技發展,zonble 在 MacOS X 上面衍生出<a href="https://web.archive.org/web/20050325013817/http://rt.openfoundry.org:80/Foundry/Project/Wiki/177/index.html" title="漁村輸入法 X | OSSF | Internet Archive">漁村輸入法 X</a>,後來演變成輸入 Unicode 符號的 <mark>ehq.cin</mark> 表格(這段故事,以及漁村輸入的設計理念,寫在《<a href="https://osxchat.blogspot.com/2004/12/openvanilla.html" title="供 OpenVanilla 使用的漁村符號輸入法 | #osxchat blog">供 OpenVanilla 使用的漁村符號輸入法 </a>》),帶到 zonble 參與的 OpenVanilla、Yahoo! 奇摩輸入法等專案。</p>
<p>漁村符號輸入表格始終沒有自己的獨立專案,有的只是同好與好友間輾轉接手交替的檔案更新。<a href="https://lukhnos.org/" title="Lukhnos">Lukhnos</a>(劉燈)在《<a href="https://lukhnos.org/blog/zh/archives/337/index.html" title="輸入法,諸行無常 | Lukhnos">輸入法,諸行無常</a>》記錄到漁村輸入表格吸納 <a href="http://momizi.z6i.org/" title="Momizi's blog">Momizi</a> 的 <mark>iroha.cin</mark>(伊呂波)日文假名輸入表格(這段故事寫在《<a href="http://momizi.z6i.org/archives/005537.html" title="一株香草的成長─我所知道的 OV 故事 | Momizi's blog">一株香草的成長─我所知道的 OV 故事</a>》),成為「漁村符號及日文假名輸入表格」,即依附在 OpenVanilla 的 <a href="https://github.com/openvanilla/openvanilla/blob/master/DataTables/ehq-symbols.cin">ehq-symbols.cin</a>。</p>
<p>我在《<a href="https://jedi.org/blog/archives/005818.html" title="Dvorak 許氏鍵盤 Yahoo! 奇摩輸入法 | Jedi's BLOG">Dvorak 許氏鍵盤 Yahoo! 奇摩輸入法</a>》提到我根據自己那奇怪的輸入需求(全世界八十億人口,像我這樣用 Dvorak 許氏鍵盤排列的注音輸入法使用者,大概一隻手數得完),持續編修滋養我自己分支的漁村符號輸入表格:<a href="https://jedi.org/p4/cin/ehq-symbols-jedi.cin" download="ehq-symbols-jedi.cin">ehq-symbols-jedi.cin</a>。目前除了原本承襲的漁村符號(我後續做了一些補充跟修訂)、伊呂波日文假名,我加進希臘字母、(許氏鍵盤對應的)注音符號、(許氏鍵盤對應的)台灣點字、元素週期表(用原子序可以輸入中文元素名稱或元素符號,也可以用元素符號輸入中文元素名稱)、創用 CC 授權標章圖示。</p>]]>
</description>
<dc:subject>hack</dc:subject>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2023-10-07T14:54:00+08:00</dc:date>
</item>
<item rdf:about="https://jedi.org/blog/archives/006412.html">
<title>中秋月圓</title>
<link>https://jedi.org/blog/archives/006412.html</link>
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<description>
<![CDATA[<p><img alt="中秋月圓特寫" src="https://jedi.org/blog/archives/moon_2023.png" width="600" height="400" border="0"></p>]]>
<![CDATA[<p>隨手拿已經 11 歲的手機拍中秋月,無腳架、無後製、無縮放,直出 JPEG 轉 PNG。靠著腦海中的印象來設定拍攝參數:</p>
<dl>
<dt>超取樣模式</dt>
<dd>完整解析度 (34 MP)</dd>
<dt>JPEG 壓縮品質</dt>
<dd>100%</dd>
<dt>曝光補償</dt>
<dd>-4.0</dd>
<dt>ISO</dt>
<dd>50</dd>
<dt>對焦模式</dt>
<dd>無限遠</dd>
<dt>閃光燈</dt>
<dd>強制使用</dd>
<dt>白平衡模式</dt>
<dd>陰天</dd>
<dt>ND 減光濾鏡</dt>
<dd>強制使用</dd>
</dl>]]>
</description>
<dc:subject>visual_dump</dc:subject>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2023-09-29T23:43:17+08:00</dc:date>
</item>
<item rdf:about="https://jedi.org/blog/archives/006411.html">
<title>聽力照護諮商工具台灣華語版</title>
<link>https://jedi.org/blog/archives/006411.html</link>
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<description>
<![CDATA[<p>前陣子有位朋友找我諮商聽力處遇,我順手把幾個 <a href="https://idainstitute.com/">Ida Institute</a> 提供的諮商工具翻譯成台灣華語(Ida Institute 網站上提供的是中國華語版),現在提供如下:</p>
<ul>
<li><a href="https://jedi.org/blog/archives/The_Line_editable-cht.pdf">「線條」台灣華語版 PDF</a>,建議使用於<a href="https://jedi.org/blog/archives/006383.html#contemplation" title="意圖期 (contemplation) | 在輔具中心提供以人為本的聽覺輔具服務 | Jedi's BLOG">意圖期</a>。</li>
<li><a href="https://jedi.org/blog/archives/The_Box_editable-cht.pdf">「方格」台灣華語版 PDF</a>,建議使用於<a href="https://jedi.org/blog/archives/006383.html#preparation" title="準備期 (preparation) | 在輔具中心提供以人為本的聽覺輔具服務 | Jedi's BLOG">準備期</a>。</li>
<li><a href="https://jedi.org/blog/archives/My_hearing_explained__editable_FINAL_logo-cht.pdf">「圖解我的聽力」台灣華語版 PDF</a>,建議搭配聽力檢查結果一起使用。</li>
</ul>
<p>這三個 PDF 檔案都是「PDF 表單」格式,使用免費的 PDF 閱讀軟體也能夠輸入編輯、點選尺標。我除了翻譯內容文字,也調整表單輸入欄位的中文字型,以及讓輸入的效果可以跟欄位格線對齊(希望啦)。</p>
<p>這三個 PDF 檔案若有任何我可以主張著作權的部份,我在法律許可的範圍內,拋棄依著作權法所享有之權利,包括所有相關與鄰接的法律權利,並宣告貢獻至公眾領域。</p>]]>
</description>
<dc:subject>occupation</dc:subject>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2023-09-09T19:23:12+08:00</dc:date>
</item>
<item rdf:about="https://jedi.org/blog/archives/006410.html">
<title>情緒反應</title>
<link>https://jedi.org/blog/archives/006410.html</link>
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<description>
<![CDATA[<p>最近這幾年,我很努力實踐的自我管理是:「先等情緒過去,再反應。」</p>
<p>更年輕的時候,曾以為自己可以練習到不要讓情緒左右理智,經歷幾年的跌跌撞撞之後才明白:情緒一定會左右理智,那是擺脫不掉的身體反應。不過現在至少比較能察覺自己正處於情緒波瀾的狀態,也知道這個狀態做任何反應都只會後悔,尤其有時候不是做什麼的問題,而是怎麼做的問題。</p>
<p>所以練習了讓自己習慣「不是每件事都需要立刻反應」,學習「等待」自己的情緒消退、露出底下潛藏的理智,這時再反應。</p>]]>
</description>
<dc:subject>kitchen</dc:subject>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2023-09-05T14:11:23+08:00</dc:date>
</item>
<item rdf:about="https://jedi.org/blog/archives/006409.html">
<title>9,876</title>
<link>https://jedi.org/blog/archives/006409.html</link>
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<description>
<![CDATA[<p>很多事情都跟一年前的想像不同。</p>
<p>很多事情都跟一個月前的想像不同。</p>
<p>很多事情都跟一個星期前的想像不同。</p>
<p lang="fr">C'est la vie.</p>]]>
</description>
<dc:subject>kitchen</dc:subject>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2023-08-29T19:47:51+08:00</dc:date>
</item>
<item rdf:about="https://jedi.org/blog/archives/006408.html">
<title>「特定醫療器材品項(含助聽器)應符合之規格、檢驗方法及性能」正式訂定</title>
<link>https://jedi.org/blog/archives/006408.html</link>
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<description>
<![CDATA[<p>行政院公報第 029 卷第 152 期(2023-08-15)刊登衛生福利部食品藥物管理署於 2023 年 8 月 15 日<a href="https://gazette.nat.gov.tw/egFront/detail.do?metaid=142634" title="行政院公報資訊網 | 衛生福利部公告:訂定「特定醫療器材品項應符合之規格、檢驗方法及性能」,自113年9月1日生效">衛授食字第 1121606039 號</a>公告訂定《特定醫療器材品項應符合之規格、檢驗方法及性能》,其中包括「空氣傳導性助聽器」項目,自 2024 年 9 月 1 日生效。</p>]]>
<![CDATA[<p>這個正式訂定的版本,在助聽器部分,內容跟<a href="https://jedi.org/blog/archives/006401.html" title="更新:「特定醫療器材品項(含助聽器)應符合之規格、檢驗方法及性能」草案 | Jedi's BLOG">先前的預告草案</a>完全相同。換句話說,在助聽器的電聲性能部分,無法對產品原始設計的品質有任何把關效果。</p>
<p>我自己 3 月 30 日即透過電子郵件向食藥署表達此意見,就我所知,大概 4 月的時候,聽力師公會全國聯合會也向食藥署發文表示相同意見。我始終未曾收到食藥署回復,也很遺憾最後訂定的版本仍然如此。</p>]]>
</description>
<dc:subject>occupation</dc:subject>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2023-08-15T18:20:31+08:00</dc:date>
</item>
<item rdf:about="https://jedi.org/blog/archives/006407.html">
<title>全球無障礙體驗日 GAAD 2023</title>
<link>https://jedi.org/blog/archives/006407.html</link>
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<description>
<![CDATA[<p>科技讓我們探索無垠可能,實現前人未能企及的夢想。</p>
<p>握擁科技的力量,我們如履薄冰:如果我們運用科技的方式,增幅一些人卻排除另一些人,反而撕裂信任、擴大隔閡。</p>
<p>我們想要科技帶來進步,首要了解並樂於接受:每個人的眼、耳、手、腦都不同,各有擅長與侷限,能運用不同輔助科技改變這些能力。</p>]]>
<![CDATA[<p>今天 (2023-05-18) 是<a href="https://accessibility.day/" title="Home | GAAD">全球無障礙體認日</a> (Global Accessibility Awareness Day, GAAD),我想趁機聊聊資通安全與親和力/無障礙。</p>
<p>任何資安策略或措施都要考慮「人」也在系統中。即使出發本意是安全,一旦造成使用系統的障礙,人類的自然慣性是犧牲安全性,例如把密碼抄到便利貼,或者把個人資訊交給其他人操作。</p>
<p>我們相信:人人都能用、都好用的系統,才能長長久久,這樣的安全才是大家想要且需要的安全。我們說,這樣的系統具備<dfn><strong>韌性</strong>特質</dfn>。</p>
<p>滋養這種韌性,可以就從今天體認到無障礙開始。</p>
<p>無障礙不只是法定身心障礙者的事,而是每個年齡會增長、工作很忙碌、生活很多樣的人的事;我們在人生不同階段、不同精神情緒狀態、不同空間環境裡,都需要獲得好好對待,都值得愉快體驗。</p>
<p>這是無障礙的努力目標,也是無障礙的觀點:雖然只有部分人領取身心障礙證明,但是每個人都有遭遇阻礙的時候;無障礙對一些人不可或缺,且對所有人帶來益處,是系統韌性的重要元素。</p>
<p>了解無障礙、學習無障礙、實踐無障礙設計,馬上可以拯救一些人,幫助所有人,還能幫到未來的自己。</p>]]>
</description>
<dc:subject>typing</dc:subject>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2023-05-18T00:02:00+08:00</dc:date>
</item>
<item rdf:about="https://jedi.org/blog/archives/006406.html">
<title>名片觸摸設計與貝爾曼截角 (Berman Corner)</title>
<link>https://jedi.org/blog/archives/006406.html</link>
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<description>
<![CDATA[<p>最近因為一些原因,又做起名片。我覺得這是個很好的機會,重新檢討「要怎麼製作名片,才能讓盲人可以獲得等效資訊內容?」</p>
<p><img alt="名片上的點字印壓凸起效果特寫" src="https://jedi.org/blog/archives/card_braille.png" width="800" height="480" border="0"><br>
我使用至今的名片是直接在名片上印壓點字(目前在台灣有許多視障者團體可以承接這類製作案件),這個做法的主要缺點有四:首先可以使用的字數相當有限,大概是 15 個中文字加上一串電話號碼,無法再放更多內容;其次是凸起效果對於紙面印刷內容的視覺呈現效果難免有些影響,反而對不會點字的低視能者可能造成干擾;第三是難以製作成多語版本,例如只會英文點字的視障者,無法理解台灣點字內容;第四是名片放久或壓在書本、墊板久了,可能會把點字壓平,失去效果。</p>
<p class="pre">註:台灣常用的點字名片製作方式包括直接印壓及黏貼透明點字膜兩種方式。</p>
<p>當時其實我已經在名片上印製 QR Code 二維條碼,我可以透過網頁提供更詳細、兼顧多語需求、具備親和力的內容。但是當年我有個不安:盲人是否可以順利操作「掃描 QR Code」呢?拜智慧型行動設備軟、硬體進步所賜,現在我已經很有信心:<mark>盲人掃描 QR Code 可以相當順利且迅速。</mark>下一個問題,就是我要怎麼讓盲人知道這張名片上面有 QR Code 可以掃描?當然我遞名片的時候會順口說,但是對方是否能夠記得住?或者,能否在一疊名片中知道有 QR Code 的是哪幾張?</p>]]>
<![CDATA[<p><img alt="二維條碼旁邊以點字印壓 QR 文字的凸起效果特寫" src="https://jedi.org/blog/archives/qr_braille.png" width="800" height="480" border="0"><br>
微軟在<a href="https://jedi.org/blog/archives/006385.html" title="微軟適應性周邊開箱 | Jedi's BLOG">適應性周邊</a>的外盒包裝上,利用 QR Code 提供完整資訊網頁。對於「包裝盒」這麼一個外型複雜的物品,微軟標示的方法非常簡單,就是在 QR Code 旁邊用點字印壓 QR 文字 (⠟ ⠗),點字部分不會佔用太多空間,很容易融入整體視覺設計。</p>
<p><img alt="二維條碼旁邊以點字印壓 QR 文字,以及二維條碼外框四角印壓凸起效果特寫" src="https://jedi.org/blog/archives/qr_braille_square.png" width="800" height="480" border="0"><br>
與之相似地,微軟在<a href="https://jedi.org/blog/archives/006343.html" title="微軟調適型套件/適應性套件 (Surface Adaptive Kit) 開箱 | Jedi's BLOG">適應性套件</a>說明小卡上也印壓 QR 文字,但是在 QR Code 外框四邊角也壓印凸起,幫助盲人更容易定位 QR Code 位置。</p>
<p>不過,對於一般製作名片來說,印壓 QR Code 外框或外框邊角的成本可能是項挑戰,也許要達到某個印量,才能攤平模具成本。</p>
<p class="pre">註:前陣子<a href="https://www.facebook.com/people/雲嘉南區職務再設計/100057064585183/" title="雲嘉南區職務再設計 | Facebook">雲嘉南區職務再設計專案單位</a>的職務再設計專員告訴我:現在市場上興起的 UV 印刷技術可以在各種材質上印製立體浮雕的凹凸效果,也能少量印製,是鋼印之外的選擇。</p>
<p>其實就跟盲人如何簽名跟蓋章很像,不需要完整四個角落,通常(對於慣用手為右手的盲人)只需告知區域左上角,就可以形成充足的空間心像。</p>
<p>如果只想要少量製作(保留給盲人對象),不妨拿微軟適應性套件來用:<br>
<img alt="圓點、短線、圓圈、叉叉形狀的凸面貼紙特寫" src="https://jedi.org/blog/archives/touch_stickers.png" width="800" height="480" border="0"><img alt="短線、長線、圓圈等形狀的透明凸面貼紙特寫" src="https://jedi.org/blog/archives/touch_transparent_stickers.png" width="800" height="480" border="0"><br>
貼在 QR Code 的邊邊角角,很容易搭配名片原本的視覺設計。</p>
<p>其實還有一種設計花樣 (design pattern) 特別適用於名片。因為名片的尺寸不大,形狀也不像包裝盒那樣複雜多面,只要有辦法提示「這張名片有 QR Code」,盲人很快就能掃描成功。這個設計花樣是<u class="pn">大衛</u>‧<u class="pn">貝爾曼</u>在 2014 年提出的<dfn><a href="http://www.davidberman.com/corner" title="“Berman Corner” for people who can’t see | David Berman Communications">貝爾曼截角</a></dfn>,方法是在平面印刷品(包括名片)的某個角落截掉一角,截掉的那角是短邊 0.32~0.64 公分長的等腰直角三角形,用來表示這個角落的 9 公分見方範圍內有個 QR Code。</p>
<p>因為名片的長邊通常就是 9 公分,所以在任何一角截掉都可以表示名片上某處有 QR Code;有些盲人偏好截在右上角,有些偏好截在左上角,有些偏好截在最靠近 QR Code 那一角,似乎沒有一定要怎麼截。貝爾曼截角的優勢是加工非常容易:自己拿把剪刀也能做,辦公室裁紙機也可以小批量加工。如果要大量製作名片,也許要向印刷廠洽詢刀模,價錢可能比較不一定。另外,對於原本四角就已經裁成圓角的名片,貝爾曼截角的觸覺差異是否夠明顯?從<u class="pn">貝爾曼</u>引述的研究結果來說似乎是夠的,但也許值得再與盲人朋友多確認。</p>]]>
</description>
<dc:subject>occupation</dc:subject>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2023-05-01T20:23:24+08:00</dc:date>
</item>
<item rdf:about="https://jedi.org/blog/archives/006405.html">
<title>9,999</title>
<link>https://jedi.org/blog/archives/006405.html</link>
<cc:License rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/" />
<description>
<![CDATA[<p>最近又忙碌起來。起先料想的衝擊沒有發生,但是衝擊還是發生了,希望不要耗費太長的時間調整完日常生活步調。</p>
<p>很多事情略有進展,但也還有太多待辦。</p>
<p>總之目前的狀態是覺得有很多未知不明(也許混著一些不安),充滿希望的那一種,所以大概是好事。想一想,明年此刻無論路線怎麼分支,對自己都還是開心的方向吧。</p>
<p>這樣也就夠了。</p>]]>
</description>
<dc:subject>kitchen</dc:subject>
<dc:creator>Jedi Lin</dc:creator>
<dc:date>2023-04-28T12:20:28+08:00</dc:date>
</item>
<cc:License rdf:about="http://creativecommons.org/licenses/by/3.0/tw/">
<dcq:hasVersion>3.0</dcq:hasVersion>
<cc:licenseClass rdf:resource="http://creativecommons.org/license/"/>
<dc:identifier>by</dc:identifier>
<foaf:logo rdf:resource="http://i.creativecommons.org/l/by/3.0/tw/88x31.png"/>
<foaf:logo rdf:resource="http://i.creativecommons.org/l/by/3.0/tw/80x15.png"/>
<cc:legalcode rdf:resource="http://creativecommons.org/licenses/by/3.0/tw/legalcode"/>
<dc:title xml:lang="te">ఆపాదింపు 3.0 తైవాన్</dc:title>
<dc:title xml:lang="sr-Latn">Autorstvo 3.0 Tajvan</dc:title>
<dc:title xml:lang="en-sg">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="es-ar">Atribución 3.0 Taiwan</dc:title>
<dc:title xml:lang="pt-pt">Atribuição 3.0 Taiwan</dc:title>
<dc:title xml:lang="de-at">Namensnennung 3.0 Taiwan</dc:title>
<dc:title xml:lang="es-es">Reconocimiento 3.0 Taiwan</dc:title>
<dc:title xml:lang="th">แสดงที่มา 3.0 ไต้หวัน</dc:title>
<dc:title xml:lang="en-hk">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="et">Autorile viitamine 3.0 Taiwan</dc:title>
<dc:title xml:lang="as">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="sv">Erkännande 3.0 Taiwan</dc:title>
<dc:title xml:lang="zh-tw">姓名標示 3.0 台灣</dc:title>
<dc:title xml:lang="es-gt">Reconocimiento 3.0 Taiwan</dc:title>
<dc:title xml:lang="si-lk">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="zu">Qaphela Umnikazi 3.0 iTaiwan</dc:title>
<dc:title xml:lang="eu">Aitortu 3.0 Taiwan</dc:title>
<dc:title xml:lang="it-ch">Attribuzione 3.0 Taiwan</dc:title>
<dc:title xml:lang="en-gb">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="ur">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="tr">Attribution 3.0 Tayvan</dc:title>
<dc:title xml:lang="sl">Priznanje avtorstva 3.0 Tajvan</dc:title>
<dc:title xml:lang="hr">Imenovanje 3.0 Tajvan</dc:title>
<dc:title xml:lang="az">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="fr-lu">Paternité 3.0 Taiwan</dc:title>
<dc:title xml:lang="zh-hk">姓名標示 3.0 台灣</dc:title>
<dc:title xml:lang="it">Attribuzione 3.0 Taiwan</dc:title>
<dc:title xml:lang="st">Attribution</dc:title>
<dc:title xml:lang="ta">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="es-pr">Reconocimiento 3.0 Taiwan</dc:title>
<dc:title xml:lang="uk">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="nl">Naamsvermelding 3.0 Taiwan</dc:title>
<dc:title xml:lang="bg">Признание 3.0 Тайван</dc:title>
<dc:title xml:lang="zh">署名 3.0 台湾</dc:title>
<dc:title xml:lang="lv">Atsaucoties 3.0 Taivāna</dc:title>
<dc:title xml:lang="fr-ca">Paternité 3.0 Taiwan</dc:title>
<dc:title xml:lang="hi">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="ko">저작자표시(Attribution) 3.0 대만</dc:title>
<dc:title xml:lang="kk">Атауын сақтау 3.0 Taiwan</dc:title>
<dc:title xml:lang="ast-es">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="is">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="ca">Reconeixement 3.0 Taiwan</dc:title>
<dc:title xml:lang="ml">കടപ്പാട് 3.0 തായ്വാൻ</dc:title>
<dc:title xml:lang="ro">Atribuire 3.0 Taiwan</dc:title>
<dc:title xml:lang="ms">Pengiktirafan 3.0 Taiwan</dc:title>
<dc:title xml:lang="gl">Recoñecemento 3.0 Taiwan</dc:title>
<dc:title xml:lang="ast">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="es-cl">Atribución 3.0 Taiwan</dc:title>
<dc:title xml:lang="fr-ch">Paternité 3.0 Taiwan</dc:title>
<dc:title xml:lang="sr">Ауторство 3.0 Тајван</dc:title>
<dc:title xml:lang="es-mx">Atribución 3.0 Taiwan</dc:title>
<dc:title xml:lang="ga">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="es-pe">Reconocimiento 3.0 Taiwan</dc:title>
<dc:title xml:lang="en">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="vi">Ghi nhận công của tác giả 3.0 Taiwan</dc:title>
<dc:title xml:lang="pt">Atribuição 3.0 Taiwan</dc:title>
<dc:title xml:lang="ru">Attribution (Атрибуция) 3.0 Тайвань</dc:title>
<dc:title xml:lang="hy">Հղում 3.0 Թայվան</dc:title>
<dc:title xml:lang="lt">Priskyrimas 3.0 Taivanis</dc:title>
<dc:title xml:lang="de-ch">Namensnennung 3.0 Taiwan</dc:title>
<dc:title xml:lang="nso">Tsebagatšo 3.0 Taiwan</dc:title>
<dc:title xml:lang="mn">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="fa">Attribution 3.0 تایوان</dc:title>
<dc:title xml:lang="sq">Attribution 3.0 Taivan</dc:title>
<dc:title xml:lang="fr">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="es">Atribución 3.0 Taiwán</dc:title>
<dc:title xml:lang="es-co">Reconocimiento 3.0 Taiwan</dc:title>
<dc:title xml:lang="eo">Atribuite 3.0 Tajvano</dc:title>
<dc:title xml:lang="en-ca">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="mk">Наведи извор 3.0 Тајван</dc:title>
<dc:title xml:lang="en-us">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="cs">Uveďte autora 3.0 Tchaj-van</dc:title>
<dc:title xml:lang="bn">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="hu">Nevezd meg! 3.0 Tajvan</dc:title>
<dc:title xml:lang="da">Navngivelse 3.0 Taiwan</dc:title>
<dc:title xml:lang="pt-br">Atribuição 3.0 Taiwan</dc:title>
<dc:title xml:lang="x-i18n">${Attribution} 3.0 ${Taiwan}</dc:title>
<dc:title xml:lang="pl">Uznanie autorstwa 3.0 Tajwan</dc:title>
<dc:title xml:lang="de">Namensnennung 3.0 Taiwan</dc:title>
<dc:title xml:lang="no">Navngivelse 3.0 Taiwan</dc:title>
<dc:title xml:lang="id">Atribusi 3.0 Taiwan</dc:title>
<dc:title xml:lang="he">ייחוס 3.0 טאיוואן</dc:title>
<dc:title xml:lang="ja">表示 3.0 台湾(中華民国)</dc:title>
<dc:title xml:lang="af">Erkenning 3.0 Taiwan</dc:title>
<dc:title xml:lang="es-ec">Reconocimiento 3.0 Taiwan</dc:title>
<dc:title xml:lang="el">Αναφορά Δημιουργού 3.0 Ταϊβάν</dc:title>
<dc:title xml:lang="be">Атрыбуцыя 3.0 Тайвань</dc:title>
<dc:title xml:lang="ar">نسب المصنف 3.0 تايوان</dc:title>
<dc:title xml:lang="fi">Nimeä 3.0 Taiwan</dc:title>
<dc:title xml:lang="sr-latn">Autorstvo 3.0 Tajvan</dc:title>
<dc:title xml:lang="oci-es">Attribution 3.0 Taiwan</dc:title>
<dc:title xml:lang="ka">ავტორობის მითითებით 3.0 ტაივანი</dc:title>
<cc:jurisdiction rdf:resource="http://creativecommons.org/international/tw/"/>
<dc:source rdf:resource="http://creativecommons.org/licenses/by/3.0/"/>
<cc:requires rdf:resource="http://creativecommons.org/ns#Notice"/>
<cc:requires rdf:resource="http://creativecommons.org/ns#Attribution"/>
<dc:creator rdf:resource="http://creativecommons.org"/>
<cc:permits rdf:resource="http://creativecommons.org/ns#Reproduction"/>
<cc:permits rdf:resource="http://creativecommons.org/ns#Distribution"/>
<cc:permits rdf:resource="http://creativecommons.org/ns#DerivativeWorks"/>
</cc:License>
</rdf:RDF>
If you would like to create a banner that links to this page (i.e. this validation result), do the following:
Download the "valid RSS" banner.
Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)
Add this HTML to your page (change the image src
attribute if necessary):
If you would like to create a text link instead, here is the URL you can use:
http://www.feedvalidator.org/check.cgi?url=http%3A//Jedi.org/blog/index.rdf