[MAGNOLIA-124] provide accessibility compliant samples Created: 11/Oct/04 Updated: 23/Jan/13 Resolved: 10/Nov/04 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | samples |
| Affects Version/s: | 2.0 Final |
| Fix Version/s: | 2.0 Final |
| Type: | New Feature | Priority: | Major |
| Reporter: | Boris Kraft | Assignee: | Vinzenz Wyser |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
The current samples do not show that Magnolia could generate web sites that are "accessible" - e.g. see http://www.w3.org/WAI/gettingstarted/ Also, they should be valid xhtml in the sense of http://www.validome.org/ These samples could be in addition to existing samples |
| Comments |
| Comment by Mark [ 28/Oct/04 ] |
|
Accessibility compliance (and section 508) is mandated by a number of large institutions and agencies. It is important that magnolia meet accessibility standards. |
| Comment by Boris Kraft [ 28/Oct/04 ] |
|
Its really a question of the templates. We can lead by example, but we cannot guarantee that people out there don't write templates that don't have accessability in mind. |
| Comment by Vinzenz Wyser [ 10/Nov/04 ] |
|
validation checked accessibility more or less (alt for images, layout (text comes first) |