I hate to say it, but I do not think there can be quote official unquote discussion until such time that the AG WG formally starts working on updating WCAG2ICT. Which is kind of the point of this issue, and hence the title and request for official discussion. The AG WG does not currently have written guidance on 1.4.10 should be applied to non-web software. I prefer 's note in his WCAG2ICT draft update: "It is likely that for software there will be more frequent cases where two-dimensional layout are required for usage or meaning."Įxamples of word wrap in native mobile apps: I agree it's somewhat more challenging compared with web, but the harder challenges come from app designs that didn't consider text enlargement, not from technical limitations of the platforms. Android and iOS do give developers robust tools for word wrap in native apps (links below). I would not categorically exempt mobile apps from reflow requirements. Without OS support for a reflow mechanism, an app-author would have to build different layouts manually, which goes beyond the intended scope of the reflow SC. Mechanisms for text enlargement include browser zoom, OS font size preferences (as correctly noted for mobile native apps), or user preferences within the web site or software product (example: Change font size in Mail on wrote: To make this statement more technology agnostic, we should instead say ".allow reflow when the user enlarges text". I agree with this statement when talking about desktop browsers, where browser zoom has become the best mechanism for resizing text without assistive technology. The spirit of 1.4.10 is that it allows reflow when the user zooms.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |