- From: Wayne Dick <wayneedick@gmail.com>
- Date: Sat, 28 Jul 2018 08:40:44 -0700
- To: Jeanne Spellman <jspellman@paciellogroup.com>
- Cc: Jim Allan <jimallan@tsbvi.edu>, Jonathan Avila <jon.avila@levelaccess.com>, Laura Carlson <laura.lee.carlson@gmail.com>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
- Message-ID: <CAJeQ8SAOKEgK-weRb6GVq+xkrW1tg=yk_FJXzcA=+LmOua4gSg@mail.gmail.com>
I would like to suggest another name: *Role Level Personalization*. Most HTML elements have defined roles. So, ARIA role really is a generalization of generalization of element. Both role and element are language defined and can be detected programmatically. I also think personalization is the word because we are talking about making the page fit the person. Best, Wayne On Thu, Jul 26, 2018 at 3:16 PM Jeanne Spellman <jspellman@paciellogroup.com> wrote: > Please keep in mind that these prototypes were developed during a sprint > within very short periods of time. You will need to look at the photos > of the paper designs that are linked in the document. > > > https://docs.google.com/document/d/1TG1VsXu_oBPuDK08rcbTFhP25CT_oAsywtWPLkyjZGw/edit?usp=sharing > > > jeanne > > > On 7/25/2018 10:54 AM, Jim Allan wrote: > > Jeanne, > > the link for the prototype for UA and AT (assistive tech? or authoring > > tool?) would be useful. > > Sounds like Element Level is the choice. I will dig around and see what > > resources we have on that SC. > > > > Jim > > > > On Wed, Jul 18, 2018 at 12:49 PM Jeanne Spellman > > <jspellman@paciellogroup.com <mailto:jspellman@paciellogroup.com>> > wrote: > > > > I think Element Level Customization would be a challenging choice > > (therefore a good choice) for Silver feasibility testing. I would > also > > like an example that could be used for Silver feasibility testing of > > measurement of success-criteria-equivalents. I think Jim mentioned > > Font > > Families as an example of an SC that is difficult to True/False > > statement test. I think this would also be helpful. > > > > Could you ask someone to write up the description of the SCs (maybe > > whatever you drafted for the Understanding document would do as is) > so > > we can start including the text in the prototypes? This is NOT a > > content proposal, this is sample text that we can use for evaluating > > the > > prototypes. We aren't working on content yet. Content will be > starting > > in Q4 2018 at the earliest. > > > > This just my opinion, because the Silver group only discussed > including > > user agents at the Design Sprint, and hasn't developed any ideas in > > detail since then. I would like to invite any of you to try out some > > ideas, because I think that LVTF has a high investment in user agent > > accessibility. > > > > I think Silver could approach user agent accessibility like this: For > > each Silver success-criterion-equivalent, there would also be > > implementation advice for user agents, assistive technology, and > > authoring tools (in addition to advice for authors). For user agents, > > the tests could become Web Platform tests (the results are public and > > watched by the browser C-level executives). Web Platform has never > had > > accessibility tests, but I know there are people in the browser A11y > > departments that are interested in writing them. > > > > At the Design Sprint, Makoto Ueki spoke passionately of the need to > > include AT advice for international users. This could help the > > non-English screen readers prioritize and implement features that > they > > currently cannot do. I would like Silver to include AT advice and > > Authoring Tool advice as well as User Agent. Wayne Dick talked about > > the > > need for better AT for low vision. He discussed how the various low > > vision AT are insufficient for long form reading. Silver could help. > > > > Table 2 at the Silver Design Sprint did a rough prototype on > including > > User Agent and Assistive Technology advice. I can find the link to > > it if > > you want to see it for inspiration. > > > > Thanks! This is really a big help to the Silver group. It is much > > better to involve the people who are expert in the issues early on. > > > > jeanne > > > > > > On 7/18/2018 10:04 AM, Jonathan Avila wrote: > > > +1 to element-level customization as well -- although I admit it > > could be tricky from simply an authoring standpoint. > > > > > > Jonathan > > > > > > -----Original Message----- > > > From: Laura Carlson <laura.lee.carlson@gmail.com > > <mailto:laura.lee.carlson@gmail.com>> > > > Sent: Wednesday, July 18, 2018 9:57 AM > > > To: Jim Allan <jimallan@tsbvi.edu <mailto:jimallan@tsbvi.edu>> > > > Cc: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org > > <mailto:public-low-vision-a11y-tf@w3.org>>; Jeanne Spellman > > <jspellman@paciellogroup.com <mailto:jspellman@paciellogroup.com>> > > > Subject: Re: Prototype Silver SC > > > > > > Hi Jim, > > > > > > +1 for Element Level Customization. > > > > > > https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Element_Level_Customization > > > > > > Kindest Regards, > > > Laura > > > > > > On 7/17/18, Jim Allan <jimallan@tsbvi.edu > > <mailto:jimallan@tsbvi.edu>> wrote: > > >> Last week, the Silver Task Force asked the LVTF for SC that did > not > > >> make it in to WCAG21. Several items were mentioned, see below. > Which > > >> is our #1 choice > > >> > > >> - Browser exemptions/issues > > >> - 1.4.11 [1] - "... where the appearance of the > > component is > > >> determined by the user agent and not modified by the > author;" > > >> the exemption > > >> for contrast of native active elements (form element, > focus > > >> ring, media > > >> controls, etc.) failing WCAG20 3:1 contrast threshold > > >> - 1.4.13 [2] - "Exception: The visual presentation of the > > additional > > >> content is controlled by the user agent and is not > > modified by the > > >> author." the exemption for 'title' attribute > > >> - Element Level Customization [3] - user interface for UA to > > allow > > >> override of many values. Closely related to Personalization. > > It is the > > >> super set of the proposed SCs on font size, family, color, > > >> justification, hyphenation, etc. Also know as Return of User > > Stylesheets > > >> - Printing [4] - documents printed do not loose content. > > Huge discussion > > >> - much having to do with testing. Closely related to this is > the > > >> user being > > >> able to print what is on the screen after all of the font, > > spacing, and > > >> sizing changes have been applied. Would be nice not to have > > to write a > > >> print style sheet. If I zoom a page a bit to make it easier > to > > >> read, I want > > >> to print at that size. > > >> > > >> > > >> > > < > https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Issues_to_be_addres > > >> sed_in_Silver> 1. > https://www.w3.org/TR/WCAG21/#non-text-contrast > > >> 2. https://www.w3.org/TR/WCAG21/#content-on-hover-or-focus > > >> 3. > > >> > > > https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Element_Level_Customization > > >> 4. https://github.com/w3c/wcag21/issues/76 [Printing SC] > > >> > > >> LVTF issues for Silver > > >> > > < > https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Issues_to_be_addres > > >> sed_in_Silver> > > >> -- > > >> 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 > > >> > > > > > > > > > -- > > > Laura L. Carlson > > > > > > > -- > > > > Jeanne Spellman > > -- > > Senior Accessibility Engineer > > The Paciello Group > > https://www.paciellogroup.com > > A VFO™ Company http://www.vfo-group.com/ > > > > Skype: jeanne_spellman > > Twitter, Github @jspellman > > -- > > This message is intended to be confidential and may be legally > > privileged. It is intended solely for the addressee. If you are not > the > > intended recipient, please delete this message from your system and > > notify us immediately.Any disclosure, copying, distribution or action > > taken or omitted to be taken by an unintended recipient in reliance > on > > this message is prohibited and may be unlawful. > > > > > > > > -- > > 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 > > -- > > Jeanne Spellman > -- > Senior Accessibility Engineer > The Paciello Group > https://www.paciellogroup.com > A VFO™ Company http://www.vfo-group.com/ > > Skype: jeanne_spellman > Twitter, Github @jspellman > -- > This message is intended to be confidential and may be legally > privileged. It is intended solely for the addressee. If you are not the > intended recipient, please delete this message from your system and > notify us immediately.Any disclosure, copying, distribution or action > taken or omitted to be taken by an unintended recipient in reliance on > this message is prohibited and may be unlawful. > >
Received on Saturday, 28 July 2018 15:41:44 UTC