Re: Quickref/WCAG EM Report Tool/Tutorials Updates FYI

Footnoted “Geek Week” for the win.    You are the best Eric.  ☺


--
Kris Anne Kinney
Accessibility Specialist
Educational Testing Service
609-734-1466

The only thing worse than being blind is having sight with no vision.  ~ Helen Keller

Have a request for an accessibility review?  Please submit your Accessibility Work Request here<https://etsorg1.sharepoint.com/teams/rd/a11y/Lists/Accessiblity%20Work%20Requests/active.aspx>.

Vacation Plans : Out July 24th-28th


From: Eric Eggert <ee@w3.org>
Date: Wednesday, July 5, 2017 at 11:46 AM
To: EOWG <w3c-wai-eo@w3.org>
Subject: Quickref/WCAG EM Report Tool/Tutorials Updates FYI
Resent-From: <w3c-wai-eo@w3.org>
Resent-Date: Wednesday, July 5, 2017 at 11:46 AM


This week, I used my GeekWeek1 time last week to go through issues on several projects and fix some of the low-hanging fruit!

All of the below is not published on w3.org yet, but I plan to do that eventually this week or early next week.

Feel free to skim the issues.

Quickref

·         Several ARIA fixes:

     *   Removed the tab panel ARIA as we did not implement the associated keyboard navigation (#139<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwai-wcag-quickref%2Fissues%2F139&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=tcS4cH4aNw9zgUurSRFMSmXPWqUoEqAXXpuUSEB0TeA%3D&reserved=0>)
     *   Fix share links to have the proper label (#143<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwai-wcag-quickref%2Fissues%2F143&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=diQB1tvZQKM%2BBqQs1nFc2DAXXQLtkJmRv3raDEzzogY%3D&reserved=0>)
     *   Remove wrongly set Complementary landmarks (All notes were in an aside which create the unnecessary landmarks) (#145<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwai-wcag-quickref%2Fissues%2F145&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=lQraJc9y58sWyTppsY7LAMeYIAuI5V65FXNc1IOXBfk%3D&reserved=0>)
     *   Add landmarks to the individual SCs by adding role=region to the <article> and label with the heading inside. (#137<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwai-wcag-quickref%2Fissues%2F137&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=gmK5mmfnoPBDQM7fVWBu0a1NBWEFOHufI9%2B8YLn2GWI%3D&reserved=0>)

·         Renamed “Filtered Success Criteria” on the bottom to “Filtered-Out Success Criteria” – Although we as a group decided that “filtered” was OK, I heard from several people that “Filtered-Out” is just easier to understand. (And all SCs are filtered…) (#142<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwai-wcag-quickref%2Fissues%2F142&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=TBS6VLFd6AQY8N4MsgQ0mSQMzqgLsxe6u7VZLpTV%2BdE%3D&reserved=0>)

·         Manually re-ordered and added some Failures that were not exported correctly from WCAG (#146<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwai-wcag-quickref%2Fissues%2F146&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=qCUGbZh8xVBrmBtIehcsN9thH7DYTeamEK1RO4fy8r0%3D&reserved=0>)

·         Fix scrolling behavior (#135<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwai-wcag-quickref%2Fissues%2F135&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=GhFUtOWA34qYYPzrTOg%2FZU501Ec8TxuYEY0R7cW%2Fi1U%3D&reserved=0>)

·         Tested reported browser issues and couldn’t see them, so I closed the related issues (#140<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwai-wcag-quickref%2Fissues%2F140&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=HMN84GwwlDq8Uz69Pa6k47QRktqp3RorMWjVpAjB6Co%3D&reserved=0>, #148<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwai-wcag-quickref%2Fissues%2F148&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=iB08T8iu5ohFA8OQq2UiSFWSR7WJW9zyewD31UtJc6A%3D&reserved=0>)

WCAG EM Report Tool

  *   A bug was reported about the downloaded report’s JavaScript not working. Together with Wilco Fiers, who did the initial development of the tool, I found the error and corrected it. (fc589080<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag-em-report-tool%2Fcommit%2Ffc589080e1fefa99de2db5923be5dca400e2bcb4&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=iEyQAGGaTbpZ39WOR0PkpCTbShgNvfIbGOuzdPNdkVM%3D&reserved=0>)
  *   Fixed the extremely thin font on Retina Mac screens (#283<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag-em-report-tool%2Fpull%2F283&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=%2B0THcnrAjnUuZDDDyCVgBVsGynCFDDi3DcNo5mV40W8%3D&reserved=0>)

Tables Tutorial

  *   Clarified headers/id example that was a bit confusing (#533<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwai-tutorials%2Fpull%2F533%2Ffiles&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=lMYiUQCjm5bllwIengfj%2Fx5BspS7LL12Ss%2BWky6JF9w%3D&reserved=0>)

Fly-Out Menus Tutorial

·         Move the button for the fly-out menu out of the link (where it belongs) and change the styling. Adding text to the “open menu” button that designates which menu will be opened. (a2c650fa<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwai-tutorials%2Fpull%2F534%2Fcommits%2Fa2c650fa76090b923060d28dbf870d5273453218&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=M9YMyxIwXGLUyxYhzpNnQF2vbrVI6uqUPFKGEn%2FU2mA%3D&reserved=0>, see also #522<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwai-tutorials%2Fissues%2F522&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=He6HvfWjuE7zDXSeME23qDOWJo1ndw8%2B3DRfoKLAq5Y%3D&reserved=0> and #525<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwai-tutorials%2Fissues%2F525&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=7cIxnFxC1yI8%2B6UYq09JebDFHzUU0HYf5YKfEzlyUXk%3D&reserved=0>)

·         Change font for code examples from Fira Code (which has ligatures) to Fire Mono (which has none) as the ligatures could be confusing to people not used to seeing them in code. (The use of ligatures was not deliberate, I embedded the wrong font.) (5cf5abad<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwai-tutorials%2Fpull%2F534%2Fcommits%2F5cf5abad82d5d55714f25d8f4d1243fb101ce38e&data=02%7C01%7Ckakinney%40ets.org%7C0732b779f3c948f583f408d4c3bd1db6%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636348664392930516&sdata=F9iNWGYetb3Hue%2FBC8Cvg87v9tuDgTFKNi0QDkUzbNk%3D&reserved=0>)

Best, Eric

--

Eric Eggert
Web Accessibility Specialist
Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)

________________________________

  1.  One week a year, W3C staff is asked to “geek out” and play around with technology or or do whatever they feel passionate about in W3C. ↩

________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________