1 |
Curtis Napier wrote: |
2 |
|
3 |
> Aarons design uses a smaller default font, that is not acceptable from |
4 |
> an accessibility POV. The main font is at 1em and all cursory fonts |
5 |
> multipliers of 1em. The main font will remain at 1em which is the |
6 |
> standard for the accessibility guidelines. If you don't like the |
7 |
> standard font size every single graphical browser offers a font zoom |
8 |
> capability, use it. |
9 |
|
10 |
I just asked we don't set the font size in px.. |
11 |
|
12 |
> |
13 |
> The site is not XHTML it is HTML-4.01 Transitional and it passes the |
14 |
> w3c validator. Manually overriding HTML-4.01 Transitional in the w3c |
15 |
> validator is not required and any errors that it reports if you do |
16 |
> this will not be addressed. If you can come up with a good technical |
17 |
> reason why doing this would benefit anyone I will address it. |
18 |
> |
19 |
> Navigation and useability studies are beyond my scope. These issues |
20 |
> should have been addressed a year ago. |
21 |
|
22 |
There always has to be a point in software were we lock on features.. |
23 |
Hopefully we look at this sometime in the future. It's my understanding |
24 |
that xhtml is a finer grained standard and will become more so in the |
25 |
future.. Allowing for a right once and preview the same across browsers |
26 |
approach.. Thus not having to "worry" so much if the site previews the |
27 |
same across any platform. It will save time for everyone later.. (only |
28 |
mentioning) |
29 |
|
30 |
> |
31 |
> The left hand navigation column is dead. No amount of beating this |
32 |
> dead horse will resurrect it. The jumppads will remain at the bottom |
33 |
> and appear on all non-documentation pages so that those links are |
34 |
> accessible as much as possible. |
35 |
|
36 |
I only recommended kicking a small portion of the bottom jump pads to |
37 |
the right side above the ads. Allowing for navigation bar and menu to |
38 |
be closer together.. (imho not important) |
39 |
|
40 |
> |
41 |
> The CSS is only 12k. Why would shaving 4k off of it to make it 8k make |
42 |
> a difference to anyone? |
43 |
|
44 |
Loads, parses and renders faster... After the need for editing is |
45 |
done.. I think simply removing white space might accomplish this.. |
46 |
|
47 |
> |
48 |
> The site is dynamically generated with XSL/XML all the pages end in |
49 |
> .xml. There are no plans to change it to .xhtml now or in the future. |
50 |
|
51 |
I have to look at this logically.. |
52 |
So we are intentionally rendering HTML 4? HTML docs being such usually |
53 |
end it .html file extension.. Unless there are some changes then should |
54 |
be just .html files.. OR update the code to be xhtml compliant and leave |
55 |
as .xml.. This doesn't really matter, but it's semantics.. |
56 |
|
57 |
It's like renaming a bzImage to Kernel.dll |
58 |
|
59 |
In the end.. Looks better and thanks for the great work |
60 |
|
61 |
Cheers, |
62 |
|
63 |
C. |
64 |
-- |
65 |
www-redesign@g.o mailing list |