You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 30, 2018. It is now read-only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
Plain language: Provide clear and simple language in instructions, labels, navigational elements, and error messages which require a response to continue, so that all of the following are true.
Simple tense: Use present tense and active voice.
Simple, clear, and common words: Use the most common 1500 words or phrases or, provide words, phrases or abbreviations that are the most-common form to refer to the concept in the identified context.
Double negatives are not used.
Concrete language: Non-literal language is not used, or can be automatically replaced, via an easy-to-set user setting. All meaning must be retained when non-literal text is replaced.
Instructions: Each step in instructions is identified
New exception
If there are no tools available in the language of the content that identify uncommon words, instructions that are longer than 400 words are exempt unless they directly relate to a critical service.
New Glossary item:
identified context: context and a context specific word frequency list (and glossary) have been identified in an accessibility statement or other known technique. A word frequency list has to be generated from at least 1000 sources from the same context or however many pages can reasonably be found.
I am afraid that the definitions of Success Criterion 3.1.7 maybe too English-centric. For instance, labels and buttons may require infinitive or imperative forms in other languages such as Spanish, and those forms can also be easily testable. Use of modals like MUST and SHOULD would also be useful where. I would suggest concentrating on specific areas which are lexical, grammatical and discourse-analysis oriented, and then leave the specific techniques to each language (and to translators and localisers). For instance, use of X most common words in a language, or if a term is frequently used in a certain context but uncommon in the language (e.g. pull request), there should be a clear definition using common words (but then we are in the 3.1.3 success criterion). As for grammar, use tenses which clearly and unambiguously allow (and require) to specify subject, object of the phrase, etc. As for discourse analysis or textual coherence, clearly refer to objects or actions which have previously or just before been presented or can be perceived in the vicinity or whose results can actually be tested before commiting the specif action, and so on.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Plain Language (Minimum) #30