| Anchors underlined |
Do not underline a elements used as anchors only (i.e., that are not links) |
Fixed using a:link, a:visited selectors in minimum.css |
| Anchors bold |
Do not bold a elements used as anchors only (i.e., that are not links) |
Fixed using selectors in minimum.css |
| Style override inside anchors |
Ensure that a elements bold even when other
markup (e.g., cite) inside them |
Fixed adding selectors to minimum.css |
| Highlight current section (standards, participate, membership, about) |
[M]ain menu (STANDARDS etc.) is not highlighted when selecting a
certain section. If I'm in Participate the only way of me knowing that
is looking at the breadcrumb below (W3C > Participate) but the menu
should be highlighted too because you are showing me that on mouseover
anyway
|
We had that feature in an earlier version of the templates
but dropped it and wanted to see if anybody requested it.
Although the highlight provides a small bit of additional
orientation, the information "you are here" is available
in the breadcrumbs as well. |
| Underline links not bold |
Bold, no underline for links (except on hover) - hmmm. not sure this is a good idea because it prevents you using bold for emphasis. Would recommend underlining links (or border-bottom?). |
Done (in content). |
| Default text size |
Suggestion for font-size: 100%. |
Commenter refers to an
article which itself talks about the trade-offs between setting font-size to approximately 62.5% and leaving it at 100%. This is a known issue for which there are
multiple perspectives and experiences (and no easy answer). We consciously chose a base font size for the site in order to solicit feedback on this question.
Inclined to leave as-is / do more user testing. |
| Default text color |
Suggest black instead of #333. See another suggestion to not use grey on grey. |
Inclined to leave the softer #333 (noting that #333 on white is WCAG AAA). |
| Tags |
Tags/folksonomy - some cross-cutting themes via taggin would be great... also on-page comments? |
At the current time we've not chosen to implement this feature.
One reason is a resource consideration; the need to moderate
comments. Another is that for performance reasons the home pages
are "baked" HTML pages, increasing the cost of providing tagged
views. We do provide different views of information as follows:
- TR page views
- Groupings by large theme (e.g., "Web design"), although those pages
do not include home page news.
|
| Left-col shadow / 3-D effect |
The shadow effect on the left (e.g., main page)
looks really cheap if you ask me. There are no shadows on the other parts of
site, it might be worth removing this rudiment.
|
Done. |
| Permalink glyph |
Suggest something else, plus use an image rather than
unicode char |
Done. |
| Links under titles not obvious |
Several people have indicated that titles-as-links
are not obvious (though they display with an underline on hover).
One suggestion has been to make the links redundant; keeping
the title-as-link but adding one elsewhere in the content.
On bucket pages, a [More information] link was suggested,
followed by the status page links.
|
Links in content now underlined |
| X-UA-Compatible header |
The site could send the X-UA-Compatible header to ensure that IE8's
standards mode is used |
This is a non-standard header; hesitate to use it, especially
if IE8 is rendering the page acceptably. |
| left side nav disappears on top pages |
The contextual left nav shows on the homepage, but disappears on all
other landing pages, only to reappear when you click through from a
landing page to other content within the section. |
Have added left side nav for top four pages.
Note: Left-side navigation is for navigating among
siblings (not children). When on the top four pages
(standards, participate, membership, about) left side navigation
among those pages would be redundant with the top navigation,
so we've not shown them. The effect is that left side navigation
is there, then disappears, then re-appears. Other notes:
- The home page is different and features the main
standards subpages for each access
- On pages with no siblings, there's no left navigation bar
|
| reduce vertical space in top menu items when narrow browser |
Could some of the vertical space around the "STANDARDS," "PARTICIPATE," etc., links be moved from the boxes within the line that wraps to a box
outside that line? |
Couldn't do as suggested and keep vertical lines all the way to the horizontal bar below the menu items. Instead, reduced padding by 10px both above and below individual items. |
| left col should be proportional to screen |
At least make the width proportional to the page or viewport width so that
it doesn't take up a larger fraction of the horizontal space in windows that
are tall rather than wide.
|
Done |
| make left nav float to reuse space below it when empty |
Ideally, make the left navigation column into a float (or move it to something
at the top (e.g., such as a good (wrappable) form of tabs), so that that
the left-side space in the browser pane can be used to display part of the main
content once the user has scrolled down beyond the extent of the left-column
navigation content. (See also follow-up from Daniel)
|
Not done, but other changes will help in this area (see proportional layout, plus other organizational improvements to make better use of left space) |
| contact link top of every page |
As I am unable at times to use a mouse one thing that
really annoys me is when I have to tab my way all through a site to
get to the contact information. I strongly recommend that you include
a contact link at the top of the page as well as the bottom if you
want one there as well. Just beside the search function would be great.
|
We have "0" as an accesskey to "Help and FAQ". Also, if you follow "About W3C" we've put a contact link in the first paragraph. That's still not as fast as a direct link, I realize. Will propose accesskey=4 and see if this addresses use case. (No reply from reviewer)/td>
|
| Better left nav alignment |
Left navigation doesn't align with anything |
Changed left nav so that it behaves differently
on home page and non-home pages. We had wanted to avoid this
movement between pages, but given the general movement to large titles,
it may not be noticeable. Now there is better alignment on home pages
and better alignment on other pages, but the alignment is different from type to type. |
| Use max-width for text |
Design ok for regular screens/browsers, but I'd like to have max-width
applied - maybe in em - to prevent extremely long text lines. |
Added max-width of 65em for p, li. |
| Add "w3c" to title element |
For orientation, add some variation of "W3C" to end of
title elements that don't have W3C in them. |
Done |
| Use drop-down menus. |
People have suggested drop-down menus for both
left side navigation and top navigation. |
Currently we have not chosen to do this
(although this was part of an earlier draft of templates). |
| Search results page |
Invoking google directly means that the search results page
has no navigation to return to the W3C site, which may pose
usability issues. |
I believe that we chose not to use a custom search engine due to our privacy policy (sharing data with third parties). We have room for improvement regarding search results pages (including customization of the results
order). |
| Dummy links on expandable content |
Links are used to allow tab navigation. They are activated
through javascript, but if javascript is turned off they are confusing.
|
Done. |