- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Thu, 16 Aug 2018 16:46:17 -0500
- To: Jared Smith <jared@webaim.org>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
- Message-ID: <CA+=z1Wn9-78A9feB3G_hdD0jZ0+d9bt-oPS0BzjcAE3jiFtfXQ@mail.gmail.com>
Thank-you for the opportunity to provide input to the survey. Below is a summary of items the group thought should be amended, changed, reformatted, or added -- at your discretion. Also attached as a word document Low Vision survey Format thoughts · text size of dropdown boxes is smaller than other text in questions · dropdowns have a higher cognitive load to read and operated, why not radio buttons. · no real differentiation between questions. perhaps add numbers or headings or more space · on questions with Other, provide a blank to collect more info. · Put related questions next to each other. (e.g. keyboard and heading nav questions) Visual Impairment question · change Contrast/light Sensitivity to Contrast sensitivity (difficulty seeing low contrast) · perhaps add Field of vision limitations (peripheral field loss, central field loss, or other) Primary device · mobile and tablet should be separate items · had a discussion about changing question to be about monitor size What is your preferred monitor size? – desktop monitor, laptop, tablet, phone. AT used · remove “software” from screen magnifier · some in the group thought the public might confuse screen magnifier with browser zoom · really wanted a granular question on custom styles. See below primary screen reader · include Fusion? Or is it too new. · Why no Talkback? · Perhaps a list “check all that apply” people may use different ones at different times. Mobile platform · Perhaps add Jitterbug for age related vision phone A11y settings · Perhaps add (including large text) in the question because many people don't consider large text an accessibility setting Magnification level · No response and I don’t know should be separate answers. Nav by Heading · Add I didn’t know they existed (might be appropriate for other questions also) Custom Styles – change wording and add questions. Change the order to put AT question and Custom styles in sequential order Which of the following do you frequently use? (Select all that apply) Screen reader Screen magnifier software Browser page zoom (zooms all page content) Browser text size settings High contrast mode or settings Browser settings to change colors Custom styles (for example with Stylish, Stylus, and user style sheets) Other: ______ New question If you use custom styles (for example with Stylish, Stylus, and user style sheets), what do you change: I don't know how to use custom styles I know how to use custom styles, but don't use them Font size Font family Font weight Background and/or text color Line height Letter or word spacing Spacing around paragraphs, headings, etc. Element-level customization (for example, different styles for different heading levels) Other: [______________________________] New Question What type of font do you prefer for paragraphs (or large blocks of text).? Serif (e.g., Times New Roman, Georgia, Bookman) Sans-serif (e.g., Arial, Helvetica, Verdana, Tahoma) New Question Do you quit reading information from the computer (such as an article on the web or instructions in PDF) and not finish it, just because the text is too hard to read comfortably? Never, Rarely - a few times a year, Occasionally - a few times a month, Sometimes - a few times a week, Often every day New question Which high contrast mode do you use? -I don’t use a high contrast mode -A dark contrast theme -A low contrast theme -Other (please describe) On Thu, Aug 16, 2018 at 12:39 PM Jared Smith <jared@webaim.org> wrote: > Thanks Jim. Could you maybe provide a cliff-notes version of the actual > recommendations? It's really hard to parse the notes (especially with so > many sentence fragments and missing punctuation/capitalization) to know > what was a discussion item/idea vs. a recommendation. > > Thanks, > > Jared > > > On Thu, Aug 16, 2018 at 11:32 AM, Jim Allan <jimallan@tsbvi.edu> wrote: > >> https://www.w3.org/2018/08/16-lvtf-minutes.html >> >> Low Vision Accessibility Task Force Teleconference16 Aug 2018Attendees >> PresentJim, Laura, Shawn, SteveRepsher, jon_avila, wayneDRegretsChairJim >> Scribejim >> Contents >> >> - Topics <https://www.w3.org/2018/08/16-lvtf-minutes.html#agenda> >> 1. WebAIM Low Vision Survey #2 Draft Review >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#item01> >> 2. primary device >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#item02> >> 3. AT that is used >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#item03> >> 4. primary screen reader >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#item04> >> 5. keyboard >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#item05> >> 6. mobile platform >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#item06> >> 7. Accessibility settings >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#item07> >> 8. voice assistant >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#item08> >> 9. magnification level >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#item09> >> 10. custom styles >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#item10> >> 11. nav by headings >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#item11> >> 12. accessibility feelings >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#item12> >> 13. social media >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#item13> >> 14. custom styles >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#item14> >> - Summary of Action Items >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#ActionSummary> >> - Summary of Resolutions >> <https://www.w3.org/2018/08/16-lvtf-minutes.html#ResolutionSummary> >> >> ------------------------------ >> >> <jon_avila> A link I found that says "expand your window to view this >> experience" >> https://www.cnn.com/ampstories/entertainment/the-aretha-franklin-you-probably-didnt-know >> >> <shawn> [ reviewing https://webaim.org/projects/lowvisionsurvey/survey2... >> font size in drop-downs ... ] >> >> <shawn> https://webaim.org/projects/lowvisionsurvey/survey2 >> >> zakim: open item 1 >> WebAIM Low Vision Survey #2 Draft Review >> >> <scribe> scribe: jim >> >> WebAim looking for input, hope to launch at end of august >> >> jon: likes questions on font size, heading, and keyboard >> ... would like more questions >> >> wd: enlargement - with or without word wrapping >> >> * text size of dropdown boxex is smaller than other text >> >> <shawn> slh: font size in fields smaller >> >> * questions seem to run together. no real differentiation between >> questions. perhaps add numbers or headings >> >> <shawn> * minor - more space between questions (esp before "Which of the >> following types of visual impairment do you have?") >> >> <shawn> * "Contrast/light sensitivity" -> >> >> <shawn> * "Contrast/light sensitivity" -> "Contrast sensitivity" >> >> <shawn> ... maybe add "(difficulty reading low contrast)" >> >> * question 5 Contrast/light sensitivity - change to "Contrast sensitivity >> (difficulty seeing low contrast)" >> >> * q5 other should have blank for other input >> >> * appreciate short survey. wonder about removing some quesitons - e.g >> internet proficiency. >> >> wd: correlate custom style sheet question with internet proficiency. >> >> <steverep> Can someone paste a link to this survey? >> >> laura: why have age? is it important? >> >> https://webaim.org/projects/lowvisionsurvey/survey2 >> >> laura: what are they going to do with the information on age? >> >> wd: seen breakdown on age related vision from 50 to 90%% >> >> jon: may correlate age with other questions. >> ... thought you had to be over 18 to take survey >> primary device >> >> jon: TV >> >> <steverep> Shouldn't "internet" be "world wide web" ;) >> >> * mobile and tablet should be separate >> >> discussion of laptop with external monitor, keyboard, mouse, etc. would >> answer desktop. >> >> <shawn> Shawn: Technically use laptop, but use external keyboard, >> external monitor, etc. >> >> jon: external large monitor connected to laptop. >> >> <shawn> ... but what's important for this survey? size of screen? >> >> * perhaps question should be preferred or common monitor size >> >> <shawn> a = desktop monitor, laptop, tablet, phone >> >> do people know what size monitor they use >> >> what size to you use to navigate the web. - laptop size screen or desktop >> size screen >> AT that is used >> >> * custom style - should have a seperate item for text spacing. although >> that question is asked later. >> >> slh: separate question on custom styles = how granular to get answers >> >> <laura> Custom styles to change spacing, font face/type face, color, or >> elements >> >> <shawn> SLH: want separate item for custom style. do we care about what >> they change with the styles? (Would be nice, but maybe or maybe not worth >> it :-) >> >> <shawn> SLH: Why have "Do you use custom styles or settings to change >> the default text spacing, such as letter/word spacing, line height, or >> paragraph spacing?" as a separate question further down? Probably better >> with the "Which of the following do you frequently use?" question >> >> sr: remove software from screen magnifier >> >> <steverep> Use "Screen magnifier (excluding browser zoom)" >> >> jon: could be hand held, or OS magnifier, >> >> sr: separate screen magnifier (not browser zoom) from browser zoom >> >> wd: always surprise at level of knowledge or lack of knowledge of >> browsers and modifications to behavior >> >> sr: magnifying glass vs software >> primary screen reader >> >> jim: should they include Fusion, Talkback - too many android screen >> readers >> >> jon: other needs a blank for more info >> ... have different screen readers for different platforms. Perhaps a list >> = check all that apply >> keyboard >> >> <shawn> consider putting next to each other "How often do you use the >> keyboard for web page navigation?" and "Do you use software or browser >> extensions that allow navigation by headings?" as they are related >> >> jim: dropdowns hard cognitively >> mobile platform >> >> jim: Nokia?? are they still out there >> >> wd: jitterbug >> ... for age related >> Accessibility settings >> >> jim: good question >> >> jon: is large text an accessibility setting. >> ... accessibility settings - (including large text) many people don't >> consider large text an accessibility setting >> voice assistant >> >> jon: not accessibility setting - adjust contrast - lower or increase >> brightness. >> >> wd: changing brightness by time of day >> >> jon: lots of disabled folk use these. >> >> slh: why asking this quesiton? >> >> jon: think its a useful question >> >> sr: wonder if getting at general use or as a replacement for typing or >> app usage. Functional use vs playing music >> magnification level >> >> wd: important to ask correctly. >> >> jon: depends on device. each platform are different, change resolution >> (800x600), change font size, etc. >> ... would answer 200% >> >> slh: have system settings (resolution, dpi, etc) then browser zoom, >> combination is larger that just browser zoom >> >> <shawn> slh: also have system settings *and* browser magnification -- >> but less than 200%. seems you have to ask about system settings first >> >> laura: may make the question too complicated. most don't know this stuff >> >> <shawn> SLH: realize mostpeople won't know. However, if just ask browser >> zoom, then you're not getting accurate data >> >> question: do you adjust system settings to meet your needs... yes/no/i >> don't know >> >> <shawn> SLH: "I don't know" is good info to know! >> >> <shawn> SLH: answers: 1. I don't know, 2. I don't change any settings, >> 3... >> >> laura - no response and I don't know are different things... should be >> separate. >> custom stylesnav by headings >> >> wd: interesting question. I turn on silent screen reader >> ... add "I didn't know they existed" >> >> <jon_avila> Thanks all. I have to drop off. >> >> wd: dealing with people who don't know you can do so many things. >> accessibility feelings >> >> wd: responsive design is making things look better >> >> laura: reorder questions. put most important ones first. >> >> wd: people used to demographics first. use headings to separate info. >> social media >> >> slh: why? >> >> wayne: its a pain. avoid it, too hard to use with low vision. too many >> columns, can't enlarge >> ... not sure if its accessibility or I avoid reading >> custom styles >> >> <shawn> Which of the following do you frequently use? (Select all that >> apply) >> >> <shawn> [_] Screen reader >> >> <shawn> [_] Screen magnifier software >> >> <shawn> [_] Browser page zoom (zooms all page content) >> >> <shawn> [_] Browser text size settings >> >> <shawn> [_] High contrast mode or settings >> >> <shawn> [_] Browser settings to change colors >> >> <shawn> [_] Custom styles (for example with Stylish, Stylus, and user >> style sheets) >> >> <shawn> [_] Other: ______ >> >> <shawn> If you use custom styles (for example with Stylish, Stylus, and >> user style sheets), what do you change: >> >> <shawn> [_] Font size >> >> <shawn> [_] Font family >> >> <shawn> [_] Font weight >> >> <shawn> [_] Background and/or text color >> >> <shawn> [_] Line height >> >> <shawn> [_] Letter or word spacing >> >> <shawn> [_] Spacing around paragraphs, headings, etc. >> >> <shawn> [_] Element-level customization (for example, different styles >> for different heading levels) [_] Other: [______________________________] >> >> <shawn> What type of font do you usually use for paragraphs (or large >> blocks of text).? >> >> <shawn> [_] Serif (e.g., Times New Roman, Georgia, Bookman) >> >> <shawn> [_] Sans-serif (e.g., Arial, Helvetica, Verdana, Tahoma) >> >> <shawn> [ fyi, background for this question: >> https://www.w3.org/WAI/RD/2012/text-customization/r14] >> >> wayne: separate question do you know about custom styles >> >> Thank You JARED!! and webAIM!!! >> >> <shawn> before "[_] Font size" *maybe* put "[_] I don't know how to use >> custom stlyes" and possibly "[_] I know how to use custom stlyes, but don't >> use them" >> >> <shawn> [ Shawn would welcome the opportunity to review revised draft ] >> >> <shawn> [ Shawn will check back through LVTF User Needs and TAdER survey >> to see if other suggestions ] >> >> wd: there is a sweet spot between font size, family, letter spacing, >> word spacing. try to stay within 1.2 times font size >> ... find the balance. the paramaters interact, >> >> <shawn> Under "Which of the following types of visual impairment do you >> have?" Do you want to add "Field of vision limitations (peripheral field >> loss, central field loss, or other)"? It is one of the categories that we >> describe in https://www.w3.org/TR/low-vision-needs/#visfie -- however >> maybe less relevant for this survey? >> >> <shawn> Undr "Which of the following do you frequently use?" Do you want >> to add "[_] Screen brightness - lower" and "[_] Screen brightness - >> higher". It's one of the user needs in >> https://www.w3.org/TR/low-vision-needs/#brightness-overall -- however, >> maybe less relevant for this survey? >> >> <shawn> [ Shawn will start e-mail thread about printing to be archived >> here >> https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2018Aug/thread.html >> ] >> >> <shawn> fyi, here are the things I asked in my survey a while ago: >> http://tader.info/survey1304.html >> >> <shawn> One of the questions that I found useful for helping show web >> designers and developers the importance of text customization is: >> >> <shawn> " >> >> <shawn> Question: Do you quit reading information from the computer >> (such as an article on the web or instructions in PDF) and not finish it, >> just because the text is too hard to read comfortably? >> >> <shawn> Answer choices: >> >> <shawn> Half of the respondents got: Never, Rarely - a few times a year, >> Occasionally - a few times a month, Sometimes - a few times a week, Often >> every day >> >> <shawn> Half of the respondents got: Often every day, Sometimes - a few >> times a week, Occasionally - a few times a month, Rarely - a few times a >> year, Never >> >> <shawn> " >> >> <shawn> Not sure if this type of question would fit in this survey. If >> so, I think the data would be very helpful. >> Summary of Action ItemsSummary of Resolutions[End of minutes] >> >> -- >> Jim Allan, Accessibility Coordinator >> Texas School for the Blind and Visually Impaired >> 1100 W. 45th St., Austin, Texas 78756 >> <https://maps.google.com/?q=1100+W.+45th+St.,+Austin,+Texas+78756&entry=gmail&source=g> >> voice 512.206.9315 fax: 512.206.9452 http://www.tsbvi.edu/ >> "We shape our tools and thereafter our tools shape us." McLuhan, 1964 >> > > -- Jim Allan, Accessibility Coordinator Texas School for the Blind and Visually Impaired 1100 W. 45th St., Austin, Texas 78756 voice 512.206.9315 fax: 512.206.9452 http://www.tsbvi.edu/ "We shape our tools and thereafter our tools shape us." McLuhan, 1964
Attachments
- application/vnd.openxmlformats-officedocument.wordprocessingml.document attachment: Low_Vision_survey_response.docx
Received on Thursday, 16 August 2018 21:47:01 UTC