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

You rock! Thanks, Eric.


On 05/07/2017 17:46, Eric Eggert wrote:
> This week, I used my GeekWeek[^1] 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://github.com/w3c/wai-wcag-quickref/issues/139))
> 
>    * Fix share links to have the proper label 
> ([#143](https://github.com/w3c/wai-wcag-quickref/issues/143))
> 
>    * Remove wrongly set Complementary landmarks (All notes were in an 
> aside which create the unnecessary landmarks) 
> ([#145](https://github.com/w3c/wai-wcag-quickref/issues/145))
> 
>    * Add landmarks to the individual SCs by adding role=region to the 
> `<article>` and label with the heading inside. 
> ([#137](https://github.com/w3c/wai-wcag-quickref/issues/137))
> 
> * 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://github.com/w3c/wai-wcag-quickref/issues/142))
> 
> * Manually re-ordered and added some Failures that were not exported 
> correctly from WCAG 
> ([#146](https://github.com/w3c/wai-wcag-quickref/issues/146))
> 
> * Fix scrolling behavior 
> ([#135](https://github.com/w3c/wai-wcag-quickref/issues/135))
> 
> * Tested reported browser issues and couldn’t see them, so I closed the 
> related issues 
> ([#140](https://github.com/w3c/wai-wcag-quickref/issues/140), 
> [#148](https://github.com/w3c/wai-wcag-quickref/issues/148))
> 
> ## 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://github.com/w3c/wcag-em-report-tool/commit/fc589080e1fefa99de2db5923be5dca400e2bcb4)) 
> 
> * Fixed the extremely thin font on Retina Mac screens 
> ([#283](https://github.com/w3c/wcag-em-report-tool/pull/283))
> 
> ## Tables Tutorial
> 
> * Clarified headers/id example that was a bit confusing 
> ([#533](https://github.com/w3c/wai-tutorials/pull/533/files))
> 
> ## 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://github.com/w3c/wai-tutorials/pull/534/commits/a2c650fa76090b923060d28dbf870d5273453218), 
> see also [#522](https://github.com/w3c/wai-tutorials/issues/522) and 
> [#525](https://github.com/w3c/wai-tutorials/issues/525))
> 
> * 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://github.com/w3c/wai-tutorials/pull/534/commits/5cf5abad82d5d55714f25d8f4d1243fb101ce38e)) 
> 
> 
> 
> Best, Eric
> 
> 
> [^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.
> 
> 
> 
> -- 
> 
> Eric Eggert
> Web Accessibility Specialist
> Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)

-- 
Shadi Abou-Zahra - http://www.w3.org/People/shadi/
Accessibility Strategy and Technology Specialist
Web Accessibility Initiative (WAI)
World Wide Web Consortium (W3C)

Received on Wednesday, 5 July 2017 17:28:45 UTC