unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 1/7] doc: design_www: more accessibility guidelines
Date: Fri,  4 Sep 2015 02:18:05 +0000	[thread overview]
Message-ID: <1441333091-32421-2-git-send-email-e@80x24.org> (raw)
In-Reply-To: <1441333091-32421-1-git-send-email-e@80x24.org>

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


  reply	other threads:[~2015-09-04  2:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04  2:18 [PATCH 0/7] new index and misc fixes Eric Wong
2015-09-04  2:18 ` Eric Wong [this message]
2015-09-04  2:18 ` [PATCH 2/7] index: use message threading if search is available Eric Wong
2015-09-04  2:18 ` [PATCH 3/7] consolidate thread sorting in view Eric Wong
2015-09-04  2:18 ` [PATCH 4/7] extmsg: close HTML tag in response Eric Wong
2015-09-04  2:18 ` [PATCH 5/7] view: avoid attempting to find "subject dummy" Eric Wong
2015-09-04  2:18 ` [PATCH 6/7] SearchMsg: avoid encoding Message-IDs Eric Wong
2015-09-04  2:37   ` Eric Wong
2015-09-04  2:18 ` [PATCH 7/7] view: do not generate anchors in thread views Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1441333091-32421-2-git-send-email-e@80x24.org \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).