New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WAI] same content for W3C main site and WAI subsite? #3
Comments
It seems to me that W3C page is both an introduction to accessibility and an introduction to WAI and thus, the WAI content should be different, more detailed, more comprehensive. If a user/individual is moving from W3C page to the WAI content they are seeking more in depth information. |
I think you have two separate resources which are really valuable as they address two different groups of users speaking the language of those users very well. The W3C page seems to be focused for the developer and more technical audience and addresses those needs. The WAI page provides a more detailed introduction to accessibility which I find could be more convincing to an audience just learning about the subject matter. It is a very good resource for the business case on accessibility. I would keep both resources as they address different audiences really well. |
It seems to me that keeping two different contents is good and that what @nrhsinclair and @vmmiller say is relevant (yay ;)).
I was wondering aloud, but @slhenry did well to ask me to provide specifics: re-reading it made me think that no, it's OK. |
Based on input, the plan (and requirements) has been revised to say that we will keep two different resources. We'll leave this issue open a bit in case people will add more specific comments on the different requirements for the 2 resources. |
The W3C page was created for the W3C-specific audience that is largely developer and standards orientated -- and following a template for sibling pages (linked under "WEB DESIGN AND APPLICATIONS").
Do we want essentially the same content for the WAI page? (probably minus some of the template info, e.g., "Current Status of Specifications" section)
Or do we want a different focus or emphasis for the WAI page?
(Obviously it would be simpler to have same content.)
If different, how would we define the different Requirements?
The text was updated successfully, but these errors were encountered: