- From: Wayne Dick <wayneedick@gmail.com>
- Date: Mon, 19 Nov 2018 11:12:08 -0800
- To: Laura Carlson <laura.lee.carlson@gmail.com>
- Cc: Shawn Lauriat <lauriat@google.com>, jspellman@spellmanconsulting.com, public-silver@w3.org, John Foliot <john.foliot@deque.com>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
- Message-ID: <CAJeQ8SALmPn-6eAcxgbkH=6nMMY9ZEnP2T=WWxvzayLxOGZCAg@mail.gmail.com>
Hi All, Font is measurable now. I developed an active way to compute width as it is set by the browser. If someone had even looked at my code at 2.1 time they would have realized it is measurable. Take a look: http://nosetothepage.org/TextAccessibility/FontCompare.html and http://nosetothepage.org/TextAccessibility/WebSafeCompare.html Color is also measurable, but there are too many coding conventions at this time that conflict reasonable color change. Jon A has done a lot of experimentation with high contrast on Windows. I have started experimenting with what I call assertive selectors. Rather than using the universal * selector, I've just focused on selectors that will likely contain text. I avoid div because most bad color actors are contained in div's. This leaves some ugly white stripes in pages, but large blocks of text are almost always colored well. Best, Wayne On Mon, Nov 19, 2018 at 5:18 AM Laura Carlson <laura.lee.carlson@gmail.com> wrote: > Hi Shawn and all, > > Indeed. > > Generalizing Text Spacing under something such as an adaptable or > adjustable guideline could also cover some of the Low Vision TF's > previous proposed Success Criteria (SC) that did not make it into WCAG > 2.1 such as Text Colors [1] and Font Family [2]. In fact, at one time > our 2.1 proposal combined text color, font, and spacing in one > "Adapting Text" SC [3]. So if we general it again, we have come full > circle. > > Text Colors and Font Family were not accepted into an "Adaptable" 2.1 > SC because they were not measurable under the 2.1 framework. How could > they be made measurable in Silver? Make them User Agent requirements > instead of author content requirements? > > Thank you. > > Kindest regards, > Laura > > [1] https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Text_Colors > [2] https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Font > [3] https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Adapting_Text > > On 11/16/18, Shawn Lauriat <lauriat@google.com> wrote: > > Indeed, thank you, Laura! > > > > In an effort to not drop the conversation we started during today's call > > (explicitly +John, since you and I in particular had *just* got into > > discussing potential scoping for this when I ran out of time in my > > conference room): > > > > Thinking that the overall guidance, generalized well in Laura's > prototype, > > could expand to cover other aspects of text/content/etc. reflow and > > adaptability beyond just 1.4.12 Text Spacing > > <https://www.w3.org/TR/WCAG21/#text-spacing>, like: > > > > - 1.3.4 Orientation <https://www.w3.org/TR/WCAG21/#orientation> > > - 1.4.4 Resize text <https://www.w3.org/TR/WCAG21/#resize-text> > > - 1.4.8 Visual Presentation > > <https://www.w3.org/TR/WCAG21/#visual-presentation> (at least bits of > > it) > > - 1.4.10 Reflow <https://www.w3.org/TR/WCAG21/#reflow> > > > > The overall interaction and intentions for these seem to me to all stem > > from the same principle of allowing users to customize or otherwise have > > flexibility in the rendering of the given content and/or user interface. > > Many of these SCs I think would then (as Laura, you had in your draft) > turn > > into methods for a given technology, while others may turn into tests on > > particular methods, where the methods would come from the Techniques that > > we have today. > > > > Resulting in a structure something like: > > > > - Guidance: [something like "Text spacing can be overidden." that > covers > > other aspects of adaptive rendering beyond just text spacing] > > - Methods (just picking HTML page and PDF documents as two > technologies > > to try illustrating how I think this could work): > > - [ HTML+CSS Techniques for each current SC, probably broken up in > > different ways, since many include several text attributes for one > > SC] > > - Tests: > > - [How to alter the CSS rules that would affect each > technique, > > and analyze the resulting rendering] > > - [ PDF Techniques for each current SC, probably broken up in > > different ways, since many include several text attributes for one > > SC] > > - Tests: > > - [How to alter the PDF rendering rules in a viewer that > would > > affect each technique, and analyze the resulting rendering] > > > > Kind of shorthand, but what do you think about that? Too granular? I'd > want > > to really expand this out into all of the applicable rules we'd want to > > include to get a better sense of the overall threshold of > > what-makes-a-method, since it still feels too low level to me. For spoken > > feedback, for a very different sort of guidance context, you'd have a > whole > > other set of attributes (voice, rate, pitch, volume, intonation, etc.). > > > > -Shawn > > > > On Fri, Nov 16, 2018 at 1:28 PM Jeanne Spellman < > > jspellman@spellmanconsulting.com> wrote: > > > >> Thank you Laura! I appreciate the time you took on writing it. > >> > >> We will talk about it in our meeting today. Any other feedback for us > >> on how easy or hard it was to transition to the Silver version? Things > >> you liked or didn't like? Thoughts? Cautions? > >> > >> > >> On 11/16/2018 12:59 PM, Laura Carlson wrote: > >> > Hi Jeanne and all, > >> > > >> > Thank you for the invitation. > >> > > >> > Here is a first attempt for 1.4.12 Text Spacing. > >> > > >> > http://www.d.umn.edu/~lcarlson/wcagwg/silver/prototypes/silver-spacing-draft.html > >> > > >> > Thoughts? > >> > > >> > Kindest Regards, > >> > Laura > >> > > >> > On 11/15/18, Jeanne Spellman <jspellman@spellmanconsulting.com> > wrote: > >> >> Many of you on this list don't have the time to participate in Silver > >> >> regularly, but may have an hour to contribute here-and-there. This > >> >> invitation is for you. > >> >> > >> >> TL;DR (Summary) > >> >> > >> >> Silver team wants help testing and improving two prototypes before we > >> >> send them out to the wider world for comments and testing. It > >> >> involves > >> >> sketching out new Guidelines or translating existing WCAG guidance > >> >> following the templates and examples we provide. Pick one prototype > >> >> to > >> >> test, whichever appeals to you. We want to know the problems you > >> >> encounter, suggestions for improvement, or compliments in trying to > >> >> follow the templates. We aren't writing content for Silver yet, so > >> >> don't worry about the writing. It's the process of writing that we > >> >> want > >> >> to test. It should take about an hour, although some people may > >> >> choose > >> >> to take on harder challenges (1.3.1, I'm looking at you). > >> >> > >> >> Email your work to public-silver@w3.org, or if you wish to send it > >> >> privately, you can email it to jspellman@paciellogroup.com and > >> >> lauriat@google.com. All contributions will be public, but we can > >> >> remove > >> >> your name if you wish. > >> >> > >> >> == Introducing the Prototypes == > >> >> > >> >> The Silver Design Sprint resulted in recommendations for the design > of > >> >> Silver. Silver Community Group has created two prototypes that are > >> >> ready for wider testing. Think of them as alpha stage prototypes > where > >> >> we are looking for input on the basics of the prototypes. These are > >> >> not > >> >> ready for broad input, so please don't share them on social media > yet. > >> >> We do have a plan for receiving broad input, but one of the > prototypes > >> >> can't handle the bandwidth of many testers yet. > >> >> > >> >> We are currently testing: > >> >> > >> >> * the proposed structure of Silver (Information Architecture) > >> prototype > >> >> * the use of a style guide to write Silver in plain language > >> >> > >> >> Note: Any content that is proposed in this test is not intended to go > >> >> into Silver. We are not writing content yet. > >> >> Note: We have additional prototypes under development that are not > yet > >> >> ready for review, most notably, the Conformance prototype. > >> >> > >> >> Pick one: > >> >> > >> >> * You can use an existing WCAG success criterion or combination of > >> >> related success criteria for either the Information Architecture > >> >> or > >> >> Plain Language test. We expect most people to choose this. > >> >> * Brave souls could stress test the Information Architecture by > >> >> tackling breaking up WCAG 1.3.1 or including pointer events in > >> >> keyboard navigation. :) > >> >> * You could sketch out tests, Methods and Guideline for a user > need > >> >> that is not included in WCAG to test the Information > Architecture > >> >> prototype. > >> >> * You could sketch out Methods for a user agent (browser or > >> >> assistive > >> >> technology) or authoring tool to test the Information > >> >> Architecture > >> >> * If you are expert or passionate about plain language, use our > >> >> Style > >> >> Guide to translate existing WCAG guidance in plain language. > >> >> > >> >> Choose whichever prototype appeals to you. Please copy the template > >> >> for > >> >> the prototype and fill it out using whatever text editing tool (Word, > >> >> HTML, Github PR, Google Doc, email) -- whatever works for you. Email > >> >> it > >> >> to public-silver@w3.org. If you wish to send it privately, you can > >> >> email it to jspellman@paciellogroup.com and lauriat@google.com. All > >> >> contributions will be public, but we can remove your name if you > wish. > >> >> Details on each of the prototypes are after this paragraph. > >> >> > >> >> == Information Architecture == > >> >> We hope this new structure will provide the ability to better include > >> >> user needs that could not be included in WCAG 2.1, like the proposals > >> >> from the Cognitive Accessibility Task Force and the Low Vision > >> >> Accessibility Task Force. We also want to include guidance that goes > >> >> beyond traditional Web Content, such as guidance for mobile apps, > >> >> emerging technologies, authoring tools and environments, browsers and > >> >> user agents, and assistive technology. Keep this in mind as you are > >> >> testing and let us know your feedback. > >> >> > >> >> We are proposing flattening the WCAG 2.x architecture from > Principles, > >> >> Guidelines, Success Criteria, and Techniques to simply Guidelines and > >> >> Methods. Most WCAG 2.x success criteria will become Guidelines. The > >> >> technology-specific success criteria (like most of Robust) will > become > >> >> Methods. Techniques will all be Methods. Some success criteria can > be > >> >> merged -- for example, the success criteria that are essentially the > >> >> same advice, but with different measurement levels for A, AA, and > AAA, > >> >> or Language of Parts and Language of Page could potentially be > merged. > >> >> They would have different Methods for achieving the result, but the > >> >> Guideline could be to identify the language (English, French, > >> >> Japanese, > >> >> Chinese, ...) being used. > >> >> > >> >> We don't want you to focus on the details of the writing, we are more > >> >> interested in you sketching out an accessibility guideline to test > the > >> >> structure of Silver guidance. The working Information Architecture > >> >> prototype deliberately has placeholder language, because we want you > >> >> to > >> >> look at the structure, not the content. We would like you to try > >> >> writing > >> >> Tests, Methods, and Guideline for an existing WCAG success criteria, > >> >> or > >> >> for a new idea for a guideline. We created an example and a template > >> >> that you can use to write new Methods and Guidelines for Silver. > >> >> Please > >> >> note that not everything that people write for this test will > >> >> necessarily go into Silver. We are testing the structure, we are not > >> >> writing new content for Silver. You can sketch out your ideas. You > >> >> will see in the example that we sketched out Methods for technology > >> >> that > >> >> we were not familiar with, just to test whether the Silver > Information > >> >> Architecture could work. > >> >> > >> >> Our process in creating the example was to sketch out the tests, then > >> >> derive the Methods from the tests. After sketching out all the > >> >> Methods > >> >> we could think of (including one that we wished was supported), then > >> >> we > >> >> wrote the Guideline. When you write the tests first, you better > >> >> define > >> >> the edge cases. That should make the Guideline more accurate and > >> >> easier > >> >> to test. You can link to existing WCAG techniques if you want to > >> >> reuse > >> >> their tests. > >> >> > >> >> We want examples of tests that are not just the true/false success > >> >> criteria of WCAG, but are tests that are rubrics, scales, task-based > >> >> assessment, distance from mean, or others. We know there are > >> >> researchers who have worked on a variety of tests for accessibility > >> >> that > >> >> go beyond true/false statement, but we need people to actually write > >> >> some examples. > >> >> > >> >> Links: > >> >> > >> >> * Working Information Architecture Prototype > >> >> > >> >> < > https://mikecrabb.github.io/silver_taggingSystemDemo/guidelines.html> > >> >> (limited bandwidth, the response time may be long). > >> >> * Template for Information Architecture > >> >> > >> >> < > >> > https://docs.google.com/document/d/e/2PACX-1vRgf85Z_NJ7HmF-UX992wLx0F-sCQyipL6USL9HTmvBOWtH53C78SVNjKI8kLTxl5UuYJbc7ImiGsB_/pub > >> > > >> >> Copy it into your text editor of choice, fill it out and send it > >> >> to > >> >> public-silver@w3.org > >> >> * Example for Information Architecture > >> >> > >> >> < > >> > https://docs.google.com/document/d/e/2PACX-1vQTeTyH3FQZ-qkt-UsyoePHV_joN_nDJy5CsMvit4GjKnbw9zsZljvGG-kU2ZTRP6bUEVJmdIWGc_PX/pub > >> > > >> >> - It is titled "Methods Prototype for Language of Page". It > uses > >> >> the WCAG 2.1 success criteria of 3.1.1 Language of Page. Note > >> >> that > >> >> the Guideline was changed to reflect a broader scope than a web > >> "page". > >> >> > >> >> > >> >> == Plain Language == > >> >> The Plain Language prototype examines how we can include supporting > >> >> information that is helpful and easy to understand. Think of it as > >> >> the > >> >> WCAG Understanding document, except this will be included in the main > >> >> version of Silver. It will eventually fit into the Information > >> >> Architecture prototype as the "Long Description". We have put the > >> >> Guideline information in a tab format so it is easier to find the > >> >> information. Those who are interested in the usability of Silver > >> >> should > >> >> try to write guidance following the Style Guide. We have a template > >> >> for > >> >> you to copy and use. We are really testing the Style Guide, but we > >> >> are > >> >> also interested in your feedback about the organization of the > >> >> information including the labels of the tabs. The template only > covers > >> >> the first tab. If you would like to include writing for the other > >> >> tabs, > >> >> that would be very welcome, but we are only asking for the Get > Started > >> tab. > >> >> > >> >> Links: > >> >> > >> >> * Working Plain Language Prototype > >> >> <https://w3c.github.io/silver/prototypes/PlainLanguage2/> > >> >> Select > >> >> the Section Headings link to see an example sketched out. > >> >> * Template for Plain Language > >> >> > >> >> < > >> > https://docs.google.com/document/d/e/2PACX-1vQVTxM2r00NtcYhZJY6lN6xh_fuM9L2jnPZQJ2c59KiyA_-BcC2HkhKf0IxDod4qBunvPkXbhkCHuKq/pub > >> > > >> >> Copy it into your text editor of choice, fill it out and send it > >> >> to > >> >> public-silver@w3.org > >> >> * Example of Plain Language prototype > >> >> > >> >> < > >> > https://w3c.github.io/silver/prototypes/PlainLanguage2/SectionHeading.html > >> > > >> >> - Sections Headings > >> >> * Style Guide for Plain Language > >> >> > >> >> < > >> > https://docs.google.com/document/d/e/2PACX-1vTNEIRmC8KjpYMk4APRTZIVl3AJj7XY7XiG0bDiQM4oLJueOFrpJUjbNY7fj9R41KLwjtBi8irIWclB/pub > >> > > >> >> We want your comments and suggestions on the Style Guide > > -- > Laura L. Carlson > >
Received on Monday, 19 November 2018 19:13:09 UTC