Replies: 3 comments
-
Hi @angyb The lookup table was an initial experiment, and the "add Lc15" was an attempt to simplify. We are making some changes—among other things, the strict adherence to certain table metrics is for the Silver and Gold levels, not the Bronze level. The current public draft guideline is https://readtech.org/ARC/ and in particular, see the "Bronze Simple Mode". Body text has a higher |
Beta Was this translation helpful? Give feedback.
-
@Myndex We're doing a major redesign, and I hope to make our work as future-proof as possible (given that APCA-RC is still in draft). We make an educational product used in public schools and must meet WCAG 2.x AA minimums before a school/district/state will consider purchasing our product. I thought using the Silver lookup table would ensure we are also compliant in the future WCAG 3.x. If I use the Bronze level guidelines, will I likely (hopefully?) be compliant with WCAG 3 minimums? Or should I be looking at the Silver LUT, since we need to meet WCAG 2.x AA minimums? I realize you can't see the future. Your best guess will do. The Bronze guidelines also say: "Lc 30 - The absolute minimum for any text not listed above. This includes placeholder text and disabled element text." This is confusing to me because it also recommends a font size of 36px for non-body text at Lc45. In which case, how big must placeholder text be if it's Lc30? And what about 12px hint text that appears below a field input? Must it be Lc90? That seems excessive for supplementary text. I made this table for myself to better visualize the Bronze level guidance. This seems to suggest that no body text should ever use any contrast lighter that Lc75. Am I interpreting this correctly? (b=body text, nb=non-body text) ![]() |
Beta Was this translation helpful? Give feedback.
-
ComparedWCAG 2 A level does nearly nothing at all for visual contrast or visual accessibility. APC-RC Bronze is "equivalent but better then" WCAG 2's 1.4.3 and 1.4.11 (AA) APC-RC Silver is better than WCAG 2's AAA APC-RC Gold is intended as a best-in-class complete system, though the deeper we research, the more complex it becomes, and is currently exceeding available technology (requires polyfills). WCAG 3, at present, has no actionable guidelines as they relate to visual contrast. Nuances of APC-RCWCAG 2 has no guideline for disabled text. APC-RC does, but not in the lookup tables. The draft discusses this more, for instance regarding text use cases: https://readtech.org/ARC/tests/visual-readability-contrast/?tn=conform This is draft, your thoughts and comments are very welcome. Keep in mind that visual hierarchy is also an important accessibility issue: not everything should be at high contrast. A good visual hierarchy guides the reader through the most important context, and ancillary, secondary, and non-content can and should be at much lower contrasts for this reason. Generally, disabled controls should be about Lc30 less than the non-disabled control, to clearly show the change of focus, for instance. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
@Myndex
The “+15” for body text for certain font sizes in the lookup table doesn’t make sense to me. If I want to use an 18px font (Helvetica) for body text, I need an Lc of 75 (equivalent to WCAG’s 4.5:1). If, instead, I want to use a larger font, say 24px, I still have to use Lc 75 (rather than Lc60 which is equivalent to WCAG 3:1 for a font this size). 24px is 33% larger than 18px, why do I need to use the same Lc75?
Couldn’t we have a table with more discreet Lc for body text instead of a blanket “add 15”? In my example, 24px at Lc60 appears to be nearly the same luminance as 18px at Lc75 and is equally readable (in my possibly flawed opinion). While 24px at Lc75 appears significantly darker.
Couldn't we have a LUT for body text and another for sub-fluent non-body text? It would add so much clarity to be able to look these up independently based on how they're being used.
Thank you kindly.
Beta Was this translation helpful? Give feedback.
All reactions