From b2f7190333777d5ae0845ed0e7d9d9b055597208 Mon Sep 17 00:00:00 2001 From: Jiminy Panoz Date: Sun, 20 Mar 2016 16:52:27 +0100 Subject: [PATCH] =?UTF-8?q?RGAA=20(french)=20=E2=86=92=20WCAG?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ReadingSystems/Kindle/KDF-KFX/KindlePreviewer3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ReadingSystems/Kindle/KDF-KFX/KindlePreviewer3.md b/ReadingSystems/Kindle/KDF-KFX/KindlePreviewer3.md index 8e18fe2..99705da 100644 --- a/ReadingSystems/Kindle/KDF-KFX/KindlePreviewer3.md +++ b/ReadingSystems/Kindle/KDF-KFX/KindlePreviewer3.md @@ -49,7 +49,7 @@ What they don’t advertise though, are clever features that will enhance the us - the renderer takes user settings into account and will adapt drop caps, H&J and `float` images dynamically once a critical font size is reached; - the renderer supports gaiji images (`inline` images); -- the renderer computes an RGAA2-compliant contrast ratio: `color` for text on background. +- the renderer computes an WCAG2-compliant contrast ratio: `color` for text on background. As the previous renderer (for KF8) [performed very poorly with kerning and ligatures](http://www.mobileread.com/forums/showpost.php?p=3172282&postcount=420), it could explain why they decided to build a new one and manage a lot of stuff when processing files so that the new renderer doesn’t have to.