3 ms·

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. S

by leonk 8y ago

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-wordpress-accessibility-team/ https://rianrietveld.com/2018/10/09/i-have-resigned-the-word...

motdiem 8y ago
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
- ahoy 8y ago
  not "couldn't" but "refused to"
photomatt 8y ago
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.
dpkonofa 8y ago
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...
indysigners 8y ago
I also found it pretty shocking to learn (https://www.smashingmagazine.com/2018/12/gutenberg-accessibility-situation/#what-happened 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.

by leonk 8y ago

motdiem 8y ago

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

ahoy 8y ago
not "couldn't" but "refused to"

photomatt 8y ago

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.

dpkonofa 8y ago

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...

indysigners 8y ago

I also found it pretty shocking to learn (https://www.smashingmagazine.com/2018/12/gutenberg-accessibility-situation/#what-happened 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.