w3c / wcag

Web Content Accessibility Guidelines
https://w3c.github.io/wcag/guidelines/22/
Other
1.09k stars 248 forks source link

Language level and inclusion. 3.1.5 #2022

Open paul-poupet opened 3 years ago

paul-poupet commented 3 years ago

Dear all,

After reading the discussion of @jake-abma and @alastc on reading level :

-> Anyway, my point is that technique 153 is the only sufficient technique. 103 and 86 cannot be considered as alternatives techniques but they are techniques to go further after the application of technique 153 -> Moreover, a binary result on the clarity of the language can be defined. Global functions (ratio of words/sentences…) doesn’t seem to fit, but a part of the important things are listed in the description of G153, it just has to be completed and turned into an algorithm with a binary answer (i can work on it with some researchers in linguistics, somepeople already implemented reading level scores of a text : https://cental.uclouvain.be/amesure/ in belgium, https://u31.io in france...).

=> Concretely, 153 is the main technique, or even better : the use of an understandable language as a AA guideline (either as a primary language or as another language “simplified english”), and all the other techniques (86 in supplement, 103, or the idea of including disabled peoples in a creation or validation process of the content) in a AAA guideline.

16% of the population, without other disabilities, has difficulty reading and understanding written information: making written content more readable is necessary for all of these people.

I can make a pull request if other experts do not have concerns

Thanks for reading, i’ll be happy to discuss on those points (reach me on github or at paul.poupet@seed-up.io Paul

patrickhlauke commented 3 years ago

just a brief note to clarify: you can't make a technique mandatory

paul-poupet commented 3 years ago

sorry for that, i mean this is the only existing sufficient technique (86 and 103 are not sufficient, at least advisory)