Expand/clarify understanding for 1.4.4 Resize Text, harmonise 1.4.8 Visual Presentation #2270
Conversation
Relates to #2169 and questions about whether a site that break using "text-only" resizing fails, even if zooming works
|
Rendered view via githack [Updated] |
There was a problem hiding this comment.
How about breaking the exception into its own sentence? For example:
The intent of this Success Criterion is to ensure that visually rendered text, including controls and labels using text, can scale larger so that they can be read more easily by people with milder visual impairments, without requiring the use of assistive technology (such as a screen magnifier). There is an exception for images of text and captioning, since those technologies might not provide for machine readable text. Users may benefit from scaling all content on the Web page, but text is most critical.
|
@bruce-usab i like your rewrite there. so is that exception there (about images of text and captions) what the cryptic "in data form such as ASCII" actually means to mere mortals? |
removes the inscrutable bit about "ASCII", and mentions the exception (which was otherwise missing from the understanding)
|
took @bruce-usab's suggestion (with a slight bit of language tweaking), which now nicely also mentions the exception (where previously the document is mostly silent about it, except for a bit about images of text). this also removes the cryptic mention of "text characters that are still in data form such as ASCII" which i still fail to understand. again, if anybody wiser than me has any idea what that meant, and why it was there/if it's essential to bring that back, happy to reinstate something, but it'll need a bit of clarification as well, as currently it seems to baffle people. |
|
@patrickhlauke maybe you also want to remove the ASCII part of 1.4.8? - it is the same there |
|
@JAWS-test good point, might as well |
patrickhlauke
changed the title
|
I do not know who wrote |
…hub.com/w3c/wcag into patrickhlauke-understanding-resize-text
|
Could we somehow form a community group that reviews and merges those changes largely independently from AG WG? It feels like AG WG has not enough time to prioritize this, and a dedicated group for these editorial changes would probably be more efficient, especially if the red tape is removed. |
|
I was under the impression there was already a sub-group (meeting on Fridays) of the AGWG supposed to look at clearing the backlog of some of the pre-2.2 related issues, but I think that's been going slowly as well. agree that for reasonably non-controversial additions/edits, it would be great to have a more nimble approach... |
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Co-authored-by: Alastair Campbell <[email protected]>
Relates to #2169 and questions about whether a site that break using "text-only" resizing fails, even if zooming works