Thread by @jpluimers

I am going to first translate this, then extend this to archivability.Jeroen Pluimers added,
Bianca ♻️ 🚵‍♀️ 😎

Based on the below thread of @jpluimers @mbirna @rulesbyrosita

https://twitter.com/BiancaPrins/status/1139570571979739137

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

https://twitter.com/MarkGraham/status/1136881307714170880

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 (bandwith/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:

1. make sure what you create is accessible
2. ensure your (online) content is archivable
3. help archiving content

/end