Skip to content
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

Closed
shawna-slh opened this issue Jul 19, 2017 · 4 comments
Closed

[WAI] same content for W3C main site and WAI subsite? #3

shawna-slh opened this issue Jul 19, 2017 · 4 comments
Labels

Comments

@shawna-slh
Copy link
Contributor

shawna-slh commented Jul 19, 2017

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?

@shawna-slh shawna-slh changed the title [W3C WAI] same content? [W3C WAI] same content for W3C main site and WAI subsite? Jul 19, 2017
@shawna-slh shawna-slh changed the title [W3C WAI] same content for W3C main site and WAI subsite? [WAI] same content for W3C main site and WAI subsite? Jul 22, 2017
@nrhsinclair
Copy link

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.

@vmmiller
Copy link

vmmiller commented Jul 26, 2017

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.

@notabene
Copy link
Member

notabene commented Aug 3, 2017

It seems to me that keeping two different contents is good and that what @nrhsinclair and @vmmiller say is relevant (yay ;)).

I wonder, though, whether the W3C page is not somehow too detailed. What is its precise role? If it's an introduction, maybe there's too much of it and the WAI page could be the go-to page for further reference. (I'm not strongly attached to what I'm saying, just that the need for separate two pages is unclear to me if they have roughly the same content and I'd be grateful to have some clarification. Maybe it's just me being new to EOWG ;))

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.

@shawna-slh
Copy link
Contributor Author

shawna-slh commented Sep 22, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants