Operations: Difference between revisions

Line 4:

'''Free''' means that their should be as little costs as possible to everyone involved. Free to contribute, and free to read. Getting permission to contribute is as simple as asking in the [matrix] space. It's important for our community model that we can talk to and discuss changes that people have made if we need to.

'''Accessible''' guides isn't just about screen readers. The text should be written so that it is easy to read, and tries to avoid overly-technical explanations with a lot of jargon. Paragraphs should be capped at 5 or so sentences to avoid the "wall of text" effect. Docs should also try to target different skill/knowledge levels. But besides the guides being accessible, it's important to ~~document~~ how to *make* computers be more accessible. That means testing things like:

'''Accessible''' guides isn't just about screen readers. The text should be written so that it is easy to read, and tries to avoid overly-technical explanations with a lot of jargon. Paragraphs should be capped at 5 or so sentences to avoid the "wall of text" effect. Docs should also try to target different skill/knowledge levels. But besides the guides being accessible, it's important to write about how to *make* computers be more accessible. That means testing things like:

* Screen readers

@@ Line 4: / Line 4: @@
 '''Free''' means that their should be as little costs as possible to everyone involved. Free to contribute, and free to read. Getting permission to contribute is as simple as asking in the [matrix] space. It's important for our community model that we can talk to and discuss changes that people have made if we need to.
-'''Accessible''' guides isn't just about screen readers. The text should be written so that it is easy to read, and tries to avoid overly-technical explanations with a lot of jargon. Paragraphs should be capped at 5 or so sentences to avoid the "wall of text" effect. Docs should also try to target different skill/knowledge levels. But besides the guides being accessible, it's important to document how to *make* computers be more accessible. That means testing things like:
+'''Accessible''' guides isn't just about screen readers. The text should be written so that it is easy to read, and tries to avoid overly-technical explanations with a lot of jargon. Paragraphs should be capped at 5 or so sentences to avoid the "wall of text" effect. Docs should also try to target different skill/knowledge levels. But besides the guides being accessible, it's important to write about how to *make* computers be more accessible. That means testing things like:
 * Screen readers