Docs: Introduction of accessibility guidelines #491
Merged
Conversation
This file contains 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
|
Thanks Timon for this guideline (Applause). I have no objections. This guideline will push the improvement of ILIAS in accessibility and give us all a clear concept of what we have to support. |
klees
approved these changes
Apr 19, 2017
docs/documentation/accessibility.md
Outdated
| # Accessibility Guidelines | ||
|
|
||
| According the [Strategy 2017](http://www.ilias.de/docu/goto_docu_file_5585_download.html) | ||
| ILIAS aims to to be "Usable for Everyone" including users with such special needs. |
docs/documentation/accessibility.md
Outdated
|
|
||
| According the [Strategy 2017](http://www.ilias.de/docu/goto_docu_file_5585_download.html) | ||
| ILIAS aims to to be "Usable for Everyone" including users with such special needs. | ||
| ILIAS therefore aims to conform WCAG (Web Content Accessibility Guidelines) 2.0 on |
docs/documentation/accessibility.md
Outdated
| ILIAS therefore aims to conform WCAG (Web Content Accessibility Guidelines) 2.0 on | ||
| conformance level A (see [https://www.w3.org/TR/WCAG20/](https://www.w3.org/TR/WCAG20/) | ||
| ). WCAGs "cover a wide range of recommendations for making Web content more accessible" | ||
| . They claim that by "following these guidelines will make content accessible to a |
docs/documentation/accessibility.md
Outdated
| The WCAG are structured by four principles that provide the foundation for Web | ||
| accessibility: perceivable, operable, understandable, and robust. In the following | ||
| sections we list all WCAG 2.0 level A guidelines we believe to have potential | ||
| consequences on developing ILIAS consequences. Note that they are originate from: |
docs/documentation/accessibility.md
Outdated
| accessibility: perceivable, operable, understandable, and robust. In the following | ||
| sections we list all WCAG 2.0 level A guidelines we believe to have potential | ||
| consequences on developing ILIAS consequences. Note that they are originate from: | ||
| [https://www.w3.org/TR/WCAG20/](https://www.w3.org/TR/WCAG20/). If unsure on how to |
There was a problem hiding this comment.
Maybe link at appropriate locations in the paragraph (e.g.) WCAG 2.0 instead of explicitly writing down the link.
docs/documentation/accessibility.md
Outdated
| sections we list all WCAG 2.0 level A guidelines we believe to have potential | ||
| consequences on developing ILIAS consequences. Note that they are originate from: | ||
| [https://www.w3.org/TR/WCAG20/](https://www.w3.org/TR/WCAG20/). If unsure on how to | ||
| meet some criteria, one can consult[How to Meet WCAG 2.0](https://www.w3.org/WAI/WCAG20/quickref/). |
docs/documentation/accessibility.md
Outdated
| ### Principle 1: Perceivable | ||
| Information and user interface components must be presentable to users in ways they can perceive. | ||
|
|
||
| ##### Guideline 1.1 Text Alternatives |
There was a problem hiding this comment.
Why level 5 title instead of level 4?
docs/documentation/accessibility.md
Outdated
| Provide text alternatives for any non-text content so that it can be changed into other | ||
| forms people need, such as large print, braille, speech, symbols or simpler language. | ||
|
|
||
| - Non-text Content: All non-text content that is presented to the user has a text |
docs/documentation/accessibility.md
Outdated
| ##### Guideline 2.4 Navigable | ||
| Provide ways to help users navigate, find content, and determine where they are. | ||
|
|
||
| Understanding Guideline 2.4 |
There was a problem hiding this comment.
This seems to be some leftover...
Thx Richard!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The JF decided that ILIAS MUST conform WCAG level guidelines (see JF decision: https://www.ilias.de/mantis/view.php?id=20290). Further the JF asked to create new Accessibility Guidelines for the docs directory in order the replace the old ones (located at: http://www.ilias.de/docu/goto_docu_pg_9820_459.html).
Since this is already accepted by the JF, this will automatically merged in one week if no objections are voiced. If there are major objections, this will be discussed in the JF again.
As always, comments, applause, corrections, enhancements or similar are very much welcome!