Low Vision Accessibility Task Force Meeting Resolutions
Minutes | Topics | Resolutions
This page was last updated on 26 May 2025. For more recent meetings, see an alternative view of meeting minutes.
2022
-
3 March: Low Vision Accessibility Task Force Teleconference
- Do skeleton loaders fall under “inactive” exemption of 1.4.11 Non-Text Contrast? #2048 <https://github.com/w3c/wcag/issues/2048> - Task force agrees that some indication of page/content loading needs to have sufficient contrast but the skeleton itself does not need to
-
20 January: Low Vision Accessibility Task Force Teleconference
- Discussion related to Proximity User Needs (https://github.com/w3c/low-vision-a11y-tf/discussions/13 - Make this guidance about visual proximity - we may do audio one separate - we should make reference to audio.
- When do we introduce important terms? - For this one we will have a section for important terms like point of regard and leaving open if it needs anything else.
- Discussion related to Proximity What To D - Try having a section like a quick check section
- open issues - include images at the top that relate to and illustrate user needs.
2021
2019
-
25 July: Low Vision Accessibility Task Force Teleconference
- Do you agree with the change to the normative SC text? (yes/no) - leave current 1.4.12 SC test as "at least"
-
30 May: Low Vision Accessibility Task Force Teleconference
- Google research - non-text contrast - Use color wheels with black lines and not with white and black lines for reasons discussed.
-
7 February: Low Vision Accessibility Task Force Teleconference
- review new WG process https://www.w3.org/WAI/GL/wiki/WCAG_2.2_working_process - LVTF prioritizes focus and control affordance to be a critice SC
2017
-
27 July: Low Vision Accessibility Task Force Teleconference
- Popup Interference (MetaData on Hover) - Accept Popup Interference above
- Printing https://github.com/w3c/wcag21/issues/76 - send to AG: "essential information can be printed with no loss of content"
-
4 May: Low Vision Accessibility Task Force Teleconference
- Contrast Smith-Kettlewell - WE WILL UPDATE ISSUES 9 & 10 WITH TEXT ABOVE
- Contrast Smith-Kettlewell - WE WILL UPDATE USER NEEDS 2.4.3 WITH TEXT ABOVE
- 27 April: Low Vision Accessibility Task Force Teleconference
-
30 March: Low Vision Accessibility Task Force Teleconference
- Adapting Text...Add bullet to Adapting text to "increase spacing between columns" - Not have the extra bullet for extra spacing between columns.
- Adapting Text...Add bullet to Adapting text to "increase spacing between columns" - Not have the extra bullet for extra spacing between columns.
-
9 February: Low Vision Accessibility Task Force Teleconference
- enlargement without word wrapping is not accessibility support - Enlargement without word wrapping is not accessibility support.
- 2 February: Low Vision Accessibility Task Force Teleconference
2016
-
8 December: Low Vision Accessibility Task Force Teleconference
- Issues 8 and 80 - Move benefits from Issue 80 to Issue 77 and close Issue 80 - https://github.com/w3c/wcag21/issues/80
- graphics contrast - Defer any VR SC's to Silver group
-
1 December: Low Vision Accessibility Task Force Teleconference
- Text Colors - Text Colors https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Text_Colors ready for WCAG 2.1
- Metadata on Hover - Metadata on Hover is ready for WCAG.
- Printing Customized text - Printing Customized Text is ready for WCAG WG
- Size of all Content - Resize content https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Size_of_all_elements is ready to go to WCAG
- Font Family - Spacing https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Spacing is ready to go to WCAG
- Font Family - Font https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Font is ready for WCAG
- seeing all interface elements - Seeing all Interface elements https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Seeing_All_Interface_Element is ready for WCAG
-
17 November: Low Vision Accessibility Task Force Teleconference
- https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Contrast_(Minimum)
- Contrast: Informational Graphics - https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Informational_Graphic_Contrast_(Minimum) Ready for WCAG.
- Line Length - https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Line_Length Ready for WCAG.
- Reflow to Single Column - https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Reflow_to_Single_Column Ready for WCAG.
-
10 November: Low Vision Accessibility Task Force Teleconference
- Contrast: Interactive Elements - Working Group agrees that Contrast Minimum for Enabled Elements is ready to be sent to WCAG
- Contrast: Interactive Elements - Working Group agrees that Contrast Minimum for Interactive Elements is ready to be sent to WCAG - https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Contrast_(Minimum)
-
27 October: Low Vision Accessibility Task Force Teleconference
- https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Tracking_Success_Criteria_Progress - Need more information and examples on https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Metadata_On_Hover to hone the SC text.
- Interactive element contrast minimum - Glenda to integrate a few more comments, e.g. a requirement for an apparent border
-
18 August: Low Vision Accessibility Task Force Teleconference
- Resolution to Accept Icon font techniques - LVTF approves the 2 Icon Font Techniques
-
4 August: Low Vision Accessibility Task Force Teleconference
- Gap analysis updated - existing SCs http://w3c.github.io/low-vision-SC/GapAnalysis-SC.html - Text Colors: A mechanism is available for users to select foreground and background colors of text from the full range of colors available on the operating system.
-
7 July: Low Vision Accessibility Task Force Teleconference
- Hyphenation https://github.com/w3c/low-vision-SC/issues/8 - Accept the wording for hyphenation.
-
23 June: Low Vision Accessibility Task Force Teleconference
- Modify SC WCAG 1.4.8 item 2 (80 characters) https://github.com/w3c/low-vision-SC/issues/6 - 1.4.8.2 width is user adjustable @@do we need a lower bound
- Modify SC WCAG 1.4.8 item 2 (80 characters) https://github.com/w3c/low-vision-SC/issues/6 - 1.4.8.2 width is user adjustable @@do we need a lower bound
-
9 June: Low Vision Accessibility Task Force Teleconference
- Section 2.5: Functional Vision https://github.com/w3c/low-vision-a11y-tf/issues/73 - Accept point 1a
- Section 2.5: Functional Vision https://github.com/w3c/low-vision-a11y-tf/issues/73 - Accept point 1b
- Section 2.5: Functional Vision https://github.com/w3c/low-vision-a11y-tf/issues/73 - We will create or extend a user need regarding clutter.
- Disclaimer draft (action-58) https://github.com/w3c/low-vision-a11y-tf/issues/67 - Adopt disclaimer language above.
-
2 June: Low Vision Accessibility Task Force Teleconference
- Password fields - Shawn to write password visibility addition to 3.7.1
- italics, bold, underline #50 - reword 3.3.3 and change intro for 3.5.1 per issue discussion
- Editorial: Electronic vs Digital content #66 https://github.com/w3c/low-vision-a11y-tf/issues/66 - current wording is fine, not changing
- Editorial: Language, Jargon #60 https://github.com/w3c/low-vision-a11y-tf/issues/60 - use shawn's comment
- visual clutter - change wording for intro in section 2.4
- Section 2.4.1 https://github.com/w3c/low-vision-a11y-tf/issues/69 - update document to reflect shawn's wording in the issue
- Section 2.4.3 https://github.com/w3c/low-vision-a11y-tf/issues/71 - change to "Contrast sensitivity is the ability to detect differences in brightness between objects and their backgrounds, for example, to discern text from its background.
- Section 2.4.4 https://github.com/w3c/low-vision-a11y-tf/issues/72 - 2.4.3 change wording "Contrast sensitivity is the ability to detect differences in brightness, for example, to discern text from its background."
-
26 May: Low Vision Accessibility Task Force Teleconference
- Photos Issue-63 - User need: users can get information from images, including photos
- Photos Issue-63 - : User need: users can get information from images, including photos
-
19 May: Low Vision Accessibility Task Force Teleconference
- 3.3.1 Text Size - GAP WCAG - 1.4.4 & 1.4.8 limits size to 200%, NOGAP UAAG met by 1.4.1 & 1.4.2
- 3.3.2 Font - GAP WCAG no SC, NOGAP UAAG met by 1.4.1 & 1.4.2
- 3.3.3 Style - GAP WCAG no SC, NOGAP UAAG met by 1.4.1 & 1.4.2
- 3.3.4 Capitalization - GAP WCAG no SC, NOGAP UAAG met by 1.4.6
- 3.4.6 spacing between elements - 3.4.6 Spacing - GAP WCAG 1.4.8 only covers <p>, NOGAP UAAG met by 1.4.2 and 1.4.3
- 3.4.6 spacing between elements - 3.4.6 Spacing - GAP WCAG 1.4.8 only covers <p>, NOGAP UAAG met by 1.4.2 and 1.4.3
- 3.5.1 element customization - No SC in WCAG, UAAG covers in 14.2 and 1.4.6
- 3.6.1 Maintain Point of Regard - GAP in WCAG, Covered in 1.8.6 and 1.8.9
- 3.6.2 proximity of related information - GAP in WCAG, UAAG GAP with partial 1.10.1
- 3.7.1 seeing all interface elements - GAP in WCAG, UAAG 2.71 covers UA items only, not content elements
- 3.7.1 seeing all interface elements - WCAG partial 1.44 and 1.48, UAAG 2.71 covers UA items only, not content elements
- 3.7.2 Printing Customized text - GAP in WCAG, Covered in UAAG 1.4.4
- 3.7.3 Using User Setting - 3.7.3 user agents uses OS settings; content uses UA and OS settings
- 3.7.3 Using User Setting - Absent in WCAG; NOGAP UAAG GL 2.6 and 5.1.3
-
12 May: Low Vision Accessibility Task Force Teleconference
- 3.3.5 Size of all elements - Gap in LVTF 3.3.5 - UAAG and WCAG only cover text
- 3.4.1 Leading - change 3.4.1 change leading to be "line spacing (leading)" eliminate line height
- 3.4.1 Leading - GAP - WCAG - partial, no adjusting, only minimum), UAAG (adjustable - only to 2x, with 3 levels). Note: users may want less than minimuim
- 3.4.2 Letter Spacing - GAP not covered by WCAG or UAAG
- 3.4.4 justification - GAP - WCAG 1.4.8 partial - no full justifiaction, NO GAP UAAG 1.4.3 blocks of text
- 2.4.5 Margins and borders - GAP not covered by WCAG, no gap in UAAG (though border settings not fully expanded)
-
4 May: Low Vision Accessibility Task Force Teleconference
- Meeting time and dates - New meeting time is Thursdays at 8:00-9:30PT/10:00-11:30CT/11:00-12:30ET
-
20 April: Low Vision Accessibility Task Force Teleconference
- Issue 49 2.1 Scope - Add clause specifiying dyslexia and learning difficulties and link to the definition in Coga Gap Analysis.
- Issue 50 Italics, bold, underline - Accept the wording above for 3.5.1.
- 3.3.3 Explanatory text - Reword explanatory text for 3.3.3 to add: For some people, it is difficult to read blocks of text [link to def] that is all italicized or underlined. For some people, substituting bold text or a different font for italics is easier to read. This applies to blocks of text, not individual words or phrases.
-
13 April: Low Vision Accessibility Task Force Teleconference
- Issue 35 Update information on acuity - Change intro to: Some low visual acuity can be corrected with glasses, contact lenses, or surgery – and some cannot. Therefore, some people will not see small text or fine details at all.
- Issue 42 3.5.1 - poor example illustration - Will preface with something to the affect that “This a real style sheet used by a person with low vision.”
- Issue 43 figure descriptions - Will update table, alts and images descriptions - and add appendix with detailed image descriptions.
- Issue 45 Note to tool developers not a user need - delete or edit? - Will make the editorial change on issue 45 per minutes.
-
6 April: Low Vision Accessibility Task Force Teleconference
- Legibility - Note and para. after covering legibility approved https://rawgit.com/w3c/low-vision-a11y-tf/user_need-legibility/requirements.html#h-note1
- Scope Issue 34 - The group deciided not to define electronic content.
- Issue 38 re-word 3.1.1 brightness vs. contrast - Edit 3.1.1 to include brightness.
- Issue 39: color wheel images - Leave the color whels images as is.
- Issue 39: color wheel images - Leave section 3.3.2 as it and cover specific fonts in best practice.
- 3.3.3 Avoid italics Issue 41 - Leave 3.3.3. Cover italics in best practices.
-
30 March: Low Vision Accessibility Task Force Teleconference
- LVTF position on contrast requirements for interactive control states - AWK to modify text of TF recommendation on focus and hover state contrast and send to TF mailing list, to be then forwarded to WCAG
-
9 March: Low Vision Accessibility Task Force Teleconference
- lvtf-ACTION-39: Craft user need on obscured perception and operability - add User Need: Users can see and operate all interface elements that are intended for users to see and operate. This includes when users have changed display settings such as text size, magnification, and cursor.
- lvtf-ACTION-39: Craft user need on obscured perception and operability - update previous resolution to: Users can see and interact with all content and user interface controls presented visually, including when users have changed display settings such as text size, magnification, and cursor appearance.
-
17 February: Low Vision Accessibility Task Force Teleconference
- We will deal with placement of tracking oafter FP'WD justification issue
- References - Collecting references in seperate page for now and adding them to the main document later
- Legibility, Readability, etc - add a note, in FPWD add a draft note that we will add a glossary def for this and leave the wikipedia link for now
-
10 February: Low Vision Accessibility Task Force Teleconference
- Color blindness - not include stats? #20 https://github.com/w3c/low-vision-a11y-tf/issues/20 - No objections to including the stats
- Change to focus on ICT more broadly #9 https://github.com/w3c/low-vision-a11y-tf/pull/9 - No objections to Shawn’s wording
- Address JB's comment on international perspective #8 https://github.com/w3c/low-vision-a11y-tf/pull/8 - No objections to Shawn’s wording.
- User Needs - specific settings #21 https://github.com/w3c/low-vision-a11y-tf/pull/21 - No objections to Shawn’s wording.
- Scope and specificity #16 https://github.com/w3c/low-vision-a11y-tf/pull/16 - No objections to Shawn’s wording.
- Change to scope and definition #10 https://github.com/w3c/low-vision-a11y-tf/pull/10 - No objections to Shawn’s wording.
- Separate color from contrast #15 https://github.com/w3c/low-vision-a11y-tf/pull/15 - No objections to Shawn’s wording.
- Brightness #22 https://github.com/w3c/low-vision-a11y-tf/pull/22 (changed from https://github.com/w3c/low-vision-a11y-tf/pull/18) - No objections to Shawn’s wording.
- Factual Correction #17 https://github.com/w3c/low-vision-a11y-tf/pull/17 - No objections to making an explicit note that we are working on this visibility section.
- Sending to WCAG WG & EOWG for approval to publish - Accept sending to WCAG WG & EOWG for approval to publish with understanding completion of minor “to dos” and notification.
-
3 February: Low Vision Accessibility Task Force Teleconference
- 7. Terminology: color vision deficiencies - Follow Jim and Shawn's suggestion in the survey
-
27 January: Low Vision Accessibility Task Force Teleconference
- User needs vs user requirements <https://www.w3.org/2002/09/wbs/81151/UserNeeds-Jan-27/results#xq2> - Keep requirements in title and keep user needs in interior sections
- Note title <https://www.w3.org/2002/09/wbs/81151/UserNeeds-Jan-27/results#xq3> - title Accessibility Requirements for People with Low Vision
- Do not include additional stats? <https://www.w3.org/2002/09/wbs/81151/LVTF18Jan2016/results#xq2> - stick with what we have for low vision incidence - stick with stats we have
- Leave movement? <https://www.w3.org/2002/09/wbs/81151/LVTF18Jan2016/results#xq3> - Leave movement bullet as is
- Leave hyphenation in tracking? <https://www.w3.org/2002/09/wbs/81151/LVTF18Jan2016/results#xq5> - leave hyphenation in Tracking
- Field of Vision section heading <https://www.w3.org/2002/09/wbs/81151/UserNeeds-Jan-27/results#xq7> - Add in clarity in parenthesis in section on Visual Acuity with editorial permission
- Field of Vision section heading <https://www.w3.org/2002/09/wbs/81151/UserNeeds-Jan-27/results#xq7> - remove perceptual area parenthetical text when talking about field of vision
- corrected terminology <https://www.w3.org/2002/09/wbs/81151/UserNeeds-Jan-27/results#xq5> - Go with "corrected" terminology
-
20 January: Low Vision Accessibility Task Force Teleconference
- 2. Seeing All Interface Elements - Size of All Elements Keep Together
- 3. Proportional text increase - 352 is adequately covered. Don’t need separate point.
-
13 January: SV_MEETING_TITLE
- survey - Level of Detail - All ancillary documents supporting the main document will be in separate documents and not in TR space.