Q1 How would you describe yourself?

chantingrompΚινητά – Ασύρματες Τεχνολογίες

10 Δεκ 2013 (πριν από 3 χρόνια και 10 μήνες)

142 εμφανίσεις

W3C Site Redesign Survey
1 / 37
40.63%
91
44.20%
99
30.80%
69
16.52%
37
27.68%
62
7.59%
17
12.50%
28
Q1
How would you describe
yourself?
Answered: 224
Skipped: 3
0%
20%
40%
60%
80%
100%
Web designer
Web
application
developer
User
experience
designer/i...
Project
manager
Web
technology
engineer
Department
head
Other (please
specify)
Web designer
Web application developer
User experience designer/information architect/content
strategist
Project manager
Web technology engineer
Department head
Other (please specify)
Total Respondents:
Total Respondents:
224
224
#
Other (please specify)
Date
1
Accessibility standards expert
5/21/2013 11:12 AM
2
an accountant clerk
5/21/2013 6:49 AM
3
teacher of Web development
5/20/2013 10:31 AM
4
University Proffessor (teaching HCI and accessibility)
5/20/2013 6:41 AM
5
architecture
5/18/2013 5:30 PM
6
Design Director
5/17/2013 4:58 PM
7
Typographer
5/16/2013 6:50 PM
8
Researcher
5/16/2013 5:33 PM
9
Front-end developer
5/16/2013 10:49 AM
10
standardista
5/16/2013 8:54 AM
11
web accessibility expert
5/16/2013 5:34 AM
Answer Choices
Responses
W3C Site Redesign Survey
2 / 37
12
front-end web developer
5/16/2013 5:23 AM
13
Educator
5/16/2013 3:55 AM
14
CEO
5/16/2013 1:33 AM
15
web accessibility specialist
5/16/2013 1:00 AM
16
Front-end developer
5/15/2013 11:38 PM
17
marketing and sales.
5/15/2013 10:06 PM
18
trainer
5/15/2013 7:47 PM
19
W3C staff
5/15/2013 6:33 PM
20
Web standards and accessibility advisor
5/15/2013 5:25 PM
21
Mathematician
5/15/2013 4:25 PM
22
Researcher
5/15/2013 4:20 PM
23
lawyer, deanonymized
5/15/2013 3:41 PM
24
Microsoft Open Technologies
5/15/2013 3:37 PM
25
Amateur
5/15/2013 3:18 PM
26
Accessibility Consultant
5/15/2013 2:43 PM
27
Lecturer, teaching web technologies to students
5/15/2013 1:58 PM
28
JavaScript Developer
5/15/2013 1:51 PM
#
Other (please specify)
Date
W3C Site Redesign Survey
3 / 37
34.08%
76
19.73%
44
21.97%
49
12.56%
28
3.59%
8
5.38%
12
0.90%
2
50.22%
112
Q2
What types of groups do you
participate in? (select all applicable)
Answered: 223
Skipped: 4
0%
20%
40%
60%
80%
100%
Working Group
Interest
Group
Community
Group
Business
Group
Advisory
Board
Advisory
Committee
TAG
None (We will
ignore other
selections...
Working Group
Interest Group
Community Group
Business Group
Advisory Board
Advisory Committee
TAG
None (We will ignore other selections if you choose this
option.)
Total Respondents:
Total Respondents:
223
223
Answer Choices
Responses
W3C Site Redesign Survey
4 / 37
6.67%
15
9.33%
21
8.89%
20
2.67%
6
81.78%
184
Q3
What roles (if any) do you have
within a W3C group?
Answered: 225
Skipped: 2
Chair
Team contact
Editor
Test manager
None (We will ignore other selections if you choose this
option.)
Total Respondents:
Total Respondents:
225
225
Answer Choices
Responses
W3C Site Redesign Survey
5 / 37
90.91%
30
9.09%
3
Q4
Would you find it useful if W3C
were to provide templates for group
home pages (e.g,. to provide a
consistent user experience across
groups, and to automate some WG
tasks)?
Answered: 33
Skipped: 194
0%
20%
40%
60%
80%
100%
Yes
No
Yes
No
Total
Total
33
33
Answer Choices
Responses
W3C Site Redesign Survey
6 / 37
75.76%
25
24.24%
8
Q5
Do you think it would be useful
to distinguish a group's "public"
home page (for visitors) from its
"operations" home page (which
would also be public, but focus on
meeting details, etc.)?
Answered: 33
Skipped: 194
0%
20%
40%
60%
80%
100%
Yes
No
Yes
No
Total
Total
33
33
Answer Choices
Responses
W3C Site Redesign Survey
7 / 37
Q6
If we were to separate the two
pages, what information would you
put on the group's "public" home
page vs. its public "operations"
home page?
Answered: 19
Skipped: 208
#
Responses
Date
1
"Public" page: Goals of the group, current status, members, external links (related tutorials, blog
posts, etc.)
5/22/2013 11:55 PM
2
public link to public specification and to information related to public
operations meeting agenda,
teleconf (if not public), charter, deadlines, etc, current drafts
5/22/2013 6:54 AM
3
operations: internal communication channels, F2F details, issue tracker, etc.
public: everything else
5/22/2013 6:14 AM
4
public relations issues, it wll also be private to an extent only pertaining to
it' s group of people
knowledgeable to one skill.
5/18/2013 5:42 PM
5
Outline and links
5/18/2013 8:36 AM
6
public:
very basic information about the group (name, why it exists, what it does)
operations:
current
projects, membership
5/17/2013 8:13 AM
7
public: brief description of what the group does, news, announcements, links to specs and other
resources, esp educational, milestone overview operations: work in progress, charter, meetings,
archives, participants, how to join, patent policy
Note that I would rather see 'public' pages as an
aggregation of all WGs in an Activity - not one per WG!
5/16/2013 8:58 AM
8
This is a dumb question. There is no reason grops should ahve only two pages. history of drafts,
minutes, details of upcoming meetings, future of work, all these things are important. So there
5/16/2013 4:08 AM
9
more examples and complex sextion videos
5/16/2013 1:39 AM
10
What's the group for, what are its deliverables, what has it delivered, current work status, links to work
output
vs
Meeting logistics, Good Standing status etc.
5/16/2013 12:14 AM
11
on the public page you should include some basic information about the group alongside bigger
group events, whilst the more nitty gritty stuff would be on the operations page.
5/15/2013 10:59 PM
12
On the public "operations" home page: administrative information, logistics information, process and
guidebook links, etc.
On the "public" homepage without "operations" parts: how to join de group,
current work, work habits (how often group meets, where to find minutes, etc.), etc.
5/15/2013 6:37 PM
13
(quick thoughts -- not going over all the ones I maintain -- this is Sandro)
I'm split about whether there
should be a split.
I do think people in the WG need info that would be noise to the public, but ideally it
can be there, somewhat hidden, available for anyone who wants it -- in the WG or not.
public-facing:
public side of the document roadmap:
what drafts the public should review
past/expected versions of
those drafts
easy links to issues/comments
weekly news (which is probably just decisions scheduled
for the next meeting and made at the last one -- unless the chair is willing to write something)
charter
membership - who is in the group
how to get involved
group-facing:
more detailed version of
document roadmap:
include action items
who needs to review what by when
comment tracking
recent and upcoming meetings
links to relevant pages & tools, eg ReSpec if the group uses ReSpec
links to internal discussion documents
5/15/2013 5:53 PM
14
Home page: summary of group charter and purpose, date established, end date, summaries of main
deliverables and status, links to meeting minutes, actual charter, actual deliverables, main contacts
and chairs. Operations: Account of meeting schedule and other logistics,
5/15/2013 5:36 PM
15
Public: news, specs, feedback, short blurb, contact people (team and chair) Operations: everything
else
5/15/2013 4:38 PM
16
Public: overview, how to get involved for newbies,
Operations: minutes, mailing lists, meeting times,
Both (via db/includes?):currently active documents and drafts
5/15/2013 3:43 PM
17
The public home page would be easy to consume - general info.
The operations page would involve
much more technical and detailed information.
5/15/2013 3:43 PM
W3C Site Redesign Survey
8 / 37
18
They are already separate today.
5/15/2013 3:33 PM
19
First of all, in response to the yes / no questions previously asked, it is only useful to provide
templates if they meet the needs of the WG. If they don't leave room for critical information or have
feature problems, I can't use them.
Public: mission of the group, links to TR and editors' drafts,
participants list, how to join
Operations: how to join (again), meeting information (telecon and FtF),
minutes links, infrastructure pointers (wiki, tracker, WBS URL, etc.)
5/15/2013 2:20 PM
#
Responses
Date
W3C Site Redesign Survey
9 / 37
15.96%
34
84.04%
179
Q7
Do you work for a W3C Member?
Answered: 213
Skipped: 14
0%
20%
40%
60%
80%
100%
Yes
No
Yes
No
Total
Total
213
213
Answer Choices
Responses
W3C Site Redesign Survey
10 / 37
0%
0
11.11%
3
29.63%
8
29.63%
8
11.11%
3
14.81%
4
3.70%
1
Q8
How often do you visit the
Member home page?
Answered: 27
Skipped: 200
0%
20%
40%
60%
80%
100%
Daily
Weekly
Monthly
A few times a
year
I have never
visited the
Member hom...
I have never
visited the
Member hom...
Other (please
specify)
Daily
Weekly
Monthly
A few times a year
I have never visited the Member home page.
I have never visited the Member home page and didn't even
know there was one!
Other (please specify)
Total
Total
27
27
#
Other (please specify)
Date
1
I have apparently visited the Member homepage but didn't recall it
5/15/2013 3:46 PM
Answer Choices
Responses
W3C Site Redesign Survey
11 / 37
Q9
What features or improvements
would you most like to see on a
Member home page?
Answered: 9
Skipped: 218
#
Responses
Date
1
More clarity in the design. Less cruft. More focus.
5/22/2013 6:16 AM
2
As I haven't used it, I have no features or improvements to suggest.
5/20/2013 6:44 AM
3
Usability
5/17/2013 5:15 PM
4
The member home page is a good jumping point to a number of useful services. I quite like it as it is.
5/17/2013 2:53 AM
5
Stuff about my organisation's participation (who, what groups, how to join/leave a new group)...
but
MOST IMPORTANTLY integrate the Community Group stuff better, PLEASE PLEASE PLEASE.
5/16/2013 4:13 AM
6
Activity graph of each WG/IG/BG.
5/15/2013 10:13 PM
7
Generally, like the site. Would like a way to easily find member names, roles, company, from the main
page.
5/15/2013 5:47 PM
8
The site needs a full redesign. It's current organization is somewhat chaotic and it's normally difficult to
find the information you're looking for. A full refresh of it's "look". In general, the site looks like websites
used to look 15 years ago.
5/15/2013 4:55 PM
9
some (gasp) personalization: items relevant to your WGs, such as... those described below...
5/15/2013 3:46 PM
W3C Site Redesign Survey
12 / 37
68.42%
13
31.58%
6
Q10
Should the Member home page
become a customized “dashboard”
with information or links specific to
you, such as: identity (name,
affiliation), lists of group
membership with your organization,
etc.?
Answered: 19
Skipped: 208
0%
20%
40%
60%
80%
100%
Yes
No
Yes
No
Total
Total
19
19
Answer Choices
Responses
W3C Site Redesign Survey
13 / 37
66.67%
12
50%
9
33.33%
6
11.11%
2
38.89%
7
22.22%
4
11.11%
2
Q11
What sections of the Member
site do you most use?
Answered: 18
Skipped: 209
0%
20%
40%
60%
80%
100%
Calendar of
Member Events
Member
Actions,
News, Mail...
Process,
Patent
Policy,...
Member
Standards
Promotion
Membership
Administrivia
List of AC
Reps
Staff FTE
tables
(summarize...
Calendar of Member Events
Member Actions, News, Mail, Discussion
Process, Patent Policy, Finances Guide
Member Standards Promotion
Membership Administrivia
List of AC Reps
Staff FTE tables (summarized by activity)
Total Respondents:
Total Respondents:
18
18
Answer Choices
Responses
W3C Site Redesign Survey
14 / 37
Q12
What information have you had
difficulty finding on the Member
site?
Answered: 10
Skipped: 217
#
Responses
Date
1
pretty much everything is hard to find unless you know exactly where it is.
5/22/2013 6:16 AM
2
Haven't used any
5/20/2013 6:44 AM
3
When and Which spec will be update(including progress)
5/19/2013 7:15 PM
4
There used to be a way to see details of my member's contract and so on. The resource at
http://www.w3.org/Systems/db/viewMembership now redirects to
https://www.w3.org/2004/12/accounts-management/ which is also a useful page, but not the one I
want.
5/17/2013 2:53 AM
5
Almost everything I have ever looked for. It has improved, but the improvements provided some jarring
readjustments.
5/16/2013 4:13 AM
6
It took a time to find which groups I and my companies colleagues are joining.
5/15/2013 10:13 PM
7
Members names and info from each member company.
5/15/2013 5:47 PM
8
information about my current contract, current Member dues, billing contact.
5/15/2013 5:40 PM
9
open issues/actions/polls
5/15/2013 3:46 PM
10
future ac meetings - the link to ac meetings goes to a page that only talks about historical data.
5/15/2013 3:34 PM
W3C Site Redesign Survey
15 / 37
Q13
What features or improvements
would you most like to see in the
Member site (other than to the
Member home page) in the future?
Answered: 5
Skipped: 222
#
Responses
Date
1
I think that the possibility of a customized "dashboard" (question 7) would be very useful.
5/20/2013 6:44 AM
2
Make requesting an account for someone, and adding them to a group, a less confusing experience.
5/16/2013 4:13 AM
3
n/a
5/15/2013 5:47 PM
4
A real membership viewer: current one has not worked for a good while.
5/15/2013 5:40 PM
5
"do my work for me"
5/15/2013 3:46 PM
W3C Site Redesign Survey
16 / 37
15.79%
3
26.32%
5
36.84%
7
21.05%
4
Q14
Because much information
useful to Members exists on the
public site, please indicate how
important it is to you to access that
information directly from the
Member site?
Answered: 19
Skipped: 208
0%
20%
40%
60%
80%
100%
Essential
Important
Somewhat
Useful
Not useful
Essential
Important
Somewhat Useful
Not useful
Total
Total
19
19
Answer Choices
Responses
W3C Site Redesign Survey
17 / 37
Q15
Which links to the public site
are most important for you to find
from the Member site?
Answered: 4
Skipped: 223
#
Responses
Date
1
As a member, I don't make a distinction between the member site and the public site. For me, all of
this is the same, with slightly annoying password requests from time to time. I do not know when I'm
on the member site and when I'm not.
5/22/2013 6:16 AM
2
Access to drafts, minutes... associated with my activities.
5/20/2013 6:44 AM
3
I don't care where I find them from. With a fair idea of what is public, I just use Yandex to find public
resources, so I only look for member resources from the member site :(
5/16/2013 4:13 AM
4
mailing lists, WG homepages, WG join information
5/15/2013 3:46 PM
W3C Site Redesign Survey
18 / 37
7.47%
13
31.61%
55
24.14%
42
32.18%
56
2.30%
4
2.30%
4
Q16
How often do you visit the W3C
home page?
Answered: 174
Skipped: 53
0%
20%
40%
60%
80%
100%
Daily
Weekly
Monthly
A few times a
year
I have never
visited the
W3C home page
Other (please
specify)
Daily
Weekly
Monthly
A few times a year
I have never visited the W3C home page
Other (please specify)
Total
Total
174
174
#
Other (please specify)
Date
1
Never visited the home page, visited certain specs through doing google searches though.
5/16/2013 3:00 AM
2
Unclear whether you refer to the start page only or pages below it. If the lattter, weekly to daily (mainly
to answer to surveys).
5/16/2013 1:31 AM
3
as needed
5/15/2013 3:35 PM
4
I visit parts of the site at least monthly, more if doing an accessiblity proejct
5/15/2013 3:23 PM
Answer Choices
Responses
W3C Site Redesign Survey
19 / 37
44.94%
71
36.71%
58
15.82%
25
4.43%
7
54.43%
86
77.85%
123
1.27%
2
Q17
What features/information do
you use on the current home page?
Answered: 158
Skipped: 69
0%
20%
40%
60%
80%
100%
News
W3C blog
Talks and
Events
Links to jobs
Links to
validators
Links to
standards and
other...
Member
testimonial
News
W3C blog
Talks and Events
Links to jobs
Links to validators
Links to standards and other materials
Member testimonial
Total Respondents:
Total Respondents:
158
158
Answer Choices
Responses
W3C Site Redesign Survey
20 / 37
Q18
What features or improvements
would you most like to see on the
public home page?
Answered: 45
Skipped: 182
#
Responses
Date
1
Better organization. Less clutter. Clearer actionable things to do depending on the audience.
5/22/2013 6:17 AM
2
easier access to standard documents
5/20/2013 10:33 AM
3
None
5/20/2013 6:44 AM
4
Progressive Disclosure. Not sure that the chronological listing of news should be the dominentn
means of representing info.
5/19/2013 7:33 AM
5
Improve readability, usability, look and feel of specs
5/19/2013 6:45 AM
6
Responsive design would be great!
5/18/2013 11:17 AM
7
I'm not terribly invested in the home page--it's just one more way, on top of my browser bookmarks
and Google, to get me to the content I'm seeking.
The better it can do that the happier I am.
5/17/2013 9:51 AM
8
Better accessibility!
5/17/2013 6:30 AM
9
Better, cleaner way to get to specification.
5/17/2013 3:55 AM
10
Documentation
5/16/2013 9:38 PM
11
I've never used the home page
5/16/2013 4:48 PM
12
Less content and more white space
5/16/2013 2:28 PM
13
direct links to most popular standards
5/16/2013 11:48 AM
14
A more structured index of materials and documents.
5/16/2013 9:19 AM
15
easier to find things - the 'standards' links are useful for exploring randomly, or for newcomers, but
often a pain if you want to find something quickly without trying to guess which bucket the link sits in
5/16/2013 9:01 AM
16
A good overview for all news/blog feeds.
5/16/2013 8:16 AM
17
Note: What I use normally is the search field. But it is not in the item before.
5/16/2013 6:22 AM
18
A tailored specification search would be useful. Right now, when I enter “CSS” in the Google search
box at the top, I get mostly irrelevant stuff, hard to sift through. Instead I would like to see a clear,
preferably short, list of relevant specifications, ordered and colored by their status (Rec → ... → WG
Note) etc. Other, non-spec hits could be listed further below.
5/16/2013 6:05 AM
19
Visual design, easier way to help and participate.
5/16/2013 5:42 AM
20
More advertising of the members :) (Plus whatever the people who do use it want)
5/16/2013 4:14 AM
21
A cleaner interface, easier to navigate to key parts of the website.
5/16/2013 3:00 AM
22
More document translated
5/16/2013 2:09 AM
23
standards news
5/16/2013 1:40 AM
24
The home page itself is pretty unimportant for me.
5/16/2013 1:31 AM
25
better search feature. Better API Declaration like Java API style.
5/16/2013 1:10 AM
26
I guess it would be useful if the home page were a better navigational starting point for the work of the
W3C
5/16/2013 12:15 AM
27
Better design to improve usability. Quick links to spec reference.
5/15/2013 11:36 PM
28
information on how to get involved with w3c
5/15/2013 11:03 PM
29
an overall more updated look, maybe a little less busy
5/15/2013 11:01 PM
W3C Site Redesign Survey
21 / 37
30
Having quicker access to references would be nice. Maybe have a reference guide you can download
or make into an app for each language.
5/15/2013 10:57 PM
31
less stuff.
5/15/2013 8:23 PM
32
make it easier to find relevant specifications.
If I go to the home page looking for the HTML5 spec, I
have to click View All (because I don't know which category is best), HTML, and scroll waaaaay down to
HTML5).
Do you look at your analytics and see what pages your visitors are flocking to?
It seems to me
that this would be one of the hottest topics right now... why aren't there quick and obvious links above
the fold on the home page to the hottest topics?
5/15/2013 7:50 PM
33
A more readable website. Especially the standards/working draft areas. Please use a reasonable
measure (width) for reading.
5/15/2013 6:29 PM
34
It makes me a little uncomfortable that the W3C uses google for an enterprise search engine.
5/15/2013 6:28 PM
35
More linking to education materials
5/15/2013 5:56 PM
36
Would like to discover Interest Groups easily.
5/15/2013 5:49 PM
37
Finding specs, with a strong focus on the browser ones. Finding groups, most importantly to provide
feedback.
5/15/2013 4:39 PM
38
the groupings under "standards" seem rather random. What's the difference between "News" and
"Blog" and why are they two?
5/15/2013 3:49 PM
39
publication status/progress.
5/15/2013 3:44 PM
40
Being powered by RichStyle framework: http://richstyle.org
5/15/2013 3:32 PM
41
Some tutorial on Web Standard. Web Technology Usage.
5/15/2013 3:27 PM
42
Better orientation. Better Design - also for the standards section.
5/15/2013 2:45 PM
43
Quick references to standards, preferably with a handy index like the one for CSS 2. W3schools have
great references, but sometimes you want more information and really want to read what the
standards document says about, for example, a specific HTML-tag in a specific version of HTML.
5/15/2013 2:25 PM
44
Stop hiding content with scripts that slow down my browser and make it harder to get to the content I
care about. It is a real art to find content now when I'm looking for something in particular. Really a
problem on the TR pages, but the organization into "buckets" that mean different things than my own
mental categorizations, and not enough cross-links between them, makes it really hard to find stuff.
5/15/2013 2:22 PM
45
A list of links to the current W3C recommendations of the most important technologies (HTML, CSS,
XML, XSLT etc.), sorted by frequency of use
5/15/2013 2:00 PM
#
Responses
Date
W3C Site Redesign Survey
22 / 37
Q19
When considering adjustments
to the style for W3C Standards and
Drafts (e.g. CSS Media Queries),
please rate the following in terms of
importance to you:
Answered: 123
Skipped: 104
0
1
2
3
4
5
Better
Typography
Narrower
column width
Less status
information
up front
Clearer
indication
when docum...
Clearer
indication of
document...
Integration
with related
materials...
Tools for
making it
easier to...
Other
Better
Typography
34.71%
42
28.10%
34
27.27%
33
9.92%
12

121

2.12
Narrower
column width
17.50%
21
24.17%
29
33.33%
40
25%
30

120

2.66
Less status
information
up front
10.43%
12
24.35%
28
50.43%
58
14.78%
17

115

2.70
Clearer
indication
when
document has
been
superseded
36.67%
44
45%
54
14.17%
17
4.17%
5

120

1.86
Clearer
indication of
document
maturity (on
the
recommendation
track)
34.71%
42
45.45%
55
15.70%
19
4.13%
5

121

1.89
Integration
with related
materials
(tests,
developer
documentation,
etc.)
33.06%
40
42.98%
52
19.83%
24
4.13%
5

121

1.95

Essential
Important
Somewhat
Useful
Not Useful
Total
Average Rating
W3C Site Redesign Survey
23 / 37
Tools for
making it
easier to
review and
comment on a
specification
29.75%
36
35.54%
43
28.93%
35
5.79%
7

121

2.11
Other
20.69%
6
17.24%
5
13.79%
4
48.28%
14

29

2.90
Please specify other feature of importance.
(

17
)
#
Please specify other feature of importance.
Date
1
"Jump to" links to example code (if applicable)
5/22/2013 11:58 PM
2
more practical examples on each item(element,attribute,object,method,property etc.)
5/20/2013 10:40 AM
3
Links to related / competing standards
5/18/2013 8:38 AM
4
multiple page for documentation, rather than a long text
5/16/2013 9:43 PM
5
Easier navigation and better organization on documents
5/16/2013 4:51 PM
6
More white space and much clearer visibility of headings and heading levels.
5/16/2013 9:09 AM
7
Offer a way to get a "current version" link when being on the latest document (without any date in the
URL)
5/16/2013 8:20 AM
8
Quick links to document headings (e. g. appearing upon hover).
5/16/2013 6:06 AM
9
Mobile interface
5/16/2013 1:37 AM
10
It's hard to say. In general W3C specifications are not intended for public consumption - i.e. they are
not tutorial in intent, are they?
5/16/2013 12:17 AM
11
That matrix is extremely leading — a statician would have your head. Sounds like you already decided
what you want to work on, but they're good choices :)
5/15/2013 11:40 PM
12
easier to extract different views of the same document.
5/15/2013 8:27 PM
13
less circular jumping around in standards documents... I can't tell you how many times I've clicked on a
link to learn more about a keyword or topic, only to be taken to the heading for the topic that I'm
already looking at, or a passing reference to the same topic that again links to nowhere useful.
It's like
you're filling the page with links for improved SEO that doesn't actually benefit the user,
5/15/2013 7:54 PM
14
printability
5/15/2013 3:52 PM
15
Terminology
5/15/2013 3:39 PM
16
Abstract begins on 2nd page, content on 4th. That's a lot. Info about versions and TOC could occupy
less space, be a column, have bypassing links, etc
5/15/2013 3:36 PM
17
Stop hiding things under expandos and different views of the page that force me to go through
several steps to find a particular document.
5/15/2013 2:23 PM
W3C Site Redesign Survey
24 / 37
45.05%
41
51.65%
47
13.19%
12
3.30%
3
Q20
Which filter options on the
Standards and Drafts index do you
use most frequently?
Answered: 91
Skipped: 136
0%
20%
40%
60%
80%
100%
All
Standards
only
Drafts only
Review
opportunities
All
Standards only
Drafts only
Review opportunities
Total Respondents:
Total Respondents:
91
91
Answer Choices
Responses
W3C Site Redesign Survey
25 / 37
57.32%
47
34.15%
28
29.27%
24
21.95%
18
21.95%
18
1.22%
1
Q21
Which sorting options on the
Standards and Drafts index do you
use most frequently?
Answered: 82
Skipped: 145
0%
20%
40%
60%
80%
100%
Technology
Status
Date
Title
Working/Inter
est Group
Editor
Technology
Status
Date
Title
Working/Interest Group
Editor
Total Respondents:
Total Respondents:
82
82
Answer Choices
Responses
W3C Site Redesign Survey
26 / 37
Q22
Do you have any
recommendations for the Standards
and Drafts index?
Answered: 18
Skipped: 209
#
Responses
Date
1
No clue what it is.
5/22/2013 6:19 AM
2
No
5/20/2013 6:46 AM
3
Do the sorting, filtering and ordering in the client side. At least make it auto-submit when changing a
dropdown menu. Clicking "Show View" is tedious.
5/16/2013 9:19 AM
4
Take up less space when with the revealed content when you click on something, and put the
revealed information to the side, somehow, so that it's easy to click on other things.
5/16/2013 9:09 AM
5
Don't break it please :)
5/16/2013 4:15 AM
6
make it hypermedia (HATEOAS) friendy by adding a few rels here and there so we could basically write
a client exploring the data autonomously.
5/15/2013 8:27 PM
7
I didn't know the “current status” pages existed, but now that I do, I'll refer to them. They're wicked
useful.
5/15/2013 6:42 PM
8
more padding.
5/15/2013 6:31 PM
9
I stopped using it when you redesigned it to hide all the content.
Before that, I could just search for
what I needed.
Now I can't find anything so I just use Google and or guess /TR/ names.
5/15/2013 5:57 PM
10
pretty good as-is.
5/15/2013 5:51 PM
11
I almost never use it.
5/15/2013 4:42 PM
12
add a title search and full-text search
5/15/2013 3:52 PM
13
Show only Recs by default
5/15/2013 3:38 PM
14
Use of color for status(es) would be a nice improvment. Adding faceted search, considering the
different criters (date, WG, status, others?).
5/15/2013 3:36 PM
15
No
5/15/2013 3:29 PM
16
All the standards should be visible at once, rather than collapsed after the page loads.
5/15/2013 3:19 PM
17
I hate the above filtering and sorting options as they just slow me down.
5/15/2013 2:23 PM
18
See previous comment
5/15/2013 2:02 PM
W3C Site Redesign Survey
27 / 37
47.97%
59
5.69%
7
46.34%
57
Q23
Are the “current status” pages
useful (e.g. CSS Current Status)?
Answered: 123
Skipped: 104
0%
20%
40%
60%
80%
100%
Yes
No
I didn't know
they existed.
Yes
No
I didn't know they existed.
Total
Total
123
123
Answer Choices
Responses
W3C Site Redesign Survey
28 / 37
38.14%
45
10.17%
12
51.69%
61
Q24
Are the labels for groups of
reports on the Standards and Drafts
index useful?
Answered: 118
Skipped: 109
0%
20%
40%
60%
80%
100%
Yes
No
I didn't know
they existed.
Yes
No
I didn't know they existed.
Total
Total
118
118
Answer Choices
Responses
W3C Site Redesign Survey
29 / 37
92.74%
115
53.23%
66
33.87%
42
74.19%
92
70.97%
88
Q25
Why do you visit the W3C site?
Check all that apply.
Answered: 124
Skipped: 103
0%
20%
40%
60%
80%
100%
Find W3C
specification
s
Find out
whether
something ...
Find how well
a
specificat...
HTML elements
and
attributes
CSS
properties
and values
Accessibility
Guidelines
Working Group
News
Overview of
current W3C
work relev...
How to
participate
in W3C
How to become
a W3C Member
List of W3C
Members
Learn about
the Web
W3C validator
Test suites
Tutorials
Other (please
specify)
Find W3C specifications
Find out whether something is a Recommendation
Find how well a specification is implemented in browsers and
other software
HTML elements and attributes
CSS properties and values
Total Respondents:
Total Respondents:
124
124
Answer Choices
Responses
W3C Site Redesign Survey
30 / 37
45.16%
56
29.03%
36
12.10%
15
11.29%
14
9.68%
12
16.13%
20
23.39%
29
63.71%
79
23.39%
29
27.42%
34
8.06%
10
Accessibility Guidelines
Working Group News
Overview of current W3C work relevant to a given industry
(e.g,. automotive, digital publishing)
How to participate in W3C
How to become a W3C Member
List of W3C Members
Learn about the Web
W3C validator
Test suites
Tutorials
Other (please specify)
Total Respondents:
Total Respondents:
124
124
#
Other (please specify)
Date
1
"Find how well a specification is implemented in browsers and other software" I wish
5/18/2013 8:39 AM
2
Update my account password.
5/16/2013 6:10 AM
3
administrative stuff, to look up things in specs
5/16/2013 4:17 AM
4
Usually I visit the specifications via Google, if I want to look something up
5/16/2013 12:20 AM
5
w3schools, if that's official, haven't checked
5/15/2013 11:02 PM
6
more narrative about what is happening at W3C in the WG lifes on the blog, more quick tips of
technology on the blog, etc.
5/15/2013 8:30 PM
7
Review Editor drafts, see issues lists, see who is in a WG, see minutes,
5/15/2013 5:59 PM
8
mailing lists, community groups
5/15/2013 4:43 PM
9
to find the process document and patent policy
5/15/2013 3:54 PM
10
team page :)
5/15/2013 3:40 PM
W3C Site Redesign Survey
31 / 37
Q26
What features or improvements
would you most like to see in the
future on the public site (other than
on the public home page)?
Answered: 25
Skipped: 202
#
Responses
Date
1
Consistency of design across the different properties, e.g. front page, specification pages, members'
pages, community/business group pages.
5/22/2013 11:59 PM
2
Better site map. More up to date content.
5/22/2013 6:20 AM
3
None
5/20/2013 6:47 AM
4
Just keep making it easy to find on Google.
5/17/2013 9:54 AM
5
Documents as courses. A platform of e-learning
5/16/2013 9:45 PM
6
- Better navigation and organization for documents, so that information relevant to web developers
and browser developers are separated - Links to collaborate with the documents
5/16/2013 4:53 PM
7
Though the site isn't doing it yet, the survey shows that you're considering having abstracted
documention for HTML/DOM/CSS features (e.g. individual easy-to-use pages for css properties, DOM
javascript methods etc.). Those are currently well-handled by MDN and others and there is currently a
big movement going on in centralising/merging all these to WebPlatform.org. I'd highly recommend
W3.org either continue to not do this, or do so in very-tight partnership and collaboration with
WebPlatform to avoid duplication of efforts.
5/16/2013 9:23 AM
8
Examples & templates
5/16/2013 6:16 AM
9
Some sections, like [1], are still empty with embarrasing boilerplate text. I even wrote some text [2]
ages ago, but nothing changed. This is just a minor pet peeve though.
[1]
http://www.w3.org/standards/webarch/identifiers [2] http://lists.w3.org/Archives/Public/site-
comments/2011Oct/0007.html
5/16/2013 6:10 AM
10
better organisation of the site architecture itself. Without breaking old links.
5/16/2013 4:17 AM
11
A better designed tool for surveys, issues, puiblic comments (the fields to propose answers to issues
and just contribute to discussion are not terrribly clear). A good part of that system however is
timeliness of responses which I guess is down to human resources available.
5/16/2013 1:36 AM
12
In general it seems the site is inward looking (it explains things in terms of how the W3C happens to
be organised) vs outward looking (what might possible visitors be interested in)
5/16/2013 12:20 AM
13
Revise the drafts/spec sections to be as useful as sites like html doctor/ dochub.
5/15/2013 11:40 PM
14
a live code editor like the one on squarefree would be nice
5/15/2013 11:02 PM
15
I never had any idea you guys had any of the above besides the ones I checked. I used it more for a
reference. Make people make a profile and/ or give them a visual walk through of all you have to offer. I
hate reading by the way.
5/15/2013 11:01 PM
16
* Better mailing list archive system * Better blog, responsive with more information for developers.
5/15/2013 8:30 PM
17
easier to find what i'm looking for.
5/15/2013 7:55 PM
18
Visually I wish that the WAI subsite integrated better with the W3 home page
5/15/2013 6:35 PM
19
A good view of all the specs at all maturity levels, clearly showing how stable and deployed they are.
5/15/2013 5:59 PM
20
A more attractive blog (the improvements proposed for the specs, or even the current spec design, is
much more readable than the current blog)
5/15/2013 3:54 PM
21
Consistency! I always feel like every part of W3C site has its own spirit.
5/15/2013 3:45 PM
22
I was going to talk about the CSS validator (the HTML one is fine), but it seems it has (finally!) been
improved. No options to ignore things like zoom:1 or proprietary -webkit- stuff but it seems way better
than a few months, at first glance. Maybe I'll use it again :)
5/15/2013 3:43 PM
W3C Site Redesign Survey
32 / 37
23
It's a mess today - we didn't have the resources to implement the last redesign completely. So, better
navigation & consistency.
5/15/2013 3:40 PM
24
Blog Contribution.
5/15/2013 3:29 PM
25
Remove the scripts that enforce a certain view of how I should interact with the site, and make better
use of CSS features that allow flexible layout and accommodate to my needs.
5/15/2013 2:24 PM
#
Responses
Date
W3C Site Redesign Survey
33 / 37
35.96%
41
64.04%
73
Q27
Is the site map useful to you?
Answered: 114
Skipped: 113
0%
20%
40%
60%
80%
100%
Yes
No
Yes
No
Total
Total
114
114
Answer Choices
Responses
W3C Site Redesign Survey
34 / 37
Q28
What do you find useful about
the site map?
Answered: 16
Skipped: 211
#
Responses
Date
1
easier access to any Working Group
5/20/2013 10:44 AM
2
site navigation
5/18/2013 8:39 AM
3
Detailed
5/16/2013 10:53 AM
4
Quick links. However, not so good that you don't always know what's actually at the other end -
sometimes spec, sometimes WG home pages, sometimes something other unexpected
5/16/2013 9:13 AM
5
It gives a good overview and it's easy to find the section you are after quickly.
5/16/2013 6:25 AM
6
Information, but sometimes is hard to find it
5/16/2013 6:19 AM
7
ordered by nesting, but also alphabetically ordered linklist, like a glossary.
5/16/2013 3:54 AM
8
a-z
5/16/2013 2:30 AM
9
Never used it.
5/16/2013 1:37 AM
10
faster navigation to pages i use frequently
5/15/2013 11:03 PM
11
I can search text in it, or read through the list and find stuff.
5/15/2013 6:45 PM
12
It makes it clear how the W3C thinks of its different arms.
5/15/2013 6:36 PM
13
Categories
5/15/2013 5:53 PM
14
that it exists
5/15/2013 3:54 PM
15
ability to visualize structure/ia, ability to verify naming conventions.
5/15/2013 3:49 PM
16
Useful to discover unknown pages/specs
5/15/2013 2:51 PM
W3C Site Redesign Survey
35 / 37
Q29
What information have you had
difficulty finding on the W3C site?
Answered: 34
Skipped: 193
#
Responses
Date
1
Simplified versions of the specs - e.g. for HTML5, what status it is, a list of valid elements and
attributes, without having to read through lots of administrative introductions and words such as
"conformance", "normative", etc.
Specs related to the one I'm currently reading. There should be a
navigation bar, sub-menu or something similar.
5/23/2013 12:08 AM
2
From google search - trying to find up to date accessibility standards and recommendations. This is
what I use the site for 90% of the time
5/22/2013 6:37 AM
3
Pretty much everything.
5/22/2013 6:20 AM
4
specifications
5/20/2013 10:44 AM
5
None
5/20/2013 6:48 AM
6
What is where... no 'index'
5/18/2013 8:39 AM
7
different wgs differ in how much uptodate info they have
5/18/2013 12:58 AM
8
It's difficult for me to find usage examples that explain well the purpose of a specification and how to
use it. Information is highly technical and this is important, but should not be the first thing an user
sees.
5/16/2013 4:56 PM
9
diffs between HTML 5, HTML 5.1, 5.2 and so on
5/16/2013 11:50 AM
10
The actual specifications and unit tests for these. Once you know where to look for the specifications
it becomes easier but I find myself going to spec.whatwg.org instead because it is much easier to find
and a better starting point. Granted, of course, over there is much less content to have to organize
(only a handful of specifications, and only the latest drafts of these).
And as for unit tests, I still haven't
found them. I know whatwg/w3 has some kind of web-app tests domain somewhere but last time I
was able to find it, it was mostly a dump of html/js files organised by username who submitted it. Not a
well-maintained or complete test suite.
5/16/2013 9:27 AM
11
Specifications
5/16/2013 9:13 AM
12
All things.
5/16/2013 8:15 AM
13
Finding the right sections in the CSS 3 documents.
5/16/2013 6:25 AM
14
When you are looking for specifics answers to a concrete question.
5/16/2013 6:19 AM
15
Specifications.
5/16/2013 6:11 AM
16
Pretty much everything except specs and stuff I don't care about (job ads, PR announcements, ...)
5/16/2013 4:18 AM
17
most current version of a standard, usage advisory
5/16/2013 2:30 AM
18
Mostly using Google search to go straight to what I know exists in the site.
5/16/2013 1:37 AM
19
It's not what I have trouble finding, it's what I come here for. Just for the dry specs/drafts.
5/15/2013 11:41 PM
20
none
5/15/2013 11:03 PM
21
Difficult navigation around references. I usually use the google search at the top for what I need.
Should have it in the page with suggestions on what you are looking for instead of turning up
numerous results.
5/15/2013 11:02 PM
22
historical information, there is a maze of things, but they are not easy to find without prior knowledge.
5/15/2013 8:32 PM
23
current specifications, detailed explanations of properties and especially their values in CSS, various
others.
5/15/2013 7:56 PM
24
examples
5/15/2013 7:02 PM
25
Editors drafts, minutes, meeting status (when/where/cancelled?)
5/15/2013 6:00 PM
26
About affiliation
5/15/2013 5:58 PM
W3C Site Redesign Survey
36 / 37
27
none
5/15/2013 5:53 PM
28
Mostly documentation about how various things are done.
Pretty much anything in dated space.
5/15/2013 4:44 PM
29
WG participation, by WG or by Member
5/15/2013 3:54 PM
30
Quick reference for standards.
5/15/2013 3:47 PM
31
Translations of Understanding WCAG 2.0 in french did exist and I didn't know about it because the
prior translated document (WCAG 2.0 REC itself) doesn't link to the newer french document. Meh.
5/15/2013 3:46 PM
32
Almost everything. Follow your own guidelines about clarity of headlines, showing status, and defining
technical language.
5/15/2013 3:25 PM
33
How to participate, tools to accomplish certain WG tasks, information about a particular WG if I don't
already know where to look.
5/15/2013 2:25 PM
34
Finding the current recommended version of common web standards (HTML, CSS etc.)
5/15/2013 2:03 PM
#
Responses
Date
W3C Site Redesign Survey
37 / 37
Q30
Please rate the following
features of the W3C website:
Answered: 109
Skipped: 118
0
1
2
3
4
5
Usefulness of
Search
function
Ease of
navigation
Organization
of
information
Value of
content to
you
Usefulness of
Search
function
9.90%
10
30.69%
31
40.59%
41
18.81%
19

101

2.68
Ease of
navigation
4.63%
5
20.37%
22
38.89%
42
36.11%
39

108

3.06
Organization
of information
5.56%
6
29.63%
32
37.96%
41
26.85%
29

108

2.86
Value of
content to
you
44.04%
48
42.20%
46
11.01%
12
2.75%
3

109

1.72

Excellent
Pretty Good
Okay
Poor
Total
Average Rating