If you're creating a tool that posts things on the web, or allows a person to create content, please make sure that your tool(s) pay attention to the Authoring Tool Accessibility Guidelines (ATAG):
w3.org/TR/ATAG20/
w3.org/TR/ATAG20/
First, your tool should be accessible itself.
Second, your tool needs to facilitate authors creating accessible content, and should guide them towards it.
Second, your tool needs to facilitate authors creating accessible content, and should guide them towards it.
As an example - Guideline B.2.3: Assist authors with managing alternative content for non-text content.
If your tool allows people to set a text equivalent for an image or some other type of content, then you should allow them to edit it.
If your tool allows people to set a text equivalent for an image or some other type of content, then you should allow them to edit it.
Another one:
B.4.1.1 Features Active by Default: All accessible content support features are turned on by default.
In other words, tools that allow you to create accessible content should be turned on and not buried somewhere.
B.4.1.1 Features Active by Default: All accessible content support features are turned on by default.
In other words, tools that allow you to create accessible content should be turned on and not buried somewhere.
B.4.1.3 Feature Deactivation Warning
If an author tries to turn off a feature that helps provide accessible content, you should warn the author that they're creating a problem by doing so.
If an author tries to turn off a feature that helps provide accessible content, you should warn the author that they're creating a problem by doing so.
This is a REALLY GREAT one:
B.4.2.1 Model Practice
Your examples demonstrate accessible authoring practices. Providing code? Providing screenshots? Demonstrate how to do it right.
B.4.2.1 Model Practice
Your examples demonstrate accessible authoring practices. Providing code? Providing screenshots? Demonstrate how to do it right.
There's a LOT more to dig into in ATAG, but lets leave it at that for now...
Bottom line: If you're creating a toolset that produces content that is consumed on the web, you've got a responsibility to do it right. ATAG can help you.
Bottom line: If you're creating a toolset that produces content that is consumed on the web, you've got a responsibility to do it right. ATAG can help you.
Ok, one more... I like this one:
Guideline B.1.2: Ensure that accessibility information is preserved
If you take content that is accessible, when you share it or transform it or do other things to it, you shouldn't take that accessibility away.
Think "sharing tools"
Guideline B.1.2: Ensure that accessibility information is preserved
If you take content that is accessible, when you share it or transform it or do other things to it, you shouldn't take that accessibility away.
Think "sharing tools"
Think bookmarklets, think in-page sharing widgets, think browser extensions, think APIs. All of these should preserve the accessibility that already exists.
