GOLDEN KNIGHTS WIN! GOLDEN KNIGHTS WIN! GOLDEN KNIGHTS WIN!
Yesterday in regulation play the Vegas Golden Knights were victorious over the Anaheim Ducks by a final score of 5 – 2.
The next scheduled game for the Vegas Golden Knights is tomorrow Saturday, January 16, 2021 at 10:00 pm against the Anaheim Ducks.
Go Golden Knights Go!
LIGHTNING WIN! LIGHTNING WIN! LIGHTNING WIN!
Yesterday in regulation play, the Tampa Bay Lightning beat the Chicago Black Hawks by a final score of 5 to 1.
The next scheduled game for the Tampa Bay Lightning is tomorrow Friday, January 15, 2021 at 7:00 pm against the Chicago Black Hawks.
Go Bolts Go!
FLYERS WIN! FLYERS WIN! FLYERS WIN!
Yesterday, the Philadelphia Flyers defeated the Pittsburgh Penguins by a final score of 6 to 3 in regulation play.
The next scheduled game for the Philadelphia Flyers is tomorrow Friday, January 15, 2021 at 7:00 pm against the Pittsburgh Penguins.
Go Flyers Go!
Two games to be interested in today, the Dallas Stars at the Florida Panthers; however, postponed. Stay tuned for the next Panthers game to be announced.
The second game of interest is the Anaheim Ducks at the Vegas Golden Knights at 10:00 pm.
Go Golden Knights Go!
That is right!
After a weeklong discussion between the WordPress Accessibility Team and at least one representative or possibly more from Automatic the WordPress 5.6.0 block editor is broken in such a way that anyone using assistive technology is not able to edit text/data in any of the blocks.
Automatic has deliberately and blatantly pressed forward with changing how individuals interact with editing blocks in the new block editor disregarding all suggestions from the accessibility team by choosing to simulate a feature of Microsoft Word that is in no way accessible which is the word templates. Word templates never have been accessible, nor will they ever be accessible. Also, if they believe that WordPress can perfectly simulate or mimic MS Word, their heads are in their own gluteus maximus, as it will never happen.
Automatic along with their upper echelon starting with the very top, have what I believe is a bias towards any person/persons with a disability by not accepting recommendations from the accessibility team which you can see by past and current decisions they have made.
You can actually see or listen to Matt’s response from Word Camp U. S. in November 2019 where he was asked about policies and procedures for implementing accessibility. This was done in the question-and-answer session after he delivered his State of the Word speech from ST. Louis. The answer that Matt gave was nothing more than bull shit held together with bailing wire and everyone in attendance sucked it in like mindless robots.
Assistive technology cannot even invoke forms or edit mode, this is because of the design decisions made regarding the edit fields within the blocks themselves. There is no focus border/boundary to assist keyboard users/screen reader users with properly selecting text so that it can be properly edited, formatted, or manipulated. There is nothing for screen readers to use to gain programmatic focus. Whomever made the decision to setup the blocks with edit fields such as this, chose to utilize the most inaccessible feature of Microsoft Word which is the Word templates. Word templates use shaded areas to indicate to a sighted user where to type and is informed via text as a placeholder within the edit field as to the kind of information to be entered into each field. This decision in the long run will create many problems that will be difficult at best to fix and turn into a big nightmare.
We updated to WordPress 5.6.0 after the first of the year and started testing the block editor to find that Automatic had made changes against all recommendations not to move forward with this idea as JAWS, NVDA and Microsoft Narrator all state when attempting to edit blocks that either the block is empty or it can not recognize any edit field that contains data that can be edited, formatted, or manipulated in any way.
WordPress 5.5.3 by no means was accessible, however with diligent practice one could at least insert and then edit a block. We were in the middle of a big project that is now in a major stop and hold where we were documenting on how individuals could at least perform some editing features with screen readers or other assistive technologies even though it takes about 2.5 times as long as writing straight HTML.
Accessibility is about quality and having a quality product means that any person regardless of the tools they need to use should have an even playing field to get the job done!
With the WordPress 5.6.0 release it is very clear that Automatic cares nothing about quality at all.
After an exciting come back win Saturday night in game 4 of the World Series with the Tampa Bay Rays defeating the Los Angeles Dodgers by a score of 8 – 7 to tie this series 2 games each, the Tampa Bay Rays lose game 5 to the Los Angeles Dodgers by a score of 4 – 2.
The Dodgers are now leading this series 3 games to 2.
Game 6 of the World Series from Arlington, Texas is scheduled for Tuesday, October 27, 2020 at 8:08 pm.
Rays Up!
Lets go Rays!
Watch out for announcements on quick tutorials that Amanda Rush and I are writing on using the WordPress block editor.
You can check out https://www.customerservant.com and then choose the “articles” link.
Also you can watch for us on twitter @whiskeydragon1 @cswordpress and @megarush1024
As soon as the proof reading and editing is done we will be posting them.
So far we have written the following for screen reader and keyboard users:
WordPress keyboard shortcuts for the block editor
Inserting, deleting, and changing layouts of blocks
Heading blocks with a keyboard
Paragraph Blocks with a keyboard
Columns blocks with a keyboard
Image blocks with a keyboard
List blocks with a keyboard
These tutorials in no way mean that the WordPress block editor is accessible, we’re just sharing information that we found on our painful adventures of trial and error testing to figure out how some of these blocks actually work with a screen reader and a keyboard.
If you want us to explore any specific blocks and write a quick tutorial on how they work, let us know on our web site, or send us a tweet.
For the past two (2) days, Amanda and I have been writing, proof reading and editing documents on using the Gutenberg block editor in WordPress.
Any screen reader user is going to need to be a master of their tools to get any job done with a keyboard.
Even though, we are practicing how to use a screen reader along with the keyboard shortcuts, there is a myriad of problems such as; keystrokes conflicting with the screen reader, browsers being tested, and Windows O/S making it frustrating as it takes about three (3) times longer to achieve any goals to complete our tasks. Not to mention all of the lock ups and crashes caused by the keyboard conflicts.
We are writing tutorials so that keyboard users, not just screen reader users won’t have to endure any unnecessary slowdowns like we have run into during two (2) different projects we are about to complete using the default twentytwenty theme and the block editor.
I heard that someone made the statement because the block editor has keystrokes assigned that it is accessible, well I have this to say to that person, “Get your head out of your anal area!”
