Despite best intentions, things like strike-throughs and italics won't render well and will harm accessibility. --- Documentation/design_www.txt | 10 ++++++++++ 1 file changed, 10 insertions(+)
diff --git a/Documentation/design_www.txt b/Documentation/design_www.txt index b73a798..8763184 100644 --- a/Documentation/design_www.txt +++ b/Documentation/design_www.txt @@ -59,6 +59,16 @@ variable-width fonts. * No setting colors or font sizes, power to users to decide those. +* Only one font type (fixed or variable) per page. This is for + accessibility, we must not blow certain elements out-of-proportion + when a reader increases font size. + +* Bold and underline elements are OK since they should render fine + regardless of chosen font and gracefully degrade if a display does + not support them. Italics and strike-through elements must be + avoided as they do not render well with some displays or user-chosen + fonts. + * No JavaScript. JS is historically too buggy and insecure, and we will never expect our readers to do either of the following: a) read and audit all our code for on every single page load -- EW -- unsubscribe: meta+unsubscr...@public-inbox.org archive: http://public-inbox.org/meta/
