News for hackers. Stuff that matters.
Re:WordPress 5.0: A Gutenberg FAQ by leonk on Friday December 07, 2018 @10:06AM (#18628225)
No mention here about Gutenberg's lack of support for accessibility standards. They pretty much went full steam ahead and left the accessibility team behind. See: https://rianrietveld.com/2018/10/09/i-have-resigned-the-word...
Re:WordPress 5.0: A Gutenberg FAQ by indysigners on Saturday December 08, 2018 @09:46AM (#18635454)
I also found it pretty shocking to learn (https://www.smashingmagazine.com/2018/12/gutenberg-accessibi...) that @photomat did hold a potential professional engagement hostage over Marcy Sutton’s personal blog decision... although he seemingly did reverse that, but still, the whole attitude is fairly disturbing in doesn’t help where there already are lots of emotions involved.
Re:WordPress 5.0: A Gutenberg FAQ by motdiem on Friday December 07, 2018 @10:28AM (#18628423)
There's a whole paragraph in the linked article talking about accessibility - it looks to me that they're mostly planning to improve it in the next few point releases. It's too bad they couldn't bake it in from the start, but at least they seem to acknowledge it
Re:WordPress 5.0: A Gutenberg FAQ by ahoy on Friday December 07, 2018 @11:28AM (#18628998)
not "couldn't" but "refused to"
Re:WordPress 5.0: A Gutenberg FAQ by dpkonofa on Friday December 07, 2018 @12:34PM (#18629634)
Is the summary of that article basically "No one on the accessibility team knows React so we can't help?". If so, then that's more the accessibility team's fault than it is the rest of the dev team. Granted, accessibility should be a priority for the whole team, but when it's your team's job to do that singular part of the development, maybe you should be resigning and let someone who knows what they're doing take over...
Re:WordPress 5.0: A Gutenberg FAQ by photomatt on Friday December 07, 2018 @12:02PM (#18629311)
That article is now two months old and a lot has changed and improved since then. You also have to compare apples to apples: don't just compare writing in a single text area to manipulating complex blocks, try to accomplish the same task (like putting two captioned images side by side) in both interfaces.