Myndex
commented
1 year ago Thank you
Thank you @angyb for bringing this to my attention. We haven't gone through and aligned everything because this is in an area of currently active research relating to use cases. The specific intent or use case will also dictate the minimum size or thickness.
Still I agree that it can certainly cause confusion and should be fixed or clarified in the interim, adding to the list of things to do...
Some Discussion On Nontext
Semantic & differentiable non-text requires a similar contrast relative to spatial frequency as "other fluent text". However, the merely discernible non-text is more equivalent to sub-fluent text, and can work at a lower contrast level. Here are some broad categories:
Semantic Non Text
- Intrinsically semantic (icon or pictogram, land map)
This kind of non-text element has needs that are similar to that of fluent text, so this chart is probably the best fit:
But what about these categories?
- Contextually semantic (chart lines, pie chart pieces, demographics map, lat/long lines, legend codes)
- Meta semantic (focus or state, dynamic driving map, animatable potentially in combination with 1 & 2)
These may not necessarily need the same level of contrast as the semantic elements, and specific levels here are being studied.
On the other hand, this final category:
Non-Semantic
- Discernible non-semantic (border, abstract button shape, map outer edge or legend area, zoom-up enlargement areas)
Non-semantic elements that need to be seen, but don't specifically convey information, such as a border dividing two elements, or a disabled control, can use lower contrasts as shown on this chart and still be effective.
Summary
So again thank you for pointing out the discrepancy, and as you can see there's actually a little bit more to it in terms of specific levels readers relative to a particular use case.
Please let me know if you have any further questions!
Thank you for reading,
Andy
Please enter a descriptive title.
Does this relate to a web app or tool (i.e. you're an end user) OR is this about code or code integration (you're a developer).
Describe the bug
In this documentation https://github.com/Myndex/SAPC-APCA/blob/master/documentation/APCA_in_a_Nutshell.md#use-case-ranges it is states that: Lc30 should be “no less than 4px solid in its smallest dimension.” Lc15 “is no less than 6px (solid) in its smallest dimension”
This document as well says the same for Lc15 https://github.com/Myndex/SAPC-APCA/blob/master/documentation/WhyAPCA.md Lc15 “is no less than 6px in its smallest dimension”
Whereas on this page: https://www.myndex.com/APCA/, under APCA Guidelines: Bronze Level, it states: Lc30 should be “no less than 10px in its smallest dimension” Lc15 “is no less than 15px in its smallest dimention”
To Reproduce Steps so we can reproduce the behavior:
Expected behavior The same correct values on all pages.
Screenshots Add screenshots or code snippets to help explain your problem.
System or device information (please complete the following):
Additional context It would be helpful if minimum widths were listed for Lc45, 60, 75, and 90, as well. For example, which Lc should a 1px form field border be vs. a 2px border?