 | Thomas Mueller on Question got closed in May 202… |
 | Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
 | bimmer on Resetting the iDrive on a BMW… |
Posted by jpluimers on 2025/02/27
A long while ago, I participated in a Twitter thread that started with a translation of some important accessibility posts by Bianca Prins, then extended it to the concept to archivability:
[WayBack] Thread by @jpluimers: “I am going to first translate this, then extend this to archivability…. @jpluimers […]” #UXdesign #accessibility.
Based on the below thread of @jpluimers @mbirna@rulesbyrosita
Bianca @BiancaPrins
Op zich is #toegankelijkheid in #UXdesign niet moeilijk, het ligt er vooral aan of je toegankelijkheid als startpunt neemt.
Het vraagt om een andere manier van denken vanaf de oorsprong. Repareren daarintegen is wel moeilijk en kostbaar, wat in huidige tijd veelal het geval is
Accessibility in #UXdesign is not hard. It very much depends if you factor in accessibility from the very start.It requires a different way of thinking early on in the process. Repairing inaccessible cases on the other hand is difficult in costly, and often is the case.This basically holds for anything: when #accessibility is your starting point, then you can include it for a maximum of 5% of the total cost without having to compromise things like beautiful design.
Again, architecting solutions need to include accessibility from day 1! 💪
I am going to extend this to archivability of on-line content. There the @internetarchive and it’s @waybackmachine are very important to be compatible with.Making a site content easy to archive is not hard either, though I sense that modern sites make it harder for themselves to be archived.
That’s why I posted
Mark Graham@MarkGraham
Might you please share a URL you are not able to archive to the Wayback Machine?
and try to raise awareness of various content owners for which content is hard to archive.(that must be: “quoted and replied to” instead of posted)
I am also immensely grateful to people like Jason Scott (@textfiles) and Steve McLaughlin (@SteveMcLaugh) of the @archiveteam that help automatic archiving.
It is also very easy to help the archive team by running an @at_warrior virtual Archive Team Warrior appliance. Basically it is a set-and-forget virtual machine that take few resources (bandwidth/memory/CPU/storage) but still help archiving.When G+ went down, I started two instances each taking the below resources, and together peaking at less than 50 Mbit/s, but averaging far below 20 Mbit/s.So:
- make sure what you create is accessible
- ensure your (online) content is archivable
- help archiving content
/end
--jeroen
The Wiert Corner - irregular stream of stuff 
Leave a comment