-
Notifications
You must be signed in to change notification settings - Fork 59
[Principles] Unreadable, unusable #21
Comments
@sharronrush maybe it is because the expand/collapse functionality is not working on the GitHub version? do you feel the same about the current online version? in any case, i look forward to the redesign too. but what would you suggest in the mean time? |
I don't know, I think I have nothing useful to suggest, Shadi, I am very sorry to say. It is just that I cannot imagine a happy use case for this information in its current presentation format. People who are new to accessibility are likely to become overwhelmed and exhausted when confronted by such a long list of links and then paragraphs of unbroken text explanations that seem to repeat information found elsewhere on the site. What is the purpose of this page? Someone said it should come first, but I don't think that is the answer either. The note says "This page is illustrative and is not intended to be an exhaustive listing of all accessibility requirements." What is it meant to do? I really just don't understand it. |
The purpose is to provide a summary of the WAI Guidelines for non-technical audiences. |
Then in my opinion it is not very successful since it is lacking brevity
and clarity. I will take a pass at an edit.
…On Tue, Mar 28, 2017 at 4:34 AM, Shadi Abou-Zahra ***@***.***> wrote:
The purpose is to provide a summary of the WAI Guidelines for
non-technical audiences.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGqv03VY8lP5iDx5F67rpXqqNhZunedlks5rqNQ-gaJpZM4MqarN>
.
--
Sharron Rush | Executive Director | Knowbility.org | @knowbility
*Equal access to technology for people with disabilities*
|
This issue was moved to w3c/wai-website#787 |
More context: We split the principles from how people with disabilities use the web. Collecting issues over there :-) |
I don't like this page at all and would completely eliminate it since it embodies all of the problems with readability, "wall of text" and other things that seem to me the formatting issues that make our information too often unusable. However, I know that I am in the minority and so will step aside and accept the decision of the group in the hope that this is addressed in the redesign.
The text was updated successfully, but these errors were encountered: