From 2ceeed427e8780af9125330fc4f743c6a0dbee4b Mon Sep 17 00:00:00 2001 From: Rohan Kumar Date: Tue, 7 Jun 2022 23:38:44 -0700 Subject: [PATCH] New note: resize and reflow --- content/notes/resize-and-reflow.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 content/notes/resize-and-reflow.md diff --git a/content/notes/resize-and-reflow.md b/content/notes/resize-and-reflow.md new file mode 100644 index 0000000..628a1f6 --- /dev/null +++ b/content/notes/resize-and-reflow.md @@ -0,0 +1,15 @@ +--- +title: "Resize and reflow" +date: 2022-06-07T23:38:39-07:00 +replyURI: "https://yatil.net/blog/resize-text-reflow" +replyTitle: "WCAG SC 1.4.4 Resize Text & 1.4.10 Reflow" +replyType: "BlogPosting" +replyAuthor: "Eric Eggert" +replyAuthorURI: "https://yatil.net" +--- + +This is a good article on the difference between SC 1.4.4 and 1.4.10. However, I don't think these criteria go far enough: + +Even narrower viewports exist. KaiOS devices tend to have 240 px viewports; smartwatches tend to have half the width of a phone while emulating a phone width (Apple Watches can be instructed not to do this with a proprietary `meta` tag). Of course, making sites watch-compatible is a stretch, but support for feature phones running KaiOS should be reasonable. I wrote about this more in [Best practices for inclusive textual websites](https://seirdy.one/posts/2020/11/23/website-best-practices/). + +Another thing worth remembering is that users can change default fonts or override sire-set fonts. Don't just test with default default fonts; test with something wider. These criteria should specify some font metrics or (royalty free) representative wide fonts to use for testing.