Croqa11y

Abbreviated to a11y meaning a 11 letters y aka accessibility - dumb but standard. read a11y as ally because even if you don't need accessibility you're an ally for those who do
whereever you see a11y read it as accessibility

Sort of like green energy in that, if you can, you should take measures to minimise your impact like turning off lights, a few basic 'hygeine' responsibilities like recycling that everyone ought to learn, and minimise your impact if you personally are doing something unusual and excessive like a home server lab or air conditioning all the time. But at the end of the day the biggest changes, like using green sources instead of eg coal for power, isn't the responsibility of the individual.

Nor is most accessibility the responsibilty of the author. It's the wiki's job to create an accessible baseline, and staff's job to maintain and improve it, but authors should only concern themselves with minimising the impact of anything they're doing that's unusual and excessive that's affecting the accessibility of their own pages.

Authors are welcome to improve their pages' accessibility beyond the baseline - more accessibility is always good - but much of the time those changes would be better incorporated into the baseline, so that everyone benefits from them

Also there are some things that just can't be done in wikidot (missing features eg aria attributes, inconfigurability eg h1 h2 in header)


Section: baseline accessibility

Theme, site structure

A lot of what you read online applies to this, but consider if any given accessibility advice is better applied to your article or to the whole site

Eg maybe you've read that menus need to be keyboard navigable, and now you're worried that you need to somehow make the site navigation keyboard navigable on your article. You don't - it's the site's responsibility, CSS themes too

Two levels of where a11y changes need to go - should just your article benefit from this? or should everyone?

CSS themes are a middle ground - you need to be careful not to create a11y deficits, but also, you are creating new baseline for people to build on. If you are using a theme there are 3 levels


Section: accessibility deficits (better title needed)
aka what actually is the author's responsibility

a11y deficit = you did something weird and your article is less accessibile as a result

eg
mandatory use of colour or font or other visual characterisitics
interactivity, anything in an iframe
accidental undoing of any baseline a11y - can be hard to spot
images being used as text (https://www.w3.org/WAI/WCAG22/Understanding/images-of-text.html)
images as essential content (alt text)
colour contrast

solutions:
will be different case by case - your a11y deficits are unique, the steps you should take to address them will be unique
'accessibility mode' should not be your immediate go-to - first step should be to try to not have an a11y deficit in the first place
'accessibility mode' as a last resort - 2nd version of the page that doesn't have the deficits


Section: tools

https://webaim.org/resources/contrastchecker/
axe devtools: https://chromewebstore.google.com/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd / https://addons.mozilla.org/en-GB/firefox/addon/axe-devtools/
ibm equal access: https://chromewebstore.google.com/detail/ibm-equal-access-accessib/lkcagbfjnkomcinoddgooolagloogehp / https://addons.mozilla.org/en-US/firefox/addon/accessibility-checker/
wcag quickref https://www.w3.org/WAI/WCAG22/quickref/
aria patterns https://www.w3.org/WAI/ARIA/apg/patterns/ - not really useful outside of iframes other than as a reference