kasperisager/ag

A set of abstract accessibility guidelines to describe all the things

ag's Issues

"Disturbances" term?

I have been thinking about if "disturbances" could be a term we want to include as well. We don't want something that hinders people in doing what they came for, because something else is causing disturbances, e.g. flashes causing seizures, audio that cannot be stopped interferring with a screen reader, or motion that cannot be stopped causing motion sickness for people with concussions or concentration issues for people with cognitive disabilities (I know that this is web examples again, I cannot help it...)

Then I realised that this term is maybe quite similar to the Non-Interference term in WCAG 2, https://www.w3.org/TR/WCAG21/#cc5, which includes these SC:

1.4.2 - Audio Control,
2.1.2 - No Keyboard Trap,
2.3.1 - Three Flashes or Below Threshold, and
2.2.2 - Pause, Stop, Hide.

So nothing new there, but I still think it is something we might want to consider including.

The baby and the bath water from WCAG 2

Here is an outline showing the WCAG 2.1 principles and guidelines with my comments on how they map or don't map to what we are currently writing on.

Notes on my annotations:

• Things in parenthesis = I find that this is too technology specific to be part of higher level definitions and should be kept closer to guidance on how to implement in different technologies.
• Things not in parenthesis = I think we should at one point ensure that we cover these concepts in our proposal. I have written a little note on how I think it relates to our current concepts.

WCAG principles and guidelines with Annes annotations:

1. Perceivable - covered in "perceive"
   (1.1 Text-alternatives)
   (1.2 Time-based Media)
   1.3 Adaptable - can maybe be covered by "perceive" through "helper" + a bit more random stuff for mobile and COGA
   1.4 Distinguishable - related to "perceive" but has to do with more of a "scale" of how perceivable things are

2. Operable - is this covered by "(able to) manipulate"?
   (2.1 Keyboard Accessible)
   (2.2 Enough Time)
   2.3 Seizures and Physical Reactions - I think I already suggested we look at some kind of "non-intereference/no disturbances" definition
   2.4 Navigable - I think there is an issue mentioning something like this already
   2.5 Input Modalities - first I was finding this too specific, but maybe there is something about supporting different input modalities (keyboard could be included here!), as well as something about "helpers" translating into different output modalities (text to speach, text to braille etc.)

3. Understandable
   (3.1 Readable)
   3.2 Predictable - related to "affordance" + something about consistency
   (3.3 Input Assistance)

4. Robust - I think this should be covered under "perceive" and "(able to) manipulate". Why isn't it already under other principles in WCAG 2?
   (4.1 Compatible)

"Navigation", "location", "view/context"

Just noting down after our meeting, that I think we had some interesting discussions about (among other things):

• being able to determine current location within the system
• having a view/context/something around the current location that sets the scene for which artefacts are currently perceivable and allows interactions. Last time the consensus was that this was just a system within the system, but it seems that we need to be able to differentiate the "current system" from other systems on other scales
• allowing navigation within the system and/or to other systems.