Research impact of techniques in the WCAG 1.4.4. Guideline for resizing text

[roslynwythe]

Dependency

• After Accessibility Audit #1347 is closed, review this issue to see if it needs rewriting or closing. See comments

Overview

Research the feasibility and impact of implementing alternative Accessibility techniques, so that Hack for LA's website can score the highest Accessibility rating possible, while still being easy to use for all visitors.

Details

Zoom functionality in modern browsers ensures that the WCAG 1.4.4 guideline on resizing text is satisfied, but there are alternative techniques for compliance that offer accessibility advantages. In this issue we will research the feasibility and impact of implementing alternative techniques described in the guideline, in particular: (1) providing accessibility controls on the page, and (2) Specifying relative font sizes and resizing text containers and layout regions to scale with text size

Action Items

• Research the impact of implementing:
  • G178: Providing controls on the Web page that allow users to incrementally change the size of all text on the page up to 200 percent
• Research the alternative of ensuring that text containers resize when the text resizes AND using measurements that are relative to other measurements in the content by using one or more of the following techniques:
  • C28: Specifying the size of text containers using em units
  • Techniques for relative measurements
    • C12: Using percent for font sizes
    • C13: Using named font sizes
    • C14: Using em units for font sizes
  • Techniques for text container resizing
    • SCR34: Calculating size and position in a way that scales with text size
    • G146: Using liquid layout
• Document findings in a Decision Record.

Resources/Instructions

• W3C Web Content Accessibility Guidelines (WCAG) 2.0
• Understanding Success Criteria 1.4.4: Resize Text
• Sufficient techniques for WCAG 1.4.4
• How to change text size in Google Chrome

Created by this issue

• DRAFT: Decision Record - Hack for LA Issue #4227

[github-actions]

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:
Complexity, Role, Feature

NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[ExperimentsInHonesty]

@roslynwythe what complexity is this?

[roslynwythe]

@ExperimentsInHonesty To determine the complexity, I would appreciate your input on the scope of this issue. Should this issue focus just on the evaluation of compliance or should it include analysis/decision re: alternative CSS approaches? And should we broaden the focus to include not just fixed font size but also other CSS issues that could impact text scaling, such as fixed width containers or the use of text within images?